Carsten Dominik gmail.com> writes:
>
> %T is the correct way to display tags in the prefix - currently only on
> tag will be shown there. If you want to remove the tags from the end
> of the line, take a look at the variable
> `org-agenda-remove-tags-when-in-prefix'.
Thank you, this is what
I've just upgraded from 4.25 to 4.29. With the former, org-agenda-later
(that is by default) in the Agenda does the right thing. With
4.29, same org files and personal configuration, it seems to do nothing
at all.
Best
DC
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Professor David Cha
On Sep 14, 2006, at 17:24, Peter BARABAS wrote:
Hello,
Is there a way to display the tags of an entry after its category? The
default
format for this is:
(todo . " %-12:c")
I tried to put %T into it, but it always prints the tags at the
position of
org-agenda-align-tags-to-column's valu
Hello,
Is there a way to display the tags of an entry after its category? The default
format for this is:
(todo . " %-12:c")
I tried to put %T into it, but it always prints the tags at the position of
org-agenda-align-tags-to-column's value. I cannot find how to disable this
align.
Also, in
Carsten Dominik wrote:
I like this idea and will try to implement it. However, where to store
the followup note is difficult to determine - how about inserting it
directly after the CLOSED time stamp? This may be not be perfect
because it will be before any other information in the entry, b
I think the example is missing some parentheses. I will fix it.
In the meantime i can get this to parse just fine:
(setq org-publish-project-alist
'(("org" :base-directory "~/notebook/org/"
:base-extension "org"
:publishing-directory "~/publ
On Sep 13, 2006, at 22:22, Ed Hirgelt wrote:
I find that I prefer a blank line between items in plain lists.
org-insert-item doesn't do that. The following patch remedies that
under the control of a customization option. Feel free to incorporate
this into a release if you think others woul
On Sep 7, 2006, at 22:14, Daniel J. Sinder wrote:
I find that completing a task often results in follow-up information
that I'd like to add to the entry in my org file. In this way, my
follow-up notes are connected to the action which generated them.
Here's an example. Prior to doing the tas
