On Wed Mar 04 2009 at 16:26, Nick Dokos wrote:
> Nick Dokos wrote:
>
>> Bill White wrote:
>>
>> > On Wed Mar 04 2009 at 12:38, Nick Dokos wrote:
>> >
>> > > Bill White wrote:
>> > >
>> > >> Hi all -
>> > >>
>> > >> "Buffer *temp* modified; kill anyway?" is driving me nuts.
>> > >>
>> > >
Nick Dokos hp.com> writes:
> Try
> import sys
> sys.stdout.write("[%d]" % val)
Thanks. That works fine.
> (shell-command "nextnum" t)
This worked fine.
>
> It may be necessary to specify a complete path to the command.
I diodnt need to because the .BAT file was in a directory wh
Charles Cave wrote:
> ...
> print "[#%s]" % val
>
>
> ...
>
> ESC-1 ESC-! nextnum RET Ctl-D
>
> The Ctrl D is needed to remove a carriage return (not sure why it is
> there.
Try
import sys
sys.stdout.write("[%d]" % val)
instead of print. It should work on Windows as well (bu
Recently I asked about a method of inserting a unique number in a
headline. My requirement is to be able to uniquely identify a
particular headline when exporting data to another system
(ListPro on Palm/Windows).
I settled on using a small Python script, since I am not
a Lisp programmer.
1.
On Tue, Mar 3, 2009 at 3:34 AM, Carsten Dominik wrote:
>> Now how do we want to do this with org-mode?
>> 1) The user is responsible for creating a bib-file using
>> whatever tools she prefers (e.g. bib2bib).
>> 2) Add an option to just select the entries that are used
>> in the org-file. Nothing
Nick Dokos wrote:
> Bill White wrote:
>
> > On Wed Mar 04 2009 at 12:38, Nick Dokos wrote:
> >
> > > Bill White wrote:
> > >
> > >> Hi all -
> > >>
> > >> "Buffer *temp* modified; kill anyway?" is driving me nuts.
> > >>
> > >> Has anyone seen this error message when html-exporting pages
Bill White wrote:
> On Wed Mar 04 2009 at 12:38, Nick Dokos wrote:
>
> > Bill White wrote:
> >
> >> Hi all -
> >>
> >> "Buffer *temp* modified; kill anyway?" is driving me nuts.
> >>
> >> Has anyone seen this error message when html-exporting pages that
> >> contain #+begin_src ? I get thi
On Wed Mar 04 2009 at 12:38, Nick Dokos wrote:
> Bill White wrote:
>
>> Hi all -
>>
>> "Buffer *temp* modified; kill anyway?" is driving me nuts.
>>
>> Has anyone seen this error message when html-exporting pages that
>> contain #+begin_src ? I get this once for every #+begin_src
>> ... #+en
Bill White wrote:
> Hi all -
>
> "Buffer *temp* modified; kill anyway?" is driving me nuts.
>
> Has anyone seen this error message when html-exporting pages that
> contain #+begin_src ? I get this once for every #+begin_src
> ... #+end_src group on a page. I assume it's coming from htmlize.e
Hi Gour,
Gour writes:
>> "Baoqiu" == Baoqiu Cui writes:
>
> Baoqiu> It is true that many open-source tools around DocBook are still
> Baoqiu> not perfect, but they should be good enough for most of the work
> Baoqiu> of most users. Some commercial tools exist and are better, but
> Baoqiu>
Hi all -
"Buffer *temp* modified; kill anyway?" is driving me nuts.
Has anyone seen this error message when html-exporting pages that
contain #+begin_src ? I get this once for every #+begin_src
... #+end_src group on a page. I assume it's coming from htmlize.el,
but I haven't been able to isol
Hi,
Whenever a tag search is done, the beginning of the lines containing
the desired tags are highlighted (in yellow with my setup). I can see
why this is desired behavior, but I don't want my tag searches to
highlight anything. First, I don't like the way the highlighting
looks, and second, the h
> "Sebastian" == Sebastian Rose writes:
Sebastian> I just did a quick search only and I think more intensive
Sebastian> search would reveal many more.
Check Pandoc's features:
"Pandoc is a Haskell library for converting from one markup format to
another, and a command-line tool that uses th
> "Matthew" == Matthew Lundin writes:
Hi Matthew,
Matthew> Apart from odt output, I'd be curious to know what reST can do
Matthew> that org-mode markup and export cannot. Footnotes, tables,
Matthew> hyperlinks, images---I've found org-mode to be a really great
Matthew> authoring tool for expo
> "Baoqiu" == Baoqiu Cui writes:
Baoqiu> It is true that many open-source tools around DocBook are still
Baoqiu> not perfect, but they should be good enough for most of the work
Baoqiu> of most users. Some commercial tools exist and are better, but
Baoqiu> they are not free. (I have not use
Sebastian Rose wrote:
> in info-view-mode the title is by default in the first section to avoid
> scrolling.
Alright, now I understand the issue.
>
> But you may pull the latest version and append '_title-above' to the
> `view:' option, to leave it above regardless of view-mode.
>
>
> #+INFOJS_OP
Hi Scott,
in info-view-mode the title is by default in the first section to avoid
scrolling.
But you may pull the latest version and append '_title-above' to the
`view:' option, to leave it above regardless of view-mode.
#+INFOJS_OPT: view:info_title-above
#+INFOJS_OPT: view:plain_title-above
Sebastian Rose wrote:
> Hi Scott,
>
>
> this is fixed now in v.0.1.0.4
Thanks, it works. I do have some suggestions for the title.
1. Unfortunately, I cannot use the ftoc:t option. For reasons I won't
go into here, I cannot have the table of contents displayed on one
side of the page. If I use ft
Bernt Hansen writes:
>> Mark,
>> Sorry about the yellow I hadn't noticed it. I am trying to fix it, but
>> it seems to be defeating my very limited css skills. The css generated
>> by org is:
>>
>>
>> *~
>>
>>
>>
>> bzr add *.org
>>
>>
>> In my stylesheet I am trying things like:
>>
>> pre.src
On Mar 4, 2009, at 3:37 PM, Bernt Hansen wrote:
Ian Barton writes:
Mark Elston wrote:
Just a note. Be careful of the use of colors. For example,
you have quoted strings in yellow in section 3.3. This color
makes the strings almost invisible on my screen. This makes
it hard to read.
Als
>> Sebastian> I highly apreciate the support of Docbook and your
>> Sebastian> effort. Yet, I think I don't want to publish XHTML through
>> Sebastian> Docbook.
Googling brings up quite some interesting formats supported through
DocBook. These are some of the formats I found on the first glance:
Ian Barton writes:
> Mark Elston wrote:
>> Just a note. Be careful of the use of colors. For example,
>> you have quoted strings in yellow in section 3.3. This color
>> makes the strings almost invisible on my screen. This makes
>> it hard to read.
>>
>> Also, is there a single-page or pdf ve
Carsten Dominik writes:
> On Mar 3, 2009, at 9:56 AM, Manuel Hermenegildo wrote:
>
>> I think a perhaps better behavior could be that the same line:
>>
>> ** TODO Check backups <2009-03-05 Thu 11:00 +2d>
>>
>> is marked as done, then a) a *copy* is made of the TODO item, and that
>> copy is t
Hi Giovanni,
I am doing exactly what you do: C-c C-e after the setq form, then
M-x normal-mode.
Works perfectly.
The only reason I can think of is that you somehow managed to make
org-todo-keywords a local variable. This can happen with
a File Variable section in the buffer, or if you
have so
Mark Elston wrote:
Just a note. Be careful of the use of colors. For example,
you have quoted strings in yellow in section 3.3. This color
makes the strings almost invisible on my screen. This makes
it hard to read.
Also, is there a single-page or pdf version of this material?
Mark,
Sorry
--- Mer 4/3/09, Matthew Lundin ha scritto:
> Giovanni Ridolfi wrote:
Hi, Matthew,
thanks for replying.
> >
> > -file-
> > -*- mode: org; -*-
> > * TODO 1st head
> >
> > (setq org-todo-keywords '((sequence "TODO" "FEEDBACK"
> > "VERIFY" "|" "DONE" "DELEGATED")))
Hi Gour,
Gour writes:
>> "Sebastian" == Sebastian Rose writes:
>
> Sebastian> I highly apreciate the support of Docbook and your
> Sebastian> effort. Yet, I think I don't want to publish XHTML through
> Sebastian> Docbook.
>
> +1
>
> I gave up on DocBook long ago. It's pain to author docu
Hi Scott,
this is fixed now in v.0.1.0.4
As always, the script is available on repo_or_cz:
http://repo.or.cz/w/Worg.git?a=blob_plain;f=code/org-info-js/org-info.js;hb=e11bc7fe538a513d899f4d006bf5f887f35dd8ce
Regards,
Sebastian
Sebastian Rose writes:
> Hi Scott,
>
>
> thanks for the report
On Mar 3, 2009, at 9:56 AM, Manuel Hermenegildo wrote:
Nobody else has commented on this, so perhaps I am doing something
wrong.
My recollection is that [setting the todo state of a task with a
repeating scheduled task to done] did not used to insert a closed
timestamp, but now it seems to
Manuel Hermenegildo writes:
> Repeating tasks do not appear in the future or the past. Cyclic
> appointments are close. If I have:
>
> ** TODO Check backups <2009-03-05 Thu 11:00 +2d>
>
> And pass from TODO to DONE this happens:
>
> ** TODO Check backups <2009-03-07 Sat 11:00 +2d>
>CL
Hi Giovanni,
Giovanni Ridolfi writes:
> Hello everybody
>
> I'm not able to change the todo keywords in a file
> with "setq org-todo-keywords" and restarting org-mode
> as described in the manual § 5.2.1 .
>
> Org-mode version 6.23b
> GNU Emacs 23.0.90.1 (i386-mingw-nt5.1.2600) of 2009-02-01 on
Hey all,
To reproduce:
* TODO Make Bicycle :project:workshop:
** TODO Buy stuff
** TODO Build stuff
** TODO Test stuff
(setq org-use-tag-inheritance t)
(setq org-tags-exclude-from-inheritance '("project"))
to type in a match string to search, I type in "project"
I expected to see:
TODO Make B
On Mar 3, 2009, at 9:56 AM, Manuel Hermenegildo wrote:
Nobody else has commented on this, so perhaps I am doing something
wrong.
My recollection is that [setting the todo state of a task with a
repeating scheduled task to done] did not used to insert a closed
timestamp, but now it seems to
Sebastian Rose writes:
> thanks for the report.
>
> The handling of the title is one of the weak points of the script
> (another one being the text before first headline).
>
> The reason might be, that I was never sure what to do with it in
> info-view-mode, plain-view-mode, TOC hidden, TOC.
>
> I
Hi Scott,
thanks for the report.
The handling of the title is one of the weak points of the script
(another one being the text before first headline).
The reason might be, that I was never sure what to do with it in
info-view-mode, plain-view-mode, TOC hidden, TOC.
In info-view-mode, the title
On Tue, Mar 03, 2009 at 01:42:56PM +, Ian Barton wrote:
> I have been working on an article on syncing org files using a version
> control system for a while. The recent posts about using a usb stick
> motivated me to try and finish it.
>
> You can see the html version at
> http://www.ian
On Mar 3, 2009, at 5:09 AM, Samuel Wales wrote:
Hi Carsten,
On Thu, Feb 19, 2009 at 12:22, Carsten Dominik
wrote:
1) priority faces are settable in the agenda. perhaps
they could be so in the outline also.
This seems more confusing than useful to me. In the agenda,
all the tasks are t
Hi Ian,
nice work!
On Mar 3, 2009, at 2:42 PM, Ian Barton wrote:
I have been working on an article on syncing org files using a
version control system for a while. The recent posts about using a
usb stick motivated me to try and finish it.
You can see the html version at http://www.ian-ba
Hello everybody
I'm not able to change the todo keywords in a file
with "setq org-todo-keywords" and restarting org-mode
as described in the manual § 5.2.1 .
Org-mode version 6.23b
GNU Emacs 23.0.90.1 (i386-mingw-nt5.1.2600) of 2009-02-01 on SOFT-MJASON
M$Widows XP
-file---
El dc, mar 04 2009, Carsten Dominik va escriure:
> (org-agenda-filter-preset '("-FLUFF" "-BLUFF"))
Thank you very much for this addition; not only it allows you to filter out a
tag, but also many tags; that is what I needed in the first place.
___
I'm starting to use column mode (C-c C-x C-c) and I'm surprised I can't do some
tasks from within, like for instance:
- move headings up/down with M-up M-down
- clock in/out tasks (C-c C-x C-i and … C-o)
- schedule tasks, etc. I always get: if: Text is read-only: "Type `e' to edit
property"
> Nobody else has commented on this, so perhaps I am doing something wrong.
>
> My recollection is that [setting the todo state of a task with a
> repeating scheduled task to done] did not used to insert a closed
> timestamp, but now it seems to -- or at least it fails to remove the
> times
Hi,
I don't know if it's just my setup, but I see many problems when using column
view (C-c C-x C-c) on org6.23trans+Emacs23(Bazaar), specially with lots of
properties in long lines (more than 1 visual line) or folded contents (where
the ellipsis ... is visible). For instance:
1. The cursor
Dear all
I just pushed a change that makes tag searches from now on case-
sensitive.
Making them case-insensitive was difficult to reconcile with an effort
to make the agenda faster, and something like Eric's org-collector *a
lot*
faster.
I hope you have not relied on case-insensitivity of
Yes, a bug, fixed now, thanks.
- Carsten
On Mar 3, 2009, at 10:48 PM, Jeff Mickey wrote:
Hey all,
To reproduce:
* TODO Make Bicycle :project:workshop:
** TODO Buy stuff
** TODO Build stuff
** TODO Test stuff
(setq org-use-tag-inheritance t)
(setq org-tags-exclude-from-inheritance '("project
Gour writes:
>> "Sebastian" == Sebastian Rose writes:
>
> Sebastian> I highly apreciate the support of Docbook and your
> Sebastian> effort. Yet, I think I don't want to publish XHTML through
> Sebastian> Docbook.
>
> +1
>
> I gave up on DocBook long ago. It's pain to author documents in i
46 matches
Mail list logo
