From: Sebastian Rose <sebastian_rose@gmx.de>
To: lukasz.stelmach@iem.pw.edu.pl
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Sending org-mode nodes
Date: Thu, 19 Nov 2009 12:12:30 +0100 [thread overview]
Message-ID: <87skca93a9.fsf@gmx.de> (raw)
In-Reply-To: <87hbsqu86y.fsf@dasa3.iem.pw.edu.pl> (lukasz stelmach's message of "Thu, 19 Nov 2009 11:20:53 +0100")
lukasz.stelmach@iem.pw.edu.pl writes:
> David Maus <maus.david@gmail.com> writes:
//....//
> - Message-ID derived from node's ID. This would be quite useful for
> associating replies with original notes/nodes.
In that case, each mail sent from the subtree would have the same
message-ID, which is invalid, since the ID is made to identify a certain
email. It's supposed to be world wide unique for at least two years.
Your provider would replace your (probably invalid) ID anyway.
> These are of course my whishful thoughts, especially the one with
> Old-Sent-To. I think, however, that org-mode with them implemented would
> be even greater tool than it is today.
I believe it's not implemented, because it's easy to just
C-c @
C-x m
Enter addresses (bbdb helps a lot here)
DOWN DOWN DOWN DOWN
C-y
evtl. edit the contents
C-c C-C
There's simply no need to implement it for Gnus users.
Emacs+Org+bbdb+Gnus implement it already.
Sebastian
next prev parent reply other threads:[~2009-11-19 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 16:46 Sending org-mode nodes lukasz.stelmach
2009-11-19 8:43 ` David Maus
2009-11-19 10:20 ` lukasz.stelmach
2009-11-19 11:12 ` Sebastian Rose [this message]
2009-11-19 13:56 ` lukasz.stelmach
2009-11-19 14:51 ` Sebastian Rose
2009-11-19 15:54 ` Bernt Hansen
2009-11-19 16:50 ` Łukasz Stelmach
2009-11-19 17:03 ` Łukasz Stelmach
2009-11-19 18:22 ` Sebastian Rose
2009-11-20 13:35 ` Łukasz Stelmach
2009-11-20 22:38 ` Sebastian Rose
2009-11-19 15:23 ` Eric Schulte
2009-11-19 17:26 ` Eric Schulte
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=87skca93a9.fsf@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=lukasz.stelmach@iem.pw.edu.pl \
/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.