From: "Roland Winkler" <winkler@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 15987@debbugs.gnu.org, Stephen Berman <stephen.berman@gmx.net>
Subject: bug#15987: 24.3; diary-add-to-list ignored by diary-mark-entries
Date: Tue, 20 Aug 2019 21:48:00 -0500 [thread overview]
Message-ID: <45280.87155.162160.23900@gargle.gargle.HOWL> (raw)
In-Reply-To: <CADwFkm=LkxkSRw8y4hFq7jxc03sWzhjfWWOEwPhq2=o1QVQ5-w@mail.gmail.com>
On Sun Aug 18 2019 Stefan Kangas wrote:
> "Roland Winkler" <winkler@gnu.org> writes:
> > On Sun Dec 1 2013 Stephen Berman wrote:
> >> It should be possible to do this by implementing a BBDB function for
> >> diary-goto-entry-function; see todo-diary-goto-entry for an example.
> >> (In fact, diary-goto-entry-function was added when the new version of
> >> todo-mode.el was added to Emacs, precisely for this purpose; note,
> >> however, that Todo files that are meant to contain diary entries must be
> >> included in the diary by the usual #include mechanism.)
> >
> > Thanks, I'll look into this. Hopefully, such an approach will not
> > require too dirty tricks.
>
> Did you ever get a chance to look into this? I'm asking since it's
> been a while (six years more or less), and it would be good if we
> could clarify if this is indeed doable and/or desirable.
Thanks for the reminder. Some time ago, I implemented a solution to
this, see the function bbdb-anniv-goto-entry in bbdb-anniv.el that
serves as a value for diary-goto-entry-function (see BBDB in GNU
Elpa or the BBDB repository on savannah). Despite its (current)
prefix `bbdb' the function bbdb-anniv-goto-entry is really
independent of BBDB and it should work for other packages, too. The
idea is to give strings passed to `diary-add-to-list' a text
property `diary-goto-entry' which should be a list (FUNCTION ARG1
ARG2 ...), see the docstring of bbdb-anniv-goto-entry. Then,
bbdb-anniv-goto-entry checks for the presence of this text property
and calls FUNCTION to locate the entry.
I believe, the cleanest, backward-compatible solution would be to
use bbdb-anniv-goto-entry as a replacement for diary-goto-entry
and declare diary-goto-entry-function obsolete. (The obsolete
variable diary-goto-entry-function could be kept for some time
without harm.)
next prev parent reply other threads:[~2019-08-21 2:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 14:40 bug#15987: 24.3; diary-add-to-list ignored by diary-mark-entries Roland Winkler
2013-11-30 23:08 ` Glenn Morris
2013-12-01 1:25 ` Roland Winkler
2013-12-01 12:03 ` Stephen Berman
2013-12-02 1:46 ` Roland Winkler
2019-08-18 17:55 ` Stefan Kangas
2019-08-21 2:48 ` Roland Winkler [this message]
2019-08-21 3:06 ` Stefan Kangas
2019-08-21 3:41 ` Roland Winkler
2019-08-21 13:29 ` Stefan Kangas
2019-08-21 14:10 ` Stephen Berman
2019-08-21 15:46 ` Roland Winkler
2019-08-21 16:31 ` Stephen Berman
2019-08-21 16:46 ` Roland Winkler
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45280.87155.162160.23900@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=15987@debbugs.gnu.org \
--cc=stefan@marxist.se \
--cc=stephen.berman@gmx.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.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).