Re: [Nmh-workers] IPv6-ifying nmh

://lists.nongnu.org/mailman/listinfo/nmh-workers -- Jeffrey C. Honig j...@honig.net http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml ___ Nmh-workers mailing list Nmh-workers@nongnu.org http://lists.nongnu.org/mailman/listinfo/nmh

Re: [Nmh-workers] 128 byte field name limit in NAMESZ breaks scan(1)

:, another topic. Other than that, it's not as invasive a patch as I'd feared it might be, but I still vote to put it on ice until we have some decent tests. Yes, testing good. Can the OP send me one of the messages that had issues? Thanks (谢谢). Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http

Re: [Nmh-workers] 128 byte field name limit in NAMESZ breaks scan(1)

What's the consensus, ware we ``good enough'' with increasing NAMESZ? Or should I do some testing on the dynamic reallocation? Thanks (谢谢). Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml

Re: [Nmh-workers] 128 byte field name limit in NAMESZ breaks scan(1)

= ___ Nmh-workers mailing list Nmh-workers@nongnu.org http://lists.nongnu.org/mailman/listinfo/nmh-workers -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml

Re: [Nmh-workers] 128 byte field name limit in NAMESZ breaks scan(1)

Peter Maydell [EMAIL PROTECTED] wrote: Jeffrey C Honig wrote: If I read RFC0822 correctly field-name does not have a length limit, it's one or more characters. Given that, using a fixed value of NAMESZ in m_getfld() is an invalid assumption. 2822 says that lines MUST be no longer than 998

Re: [Nmh-workers] 128 byte field name limit in NAMESZ breaks scan(1)

, but that was years ago), only did some relevant searches. Thanks (谢谢). Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml ___ Nmh-workers mailing list Nmh-workers@nongnu.org http

Re: [Nmh-workers] nmh-1.3-RC2 uploaded

an [EMAIL PROTECTED], but the lack of archive suggests that it's never had any posts; I wonder if it has any subscribers? :-) Also include [EMAIL PROTECTED] Thanks (谢谢). Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml

[Nmh-workers] Problem trying to build nmh from CVS on ubuntu fiesty

with the -V w/o an argument. Or did I forgot to install some Ubuntu package? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml ___ Nmh-workers mailing list Nmh-workers

Re: [Nmh-workers] Problem trying to build nmh from CVS on ubuntu fiesty

Matthew Hannigan [EMAIL PROTECTED] wrote: On Sun, Apr 29, 2007 at 07:36:20PM -0400, Jeffrey C Honig wrote: I followed the directions in docs/README.developer (autoheader, ...). ...o Do you know that nmh is available in Feisty already? Yes. But it segfaults on all the commands I tried

[Nmh-workers] Additional subject prefixes to ignore

to append to the list and possibly -nosprefix to reset the list (to just re:). Comments? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml ___ Nmh-workers mailing list Nmh

Re: [Nmh-workers] Additional subject prefixes to ignore

expressions is more than I want to take on at the moment. Yeah, I'm chicken, I admit it. Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml ___ Nmh-workers mailing list Nmh

Re: [Nmh-workers] Additional subject prefixes to ignore

POSIX regex? 2) If we add some code that uses POSIX regex, we should update pick to be consistent. Does the code in picksbr use the same syntax as the POSIX code? 3) This is going from a two hour enhancement to a multi-day enhancement and cleanup. Thanks. Jeff -- Jeffrey C. Honig

Re: [Nmh-workers] nmh-1.1-RC4 post /tmp/,LCK.* problem

/null is a useful and not unknown feature. Any ideas on how we can insure this continues to work? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml ---End Message--- -- Jeffrey C. Honig [EMAIL PROTECTED] http

Re: [Nmh-workers] nmh-1.1-RC4 post /tmp/,LCK.* problem

[EMAIL PROTECTED] wrote: Jeffrey C Honig wrote: When running under mh-e, I set the MHCONTEXT environment variable to /dev/null. This prevents my mh-e context from confusing my command line context. With 1.1 this breaks things. We could allow MHCONTEXT=/dev/null with the following

Re: [Nmh-workers] multiple folders to rcvstore

of the message, or just the first one. Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml ___ Nmh-workers mailing list Nmh-workers@nongnu.org http://lists.nongnu.org/mailman/listinfo

Re: [Nmh-workers] Questionable code - the bigger picture

to create /dev/null.lck or something like that), but if you turn on real locking it works fine. Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml ___ Nmh-workers mailing list

Re: [Nmh-workers] nmh-1.1rc2

: creating config.h config.status: error: cannot find input file: config.h.in I built with: automake ./configure Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml