From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Display most recent log item in Agenda
Date: Sat, 20 Dec 2014 22:13:22 +0100 [thread overview]
Message-ID: <874msqyqh9.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <874msuoidy.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 17 Dec 2014 15:16:57 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> I'm not terribly worried about finding the real last state note with
> 100% accuracy -- as you say, that's not really possible. This would be a
> convenience function displaying a useful bit of information, and if it
> fails to do so no planes will crash.
I should try to answer this to bug reports.
More seriously, if the function is using some heuristics to find the
last note, this should be documented somewhere (e.g., a caveat when
`org-log-into-drawer' is nil).
> I'd be inclined just to go to the location of `org-log-beginning', look
> around for likely log notes, show the most recent one if we can find
> it, and bail if not. What do you think?
That's the idea. The tricky part may be "look around for likely log
notes", depending on how hard you want to try.
Regards,
next prev parent reply other threads:[~2014-12-20 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 10:07 [RFC] Display most recent log item in Agenda Eric Abrahamsen
2014-12-14 15:12 ` Eric Abrahamsen
2014-12-14 20:34 ` Nicolas Goaziou
2014-12-15 1:34 ` Eric Abrahamsen
2014-12-15 12:43 ` Nicolas Goaziou
2014-12-16 2:26 ` Eric Abrahamsen
2014-12-16 9:10 ` Nicolas Goaziou
2014-12-17 7:16 ` Eric Abrahamsen
2014-12-20 21:13 ` Nicolas Goaziou [this message]
2014-12-19 8:50 ` Eric Abrahamsen
2014-12-20 21:02 ` Nicolas Goaziou
2014-12-21 4:08 ` Eric Abrahamsen
2014-12-15 4:29 ` Eric Abrahamsen
2014-12-15 12:33 ` Nicolas Goaziou
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=874msqyqh9.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).