* bug#35249: Allow easier customization of message-unique-id
@ 2019-04-12 16:07 積丹尼 Dan Jacobson
2019-04-14 10:18 ` Robert Pluim
2019-05-13 19:48 ` Lars Ingebrigtsen
0 siblings, 2 replies; 5+ messages in thread
From: 積丹尼 Dan Jacobson @ 2019-04-12 16:07 UTC (permalink / raw)
To: 35249
As concat
".fsf"
is hardwired into message-unique-id, I had to redefine the entire
function, just to make that instead into
"." (substring (system-name) -1 nil) ".fsf"
So do consider allowing the user to customize this easier.
Gnus v5.13
GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.4)
of 2019-02-03, modified by Debian
^ permalink raw reply [flat|nested] 5+ messages in thread* bug#35249: Allow easier customization of message-unique-id
2019-04-12 16:07 bug#35249: Allow easier customization of message-unique-id 積丹尼 Dan Jacobson
@ 2019-04-14 10:18 ` Robert Pluim
2019-04-16 3:35 ` 積丹尼 Dan Jacobson
2019-05-13 19:48 ` Lars Ingebrigtsen
1 sibling, 1 reply; 5+ messages in thread
From: Robert Pluim @ 2019-04-14 10:18 UTC (permalink / raw)
To: 積丹尼 Dan Jacobson; +Cc: 35249
>>>>> On Sat, 13 Apr 2019 00:07:54 +0800, 積丹尼 Dan Jacobson <jidanni@jidanni.org> said:
Dan> As concat ".fsf" is hardwired into message-unique-id, I had
Dan> to redefine the entire function, just to make that instead
Dan> into "." (substring (system-name) -1 nil) ".fsf" So do
Dan> consider allowing the user to customize this easier.
So would a simple string suffice? Or would you want to be able to run
arbitrary lisp code to generate it?
Robert
^ permalink raw reply [flat|nested] 5+ messages in thread* bug#35249: Allow easier customization of message-unique-id
2019-04-14 10:18 ` Robert Pluim
@ 2019-04-16 3:35 ` 積丹尼 Dan Jacobson
0 siblings, 0 replies; 5+ messages in thread
From: 積丹尼 Dan Jacobson @ 2019-04-16 3:35 UTC (permalink / raw)
To: 35249
>>>>> "RP" == Robert Pluim <rpluim@gmail.com> writes:
RP> So would a simple string suffice? Or would you want to be able to run
RP> arbitrary lisp code to generate it?
Well all I know is I want to use the same .emacs file on multiple
machines, and have the last number of that machine put into the
Message-ID, so that's why I used
> (substring (system-name) -1 nil) ".fsf" So do
So OK my code ran only once when emacs started. But maybe someone would
want to generate slightly different message IDs when sending to e.g.,
Snowden vs. Putin, so OK, the latter.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#35249: Allow easier customization of message-unique-id
2019-04-12 16:07 bug#35249: Allow easier customization of message-unique-id 積丹尼 Dan Jacobson
2019-04-14 10:18 ` Robert Pluim
@ 2019-05-13 19:48 ` Lars Ingebrigtsen
2019-05-13 23:48 ` 積丹尼 Dan Jacobson
1 sibling, 1 reply; 5+ messages in thread
From: Lars Ingebrigtsen @ 2019-05-13 19:48 UTC (permalink / raw)
To: 積丹尼 Dan Jacobson; +Cc: 35249
積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
> As concat
> ".fsf"
> is hardwired into message-unique-id, I had to redefine the entire
> function, just to make that instead into
> "." (substring (system-name) -1 nil) ".fsf"
> So do consider allowing the user to customize this easier.
I think it's fine to redefine that function if you absolutely have to
have a different Message-ID. It's not something that any user should
worry or care about, so I don't see any reason to allow customisation
beyond that.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-05-13 23:48 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-04-12 16:07 bug#35249: Allow easier customization of message-unique-id 積丹尼 Dan Jacobson
2019-04-14 10:18 ` Robert Pluim
2019-04-16 3:35 ` 積丹尼 Dan Jacobson
2019-05-13 19:48 ` Lars Ingebrigtsen
2019-05-13 23:48 ` 積丹尼 Dan Jacobson
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).