Huhu!
Michael Convey <[email protected]> wrote:
|`NU *HMFATK+-J' attributes because I was able to get the '\
|H' flag to appear by entering 'ho2' (for message 2). Howev\
|er, my 'SYSV3' environment variable
|is not set and and I've not set the 'bsdflags' binary opti\
|on. So I'm not sure why it uses 'H' instead of 'P' for hol\
|d/preserved. Any thoughts on this?
|* 'M' - 'mboxed' according to the S-nail manual. Skipped\
| because it may not be applicable to my environment.
Yes i have added a standards issue since `mbox' only works in
system mailboxes (where you get at with "file %").
Maybe i add support for generic `mbox' for v14.9 (S-nail).
|* 'K' - I was able to kill and unkill a specific messag\
|e via k# and unkill#, but killed messages disappear, so I \
|wasn't able to view the 'K'
|attribute. Any way to view this to verify it?
Martin Neitzel prodded something in August 2014 (and it was in
TODO already iirc) so i've added support for the :d search
modifier for v14.9, i.e. "from :d" should show you the deleted
messages.
|* '-' - 'collapsed' according to the S-nail manual. Ca\
|n't get this to appear -- thoughts?
The thread code never made it and i don't do this before v15
(S-nail). You can get this by editing cmd1.c:dispc() (_dispc() in
S-nail) and changing
if (mb.mb_threaded == 1 && mp->m_collapsed > 0)
dispc = a[12];
if (mb.mb_threaded == 1 && mp->m_collapsed < 0)
dispc = a[11];
to
if (mb.mb_threaded == 1) {
if (mp->m_collapsed < 0)
i = a[10];
else if (mp->m_collapsed >= 0 && mp->m_child != NULL)/* TODO ==0 */
i = a[11];
}
The latter would be S-nail -- for Heirloom use a[11] and a[12],
respectively. Note it overwrites the other attributes, which is
why i think Gunnar didn't enable it. On the other hand
m_collapsed cannot be >0 if i understand the thread code (never
really looked yet) correctly, so i may presume wrong.
|* '*' - I was able to get this flag to appear, but I do\
|n't know how. Which command will make this flag appear?
http://sdaoden.users.sourceforge.net/code-nail.html#351
documents *attrlist*.
Please note that in general we are talking about a very old
codebase that in large parts accommodates usage patterns of users
in the seventies and eighties. It has been hacked by many people,
and often little patch by little patch to get things done instead
of looking at the complete picture and going the best way to
improve the overall situation, ending up where desired.
When using this software interactively you have to be capable of
suffering, even more so in Heirloom mailx than S-nail. This
situation will hopefully improve further in the forthcoming years
(after 2017 that is), and i'm thankful for any report and rough
corners or even more so bugs. Yes i'm thankful for users which
nitpick _extremely_ in general, but this software needs a who
lotta love more to be able to serve them.
--steffen
------------------------------------------------------------------------------
_______________________________________________
nail-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nail-devel
