On Tue, Oct 20, 2009 at 06:17:05PM -0400, John Wiegley wrote:
> I've started the channel #orgmode on irc.freenode.net, for the
> discussion of all things Org and Emacs and between! Come join us!
#org-mode already exists...
--
Paul Holcomb
(quote (("todo" ?t "* TODO %?\n :LOGBOOK:\n -
CREATED:%U\n :END:\n" nil bottom nil)
--
Is there a way to get this function to work with remember as well? I
tried adding to org-remember-before-finalize-hook, but the marker is
in a weird sta
this the right approach? When you do this
you end up with items with "SCHEDULED:" or "DEADLINE:" and no date
after them. These items don't show in the agenda, but it seems a
little ugly.
--
Paul Holcomb *pholcomb\@ cpoint net
On Wed, Dec 23, 2009 at 07:14:44PM -0500, Matt Lundin wrote:
> Paul Holcomb writes:
>
> > Its great that there is a log when the DEADLINE or SCHEDULED value
> > changes for an entry. It would also be nice if you could remove the
> > deadline or scheduled value using
Patch to record a note for removal of SCHEDULED or DEADLINE property.
--
Paul Holcomb *pholcomb\@ cpoint net*
GPG key fingerprint 2B62 05AE EE74 845A 705F D716 28C4 FE1C 088F CFAC
1 files changed, 17 insertions(+), 1 deletions(-)
diff --git a
dd a "CREATED" property for new tasks. I will send
that separately as there are some issues with it still.
--
Paul Holcomb *pholcomb\@ cpoint net*
GPG key fingerprint 2B62 05AE EE74 845A 705F D716 28C4 FE1C 088F CFAC
When you are in agenda view and limit the items that are visible,
such as with a tag restriction, marking and unmarking behaves
incorrectly. After the item is marked or unmarked for bulk action,
the point is moved to the next item, regardless of whether the next item
is visible.
--
Paul
If you only have a repeating SCHEDULED item, allow using the
interface to update DEADLINE; also vice-versa.
In other words, allow org-schedule or org-deadline to update normal
timestamps in the existance of other types of repeating timestamps in
the same heading.
--
Paul Holcomb
o apply patches also
> in the future, even if they become longer?
I just started looking into this yesterday. :)
--
Paul Holcomb *pholcomb\@ cpoint net*
GPG key fingerprint 2B62 05AE EE74 845A 705F D
to show all of the data about to be moved in a
separate frame, as there is totally the possibility of destroying a
large amount of data in this way.
--
Paul Holcomb *pholcomb\@ cpoint net*
GPG key fingerprint 2B62 05AE
n then use an agenda search to find the marked
> entries and execute the bulk action from the agenda.
Awesome. Thanks for all the work here.
--
Paul Holcomb *pholcomb\@ cpoint net*
GPG key fingerprint 2B62 05AE EE74 845A 705F D
teractive)
(if (eq (get-char-property (point-at-bol) 'type)
'org-marked-entry-overlay)
(org-agenda-bulk-unmark)
(org-agenda-bulk-mark)))
--
Although it would probably be better to refactor the bulk checker
rather than copying the code here.
--
Paul Holcomb
hat should
> be the key for it? I guess you would then have to use the
> agenda-mode-hook to redefine the m key.
I thought s was fine for the key, as C-x C-s already is bound to
org-save-all-org-buffers.
--
Paul Holcomb *pholcomb\@ cpoint net
rg-pah-todo-exclude))
org-tags-view((4) (quote org-pah-todo-exclude))
It seems like the evaluation order is at fault, but I couldn't get further.
Any suggestions?
Thanks,
--
Paul Holcomb *pholcomb\@ cpoint net*
GPG key fingerpr
> >further.
>
> indeed, currently the match entry is not evaluated. I guess we could
> do that, but it would involve changing several functions. I would
> need a convincing use case before I invest the time. How would you
> want to use this?
15 matches
Mail list logo
