From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Feature idea: show last log entry
Date: Wed, 12 Oct 2011 19:59:06 +0200 [thread overview]
Message-ID: <87zkh6ytud.fsf@Rainer.invalid> (raw)
In-Reply-To: m2pqi2tffg.fsf@boostpro.com
Dave Abrahams <dave@boostpro.com> writes:
> Generally I'm interested in keeping log entries for my Org items for
> historical purposes only (so I like to stash them away in a :LOGBOOK:
> drawer), but on a day-to-day basis I'm interested in the very latest log
> entry; it tells me about the status of the item. For example, if I've
> made a task DELEGATED, the latest log entry usually has the person I've
> delegated it to and often a link to the mail message in which I did the
> delegation. So I'd like a feature that would leave the latest log entry
> outside the drawer, and always file the previous log entry into the
> drawer when I make a new one.
I'm currently using something similar with two drawers back-to-back:
:LOGBOOK:
shiny
:END:
:CLOSED:
old cruft
:END:
That means I have to move old stuff by hand from LOGBOOK to CLOSED (what
I really do is move the :END:/:CLOSED: markers normally), but the way
I'm using this it hasn't been too much trouble.
That said, I've been thinking of extending drawers to have "stops", that
is each visibility cycle on a drawer would just pull it out to the next
stop. Specifically for timestamps there should be some function to
auto-move the stop (current+last week for instance). Presumably if that
was made into a more general function one could also just keep a certain
number of lines before the stop.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
next prev parent reply other threads:[~2011-10-12 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 15:09 Feature idea: show last log entry Dave Abrahams
2011-10-12 17:59 ` Achim Gratz [this message]
2011-10-23 19:44 ` Dave Abrahams
2011-10-13 0:55 ` Bernt Hansen
2011-10-13 6:56 ` John Wiegley
2011-10-13 11:49 ` Bernt Hansen
2011-10-13 12:02 ` Sebastien Vauban
2011-10-23 19:59 ` Dave Abrahams
2011-10-23 20:37 ` Bernt Hansen
2011-10-23 22:18 ` Dave Abrahams
2011-10-23 22:45 ` Bernt Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkh6ytud.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).