From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: org-registry.el v0.1 - a registry for Org links
Date: Mon, 24 Sep 2007 11:05:53 +0200 [thread overview]
Message-ID: <878x6wh1qm.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87sl54jy6b.fsf@myhost.localdomain> (cezar@mixandgo.ro's message of "Mon, 24 Sep 2007 10:54:36 +0300")
Cezar <cezar@mixandgo.ro> writes:
> Bastien <bzg@altern.org> writes:
>
>> | Let's say that you are in the Gnus summary buffer. You suddenly
>> | realize that you are on an article or an e-mail that is very likely
>> | to be somewhere in your `org-agenda-files'. Well.. actually you
>> | *know* it's there but can't find it back. How to deal with that?
>
> I fail to understand that :D
Ahem. Was late at night :) Let me give it another try.
Org files are full of links inserted with `org-store-link'. This links
point to e-mail, webpages, files, dirs, info pages, man pages, etc.
Actually, they come from potentially *everywhere* since Org lets you
define your own storing/following functions.
So, what if you are on a e-mail, webpage or whatever and want to know if
this buffer has already been linked to somewhere in your agenda files?
Then org-registry-show will tell you where this location has been
linked.
Hope this is clearer like this, I have updated the commentary in the
source code.
> Maybe give an example of how would this be useful.
I've no time for this right now but I will in the future. One particular
case where that would be useful is when you want to check whether a link
lives in *several* agenda files and want to see all of them.
Regards,
--
Bastien
next prev parent reply other threads:[~2007-09-24 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 22:41 org-registry.el v0.1 - a registry for Org links Bastien
2007-09-24 7:54 ` Cezar
2007-09-24 9:05 ` Bastien [this message]
2007-09-24 11:03 ` Cezar
2007-09-29 17:48 ` Fabian Braennstroem
2007-09-29 16:29 ` Bastien
2007-09-29 16:32 ` Bastien
2007-09-24 9:27 ` 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=878x6wh1qm.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).