From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: howto show all todo's linked with some buffer in agenda?
Date: Sat, 29 Sep 2007 00:43:06 +0200 [thread overview]
Message-ID: <87fy0y1ked.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87odfmwnzq.fsf@web.de> (Jost Burkardt's message of "Fri, 28 Sep 2007 22:09:45 +0200")
Hi Jost,
Jost Burkardt <jost.burkardt@web.de> writes:
> Having tried org-registry I see the following drawbacks
>
> - the file .org-registry, I've no idea about performance issues yet,
> but one of the main reasons for switching from planner-mode to
> org-mode last year, was org-mode's habit of generating the agenda
> dynamically
Actually, this is why John proposed `org-occur-in-agenda-files'.
Mhh... I thought a registry would be more efficient, because you don't
have to fetch for all the links in all agenda files before finding those
pointing to your location. But perhaps maintaining the registry file has
it own cost. I will think more carefully about this and let you know.
> - if I understand the code correctly, org-registry fit's the Links
> generated by org-store-link *exactly*, which seem to rigid for me,
> as I sometimes write by hand, which are only approximate
Agreed. The most common pattern would be to match the link exactly and
to be more liberal about the description. I implemented such a "fuzzy"
matching for planner-registry, and I was quite happy with that.
One caveat though: file links contain context. Obviously, we don't want
to be only able to find such links if the point is *exactly* where the
context was defined from. So I suggest we get rid of the context when
storing a link to the registry. Of course, not having a registry file
would help here :)
Last but not least: plain links are currently not stored. Plain links
are also links in bracket links, so this might be confusing when fishing
for all links in the buffer.
> - The output is spartanic, what I would love to have is a agenda
> overview with TODO-Items and maybe headlines, which are linked to
> the current file or bbdb-entry or mail,....
Okay. I will try to implement some kind of agenda view for headlines
containing a link to the current location. More on this later.
> I think it would be great to have a function (think of
> (org-calendar-goto-agenda) called from the calendar), which would give
> a agenda with todo associated with the current
> file/bbdb-entry/mail/directory,...
Being able to search for several location would also be neat. Imagine:
you want to fetch all TODOs pointing to your bbdb buffer or/and your w3m
buffer or/and your Gnus summary buffer.
> What do you think, possible and/or interesting?
Possible and *very* interesting! Thanks for the input.
--
Bastien
next prev parent reply other threads:[~2007-09-28 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 20:09 howto show all todo's linked with some buffer in agenda? Jost Burkardt
2007-09-28 22:43 ` Bastien [this message]
2007-09-29 12:38 ` Jost Burkardt
2007-09-29 13:36 ` Bastien
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=87fy0y1ked.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).