From: Ulf Stegemann <ulf-news@zeitform.de>
To: emacs-orgmode@gnu.org
Subject: Re: Store link in message mode
Date: Mon, 15 Nov 2010 17:00:07 +0100 [thread overview]
Message-ID: <zf.upnwroea86w.fsf@zeitform.de> (raw)
In-Reply-To: 874obivco0.fsf@member.fsf.org
Hi Tassilo,
Tassilo Horn <tassilo@member.fsf.org> wrote:
>> If you think --despite of those issues-- it's worth adding the
>> creation of gnus links while in message mode I could provide a patch.
>
> I'm curious how you are able to determine where a message will be filed
> after sending it off. I mean, you neither have the Message-Id at that
> point (unless that's added to `message-generate-headers-first'),
Touché, good point. I had set `message-generate-headers-first' to t
ages ago, so obviously I didn't realise that this is not the default.
You are absolutely right that generating the Message-ID during message
setup is a perquisite for creating a link.
It's probably better, to grab all necessary headers after the message
has been sent (and that's what I originally did). But this means we
cannot use `org-store-link' in message mode and is also impractical when
using `gnus-delay-article'.
Hmmm, thinking about it, maybe `org-store-link' could create the
Message-ID and insert it if it's not already present. I should have a
look.
> nor do you know the correct group, at least if there are more than one
> in the Gcc header.
With multiple groups in Gcc I currently use the last one ... but it
could also be the first one, all, a user specified or whatever else
seems feasible.
Ulf
next prev parent reply other threads:[~2010-11-15 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 12:43 Store link in message mode Ulf Stegemann
2010-11-15 15:17 ` Tassilo Horn
2010-11-15 16:00 ` Ulf Stegemann [this message]
2010-11-16 13:22 ` Łukasz Stelmach
2010-11-17 14:29 ` Tassilo Horn
2010-11-20 19:05 ` Łukasz Stelmach
2011-02-08 16:00 ` Bastien
2011-02-09 14:41 ` Ulf Stegemann
2011-02-09 16:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=zf.upnwroea86w.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.