From: Ulf Stegemann <ulf-news@zeitform.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-capture in message-mode buffer
Date: Thu, 05 May 2011 09:02:38 +0200 [thread overview]
Message-ID: <zf.upnk4e5mxyp.fsf@zeitform.de> (raw)
In-Reply-To: m1zkn2r0rt.fsf@gmail.com
Leo <sdl.web@gmail.com> wrote:
> On 2011-05-04 21:14 +0800, Ulf Stegemann wrote:
>> The idea behind `org-store-link' (which is triggered by `org-capture')
>> in message mode is to store a link to a /sent/ message even though the
>> message has not been sent by the time you call `org-store-link'. This
>> currently works only with Gnus and only if there's a Gcc header present
>> in the message you are working on. `org-gnus-store-link' needs the Gcc
>> header to determine where the message would go once it has been sent (in
>> order to create a link to it). The error you've encountered means that
>> there hasn't been a Gcc header in your message when you've called
>> `org-capture'.
>
> I think org-gnus-store-link is too aggressive.
Hmmm, is it? Suppose that linking to a message yet to be archived
wouldn't be there, then `org-store-link' will tell you `org-store-link:
Cannot link to a buffer which is not visiting a file' when called in a
message buffer (like in any other non-file buffer).
> I also dislike the fact that it inserts the Message-Id header.
As the org link to Gnus messages consists of the group and the message
id the latter one is need (as is the first one, the Gcc header). No
reliable message id, no org link. One may argue if it's a good idea to
generate the message id when calling `org-store-link' but I think it's a
fair tradeoff to accept this in order to get the link to the message yet
to be archived.
> Also, the stored link may be useless unless it is referenced in the
> template chosen by the user.
Hmmm, I'm not quite sure what your scenario is here. If you dislike the
behaviour of `org-store-link' in message mode and furthermore do not
want to store a link at all since your template does not use it, why do
you call `org-capture' from the message mode buffer at all?
Ulf
next prev parent reply other threads:[~2011-05-05 7:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 12:26 org-capture in message-mode buffer Leo
2011-05-04 13:14 ` Ulf Stegemann
2011-05-04 14:36 ` Leo
2011-05-05 7:02 ` Ulf Stegemann [this message]
2011-05-05 7:59 ` Leo
2011-05-05 8:09 ` Leo
2011-05-05 9:19 ` Ulf Stegemann
2011-05-08 7:53 ` Leo
2011-05-24 3:19 ` Carsten Dominik
2011-05-24 3:57 ` Leo
2011-05-24 10:41 ` Tassilo Horn
2011-05-24 10:56 ` Carsten Dominik
2011-05-24 11:35 ` Tassilo Horn
2011-05-24 11:38 ` Carsten Dominik
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=zf.upnk4e5mxyp.fsf@zeitform.de \
--to=ulf-news@zeitform.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).