Re: [S-nail] Possible bug in s-nail on timestamp of Dec 31

2016-09-15 Thread Ralph Corderoy 
Hi Donald,

> How do you post correctly. Explain top posting so I can avoid doing
> it.

https://en.wikipedia.org/wiki/Posting_style should explain.  In brief,
it's common to keep just the pertinent bits of the email you're replying
to, "quote" those, I use "> " as do many others, and then intersperse
your reply between those quotes, using them for context to give
clarification and avoiding repeating their content.

But really, people should be forgiving of newcomers that are seeking
help and don't understand the local conventions.  :-)

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

--
__
S-nail-users@lists.sourceforge.net

[S-nail] S-nail v14.9.0-pre1 preview on [master] (backward incompatible!)

2016-09-15 Thread Steffen Nurpmeso 
Hello list!

After about ten months of development i have merged into [master] the
current state of affairs.

  It introduces some **backward incompatibilities**!
  Packagers should be able to find a unified diff file for their
  respective package management attached to this message.

This is a major feature release.
  Preview 1, 2016-09-16:
IMAP gone, better don't ^C during macros.  Misses major
components of the final release.

I didn't know where S-mailx will truly end up with, but only knew
i wanted to overcome the technical shortcomings, have a better
user experience (regarding the software) and that i wanted to
have, e.g., NNTP support.

During development of this release it became clear that the
general usage will be changed, backward incompatibly, and move
towards sh(1)ell style command line usage, that is to say, we will
turn over and will start parsing regular shell tokens, instead of
comma-separated lists, OR space-separated lists or whatever, and
will expand _any_ value content sh(1)ell-compatibly, instead of
not at all in general and only \t and \n in some others etc.

  wysh set a='${TMPDIR}\t/' b="${TMPDIR}\t/" c=$'\${TMPDIR}\t/'
  echo a=$a b=$b c=$c
  a=${TMPDIR}\t/ b=/tmp\t/ c=/tmp /
..
  set a='${TMPDIR}\t/' b="${TMPDIR}\t/" c=$'\${TMPDIR}\t/'
  echo a=$a b=$b c=$c
  a=${TMPDIR}\t/ b=${TMPDIR}\t/ c=$\${TMPDIR}\t/

(But don't do that).  All this is documented in COMMANDS#?.
Today only new commands (like `bind', `customhdr' etc.), but also
attachment selection, `remove' and `write' use this, others, like
`set', can optionally support it with a new command prefix: `wysh'.

  Remarks:
  However, this enlightenment came late, in Spring 2016.  A number
  of internal code flows etc. have been developed without this
  knowledge, which is why the release will take some more time:
  i want to rewrite all that with the real destination in mind.
  The user interface of all new facilities etc. is however both,
  stable and upward-compatible.  It is only about internal
  interfaces and code flow.

Credits, in order of commit appearance: Antonio Radici,
Aharon Robbins, Mike Frysinger, Predrag Punosevac, Michael Convey,
Hariskar, Rudolf Sykora, Martin Neitzel, Gavin Troy,
Salvatore Bonaccorso, Todd C.  Miller, Sergey Matveev, Robert Elz,
Mantas Mikulėnas, Respiranto, Jens Schleusener,
Walter Alejandro Iglesias, Ralph Corderoy, Thomas Dickey, Afan,
Justin Ellingwood, Ingo Schwarze, Viktor Szépe, Gaetan Bisson,
Juan RP, William Yodlowsky, Hilko Bengen, Matthew Dillon,
Colin Watson and Donald Mugnai.

We welcome Antonio Radici, Mike Frysinger, Predrag Punosevac,
Michael Convey, Rudolf Sykora, Todd C. Miller, Robert Elz,
Jens Schleusener, Walter Alejandro Iglesias, Thomas Dickey, Afan,
Justin Ellingwood, Viktor Szépe, Juan RP, Matthew Dillon,
Colin Watson and Donald Mugnai in THANKS.

Apologies: Sergey Matveev.  Members of the Roff community which await
progress.

  In the following numbers in [] reference a commit hash or a topic
  branch name.  mdocmx(7) anchors are denoted by a number-sign #:
  typing "^A ANCHOR" while reading the man(1)ual in a capable less(1)
  will scroll to the manual's Point-Of-Interest, and pointing a web-
  browser to the "#ANCHOR" of the online manual will do so, too.
  Commits can be browsed by appending the commit hash to
https://git.sdaoden.eu/cgit/s-nail.git/commit/?id=

NOTES, ChangeLog (packager-affine)
^^

* This release brings backward incompatibilities, especially for
  packagers and interactive use cases!

  + Anything which was WANT_xy before is now OPT_xy, and
compiled-in paths and values, like PREFIX or PAGER, have
gained a VAL_ prefix (thus VAL_PREFIX and VAL_PAGER).

This is _not_ true for non-persistent or environmental values,
e.g., DESTDIR, CC, etc, and also not for the overwritable
program variables during configuration, e.g., $awk.

  + SENDMAIL -> VAL_MTA, SENDMAIL_PROGNAME -> VAL_MTA_ARGV0,
MAILSPOOL -> VAL_MAIL.

  + The make system now needs config..build..install or
all..install or tangerine (config..build..test..install).

  + The `build' phase can be parallelized by setting the MAILJOBS
environment variable, e.g., "make MAILJOBS='-j 4' build".
(Gaetan Bisson)

  + Set the new OPT_CROSS_BUILD to avoid feature runtime tests,
only compile- and link-availability will be tested.  (Juan RP)

  + VERBOSE is implemented straight, but must be given at
configuration time in order to become honoured.
(William Yodlowsky)

  + ADDCFLAGS / ADDLDFLAGS -> EXTRA_CFLAGS / EXTRA_LDFLAGS

  + The LD_LIBRARY_PATH etc. building processes will skip any path
which contains the string "fakeroot".  (Hilko Bengen)

  + We honour a set SOURCE_DATE_EPOCH environment variable.
[df4954c]  (reproducible-builds.org; Colin Watson)

  + Packagers should have received diffs against v14.8.10
packaging files.

  + These are upward compatible changes.

- To support RFC 1524 a.k.a.

Re: [S-nail] Possible bug in s-nail on timestamp of Dec 31

2016-09-15 Thread Steffen Nurpmeso 
Ralph Corderoy  wrote:
 |BTW, I suspect the "Dec 31" are in 1969 and the time was zero seconds
 |past the Unix epoch, viewed offset by a negative timezone.

Ah, i see!

  ?0[steffen@wales nail.git]$ >> MTA: /usr/sbin/sendmail, arguments: sendmail -i -- h@a
  s-nail: >>> Date: Wed, 31 Dec 1969 19:00:00 -0500
  s-nail: >>> To: h@a
  s-nail: >>> Subject: test
  s-nail: >>> User-Agent: s-nail v14.8.10-364-g4492d1c
  s-nail: >>> 

An Apple a day keeps the Doctor away!

--steffen

--
__
S-nail-users@lists.sourceforge.net

Re: [S-nail] Possible bug in s-nail on timestamp of Dec 31

2016-09-15 Thread Donald Mugnai 
How do you post correctly. Explain top posting so I can avoid doing it.


Donald Mugnai
1 Watermill Place Unit 124
Arlington MA 02476
donaldmug...@gmail.com

On Thu, Sep 15, 2016 at 9:40 AM, Steffen Nurpmeso 
wrote:

> Hey.
>
> Please don't top-post on this list, it is really something ugly to
> do, imho.  That would be nice.  If you really want to include the
> entire message you respond to, you could set the internal S-nail
> variable *quote-as-attachment*, for example.  ^.^
>
> Donald Mugnai  wrote:
>  |How do you "configure the way the headline is displayed with the
> variable \
>  |of the same name[1]" In the s-nail.rc file? All I want to get is a
> correct
>  |timestamp for my messages instead of Dec 31.  Is this a configuration \
>  |issue? If so, what do you configure? What is name[1]? Thanks
>
> Weeell, after all i mean that if you read the manual ("$ man mail"
> or "$ man s-nail") at least a bit you would know about s-nail and
> settings -- i think "A starter" should be sufficient for this, as
> it "already bends those standard settings a bit towards more user
> friendliness and safety" in s-nail.rc.  And if you look in
> s-nail.rc then you see comments and the `set' command and how it
> sets variables.
>
> This makes me think that my words "if you actually set the
> datefield variable the Date: message header is used" should give
> you the right hint, and i have shown the complete command in my
> second response.
> Baby belly, baby belly.  Maybe the wording could be even simpler,
> and in the other window i have added some more explicit `set'
> references (as opposed to the plain word "Set"/"set") already in
> the Options section of the manual, but in general i think the
> wording hurdles are almost as low as they can get.
>
> For example, on Monday i made a bicycle tour and came along
> a pasture where a cow just had given birth to a young son, just
> a few seconds ago.  She was licking him dry etc.  So i stood there
> for the quarter of an hour until he stood up the first time.  But
> no.. actually not.  He fell pretty fast, and the mother looked
> at me somewhat enraged when i left the scene.  Actually i just
> drove to the other end of the pasture to say hello to the rest
> of the flock, and saw from there his first real standing.
> So i had to get back to this yesterday, and this young man
> actually had a real trauma! and ran, just two days old!, to
> overcome that i left when he was still lying!!  I really hope we
> did that fantastic boy!  He's right!  Yeah!!
>
> So you are saying i should offer wording for humans which have an
> intellectual capacity of less than a 20 minutes to 48 hours old
> young bull?  No, no i don't think i will do that.
>
> --steffen
>
--
__
S-nail-users@lists.sourceforge.net

Re: [S-nail] Possible bug in s-nail on timestamp of Dec 31

2016-09-15 Thread Ralph Corderoy 
Hi Donald,

BTW, I suspect the "Dec 31" are in 1969 and the time was zero seconds
past the Unix epoch, viewed offset by a negative timezone.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

--
__
S-nail-users@lists.sourceforge.net

Re: [S-nail] Possible bug in s-nail on timestamp of Dec 31

2016-09-15 Thread Ralph Corderoy 
Hi Donald,

> > How do you "configure the way the headline is displayed with the
> > variable of the same name[1]" In the s-nail.rc file? All I want to
> > get is a correct timestamp for my messages instead of Dec 31.

Does this help?

$ mail
mail version v14.8.10.  Type ? for help.
"/var/spool/mail/ralph": 3 messages 3 unread
>U  1 Ralph Corderoy Thu Sep 15 15:03   14/471
 U  2 Ralph Corderoy Thu Sep 15 15:03   14/471
 U  3 Ralph Corderoy Thu Sep 15 15:03   14/471
? set datefield='%Y-%m-%d %T %z %a'
? set headline='%>%a%m %-18f %29d %4l/%-5o %i%-s'
? h
>U  1 Ralph Corderoy 2016-09-15 15:03:25 +0100 Thu   14/471
 U  2 Ralph Corderoy 2016-09-15 15:03:27 +0100 Thu   14/471
 U  3 Ralph Corderoy 2016-09-15 15:03:28 +0100 Thu   14/471

headline needed altering to use a wider width for %d else datefield's
conversion was truncated.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

--
__
S-nail-users@lists.sourceforge.net

Re: [S-nail] Possible bug in s-nail on timestamp of Dec 31

2016-09-15 Thread Steffen Nurpmeso 
Hey.

Please don't top-post on this list, it is really something ugly to
do, imho.  That would be nice.  If you really want to include the
entire message you respond to, you could set the internal S-nail
variable *quote-as-attachment*, for example.  ^.^

Donald Mugnai  wrote:
 |How do you "configure the way the headline is displayed with the variable \
 |of the same name[1]" In the s-nail.rc file? All I want to get is a correct 
 |timestamp for my messages instead of Dec 31.  Is this a configuration \
 |issue? If so, what do you configure? What is name[1]? Thanks

Weeell, after all i mean that if you read the manual ("$ man mail"
or "$ man s-nail") at least a bit you would know about s-nail and
settings -- i think "A starter" should be sufficient for this, as
it "already bends those standard settings a bit towards more user
friendliness and safety" in s-nail.rc.  And if you look in
s-nail.rc then you see comments and the `set' command and how it
sets variables.

This makes me think that my words "if you actually set the
datefield variable the Date: message header is used" should give
you the right hint, and i have shown the complete command in my
second response.
Baby belly, baby belly.  Maybe the wording could be even simpler,
and in the other window i have added some more explicit `set'
references (as opposed to the plain word "Set"/"set") already in
the Options section of the manual, but in general i think the
wording hurdles are almost as low as they can get.

For example, on Monday i made a bicycle tour and came along
a pasture where a cow just had given birth to a young son, just
a few seconds ago.  She was licking him dry etc.  So i stood there
for the quarter of an hour until he stood up the first time.  But
no.. actually not.  He fell pretty fast, and the mother looked
at me somewhat enraged when i left the scene.  Actually i just
drove to the other end of the pasture to say hello to the rest
of the flock, and saw from there his first real standing.
So i had to get back to this yesterday, and this young man
actually had a real trauma! and ran, just two days old!, to
overcome that i left when he was still lying!!  I really hope we
did that fantastic boy!  He's right!  Yeah!!

So you are saying i should offer wording for humans which have an
intellectual capacity of less than a 20 minutes to 48 hours old
young bull?  No, no i don't think i will do that.

--steffen

--
__
S-nail-users@lists.sourceforge.net