bug#35249: Allow easier customization of message-unique-id

bug#35249: Allow easier customization of message-unique-id

[積丹尼 Dan Jacobson]

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

bug#35249: Allow easier customization of message-unique-id

[Robert Pluim]

>>>>> 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

bug#35249: Allow easier customization of message-unique-id

[積丹尼 Dan Jacobson]

>>>>> "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.

bug#35249: Allow easier customization of message-unique-id

[Lars Ingebrigtsen]

積丹尼 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

bug#35249: Allow easier customization of message-unique-id

[積丹尼 Dan Jacobson]

Maybe in the docstring mention approved safe ways to "advise" this
function that the user can use to e.g., get the.......OK never mind. geez.