Gnus development mailing list
 help / color / mirror / Atom feed
From: Helmut Waitzmann <nn.throttle@xoxy.net>
To: ding@gnus.org
Subject: Re: Delayed messages, postponing Date: until sending by default?
Date: Mon, 23 Mar 2020 03:51:58 +0100	[thread overview]
Message-ID: <87tv2f4wbb.fsf@helmutwaitzmann.news.arcor.de> (raw)
In-Reply-To: <87imiyyikr.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net>:
>Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> Amin Bandali <mab@gnu.org> writes:
>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>>> Adam Sjøgren <asjo@koldfront.dk> writes:
>>>>>
>>>>>> Recently I read a blog post about delayed messages in Gnus: 
>>>>>>
>>>>>>
>>>>>>  · https://tech.toryanderson.com/2020/02/21/emacs-gnus-delay-schedule-email-sending/
>>>>>>
>>>>>> And I could help myself nerdsplaining the configuration I use for 
>>>>>> delayed messages.
>>>>>>
>>>>>> One of the things is: 
>>>>>>
>>>>>>
>>>>>>   ; Remove date, so delayed messages (C-c C-j) don't get a date until
>>>>>>   ; sent, from <mailman.1180.1266014215.14305.info-gnus-english@gnu.org>:
>>>>>>   (setq message-draft-headers '(References From))
>>>>>
>>>>> Huh, I didn't realize that the Date header was set as 
>>>>> time-of-delay, not time-of-send. Confirming for myself by 
>>>>> delaying this message by a day. No harm done, as it is 
>>>>> totally useless!
>>>>
>>>> Huh, no kidding. I can't think of any reason we'd want to 
>>>>send delayed messages out with the original Date header...
>>>
>>> +1; I think it would be a more sensible default to use the 
>>>Date of send. I think it can be especially confusing for the 
>>>receiver seeing a message dated, say, 1 day before, but only 
>>>just appearing in their inbox.
>>
>> And even with regular (non-delayed) drafts, why would we want 
>>to date it from when we *started* writing the message, rather 
>>than when we sent it?
>>
>> I've opened bug#40151 for this.
>
>And it's in!

Is it possible for the user to select the other behavior: send a 
message with the date when the message was finished writing?  If 
not, I'd beg not to change that. 

On the other hand:  If I want to send a message with the date of 
sending rather than writing, I just save it as a draft.  Then, 
before sending, I reedit the message to get the current date. 

Adhering to the general principle: provide mechanism not policy – 
I'd like to select the policy for myself. 



  parent reply	other threads:[~2020-03-23  2:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 22:46 Adam Sjøgren
2020-03-19 23:01 ` Eric Abrahamsen
2020-03-20 16:42   ` Eric Abrahamsen
2020-03-20 16:57     ` Amin Bandali
2020-03-20 17:14       ` Eric Abrahamsen
2020-03-20 18:41         ` Eric Abrahamsen
2020-03-20 18:50           ` Amin Bandali
2020-03-20 18:57             ` Lars Ingebrigtsen
2020-03-23  2:51           ` Helmut Waitzmann [this message]
2020-03-23  4:41             ` Eric Abrahamsen
2020-03-23  8:20               ` Robert Pluim
2020-03-23 18:43                 ` Eric Abrahamsen
2020-03-24 15:09                   ` Robert Pluim
2020-03-24 20:09                     ` Eric Abrahamsen
2020-03-25  0:13               ` Helmut Waitzmann

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=87tv2f4wbb.fsf@helmutwaitzmann.news.arcor.de \
    --to=nn.throttle@xoxy.net \
    --cc=ding@gnus.org \
    --cc=oe.throttle@xoxy.net \
    /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.
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 NNTP newsgroup(s).