Hello Ryan! Well thanks for continuing from the IRC.
One thing first, dear Ryan: S-nail v14.9.24 can *not* be used for git-send-email, your message bounced for the RedHat subscribers. The problem is that two "Date:" header fields will be sent over the net, and strict servers actually really reject those messages. (Fun fact, maybe: a couple of years ago all GNU emails had two From: header fields i think it was, at least for some time period. I think Postel's law .. but .. well. It is like it is.) So: you can use "format-patch -M" and then send the output, but direct send-email is unreliable due to two Date: header fields. Sorry for this. Ryan Matthews via S-mailx wrote in <[email protected]>: |From: Ryan Matthews <[email protected]> | |Now you can figure out how to clear a saved message state by searching |for "saved" in the manpage. Regarding your patch it must be said that there was tremendous work also on the manual in the six years since the v14.9 series, initiated (also) by Ashton Fagg (who gave a very good and appreciated style impetus). In the meantime i came back to your issue several times, commit nail.1: clarify *hold*/*keepsave*, `hold'/`mbox'/`touch' (Ryan Matthews) on the development branch is the current state. The current manual talks in "Reading mail, and more on interactive mode" († are links) Automatic message moving: out of HISTORY† there is a notion of a primary system mailbox†, and a secondary mailbox†. The former are inbox†, MAIL†, and all folder†s (also via -f†) opened with ‘%:’ prefix, the latter is MBOX†. When leaving a primary mailbox, (also via normal program termina‐ tion, quit†) dependent upon Message states†, which there can also be en‐ forced or overwritten with the COMMANDS† hold†, mbox†, touch†, automatic deletion and moving happens dependent on the settings of hold†, keep†, keepsave†. Deviating from the standard these are set†, so automatic mes‐ sage moving does not occur. Manually move†ing or copy†ing messages is possible, write† saves selected message parts. ... hold (ho) Also preserve (pre); Allowed only in a primary system mailbox†. Marks the given message list to be preserved in the current folder†, as if hold† were set; overrides a former dele‐ tion of the given messages; only the delete†, dp†, dt† as well as mbox† and touch† commands will remove the preserve mark. ... mbox (mb) Allowed only in a primary system mailbox†. Mark the given message list as a subject to automatic message moving† to the secondary mailbox† MBOX†, overriding a set hold†; overrides a former hold† request. ... touch (tou) Allowed only in a primary system mailbox†. Touch the given message list, and mark messages therein as a subject to automatic message moving† to the secondary mailbox† MBOX†, un‐ less overriden by a set hold†; overrides a former hold† re‐ quest. (Here one hold is a variable, the other a command, which can be seen in the man(1)ual view via different font attributes.) |--- | nail.1 | 4 ++++ | 1 file changed, 4 insertions(+) | |diff --git a/nail.1 b/nail.1 |index b7363fe2..94689020 100644 |--- a/nail.1 |+++ b/nail.1 |@@ -5139,6 +5139,10 @@ or the last message restored, respectively, \ |is automatically | d; also see | .Ic dp , | .Ic dt . |+This also clears the |+.Ql saved |+state of the messages in question. See the section |+.Sx "Message states" . I will add it slightly adjusted (the patch does not apply). I also think the current "Message states" text does not elaborate enough. Thanks again, Ryan! --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
