Hi,
I wrote:
> https://www.mhonarc.org/archive/cgi-bin/extract-mesg.cgi?a=nmh-workers=2017-11=20171119004244.DA4E6A19F9%40pb-smtp2.pobox.com
>
> To: nmh-announce: ;@zimbra.mallorn.com, nmh-workers@nongnu.org
>
> So different, but still weird different.
Bug raised on the mhonarc mail
Hi,
I wrote:
> I've triggered it myself at pair.com. An empty group address isn't
> sufficient; it needs to be followed by another address. Still
> perfectly valid under RFC 2822.
>
> Tx'd: To: group-name: ;, ra...@example.com
> Rx'd: To: group-name: ;, ""@ruis.pair.com,
Hi Ken,
> The last test ("cleanup") deletes the entire test directory.
Yes, it does
rm -rf "${MH_TEST_DIR}"/.w3m
rm -rf "${MH_INST_DIR}"
so typically
rm -rf test/testdir/.w3m
rm -rf test/testdir/inst # Temporary `make install' destination.
> But if you run "make check
Hi David,
> > > Yes, that's it. slocal's split() splits on whitespace and commas:
> >
> > So tee(1) is unhappy with its arguments.
> >
> > execve("/usr/bin/tee", ["/usr/bin/tee", "/tmp/",
> > "A/nmh-1.7/test/testdir/6459.actu"...],
>
> This isn't the fault of tee.
No, sorry, I
Hi David,
> Yes, that's it. slocal's split() splits on whitespace and commas:
So tee(1) is unhappy with its arguments.
execve("/usr/bin/tee", ["/usr/bin/tee", "/tmp/",
"A/nmh-1.7/test/testdir/6459.actu"...],
0x55f2babaff00 /* 3 vars */) = 0
To keep the test outputs
Hi Norm,
I recreated your `make check' error, with the 1.7 tar file, but had to
unpack the tar file inside `/tmp/,A' to do so based on a hunch.
Can you try unpacking it into /tmp/AA, for example.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
--
Nmh-workers
Hi Ken,
> we never really standardized on it so I can't really fault the
> previous naming
Agreed. Not everything I write is a complaint. :-)
> I see no reason not to; I say go ahead!
OK, done that for 1.{2..4}, including matching the original tags' dates.
200 nmh-1_0
Hi again Ken,
> What did you write? I'm guessing the perfectly valid `nmh-announce:
> ;'?
I've triggered it myself at pair.com. An empty group address isn't
sufficient; it needs to be followed by another address. Still
perfectly valid under RFC 2822.
Tx'd: To: group-name: ;,
Hi Ken,
> I am pleased to announce the long-awaited release of nmh 1.7!
Well done. That's me switching back to running git now the other guinea
pigs have arrived. :-)
I was looking at git's tags, and how the convention has changed over
time.
$ for t in `git tag`; do
> printf '%6d
Hi,
> The branch, master has been updated
>via 8f802697c8d9c4fc52e4d0ce4facf643358aac1a (commit)
...
Well, that's annoying. I've pushed to the wrong (default) place last
thing yesterday. I intended to push to a build-and-test machine; and
did actually start the build on it. I've
Hi Ken,
> I was hoping to hear back from Kevin Cosgrove about that bug he
> reported for the test suite, but it doesn't seem like that's going to
> happen. So, anything else people want to see in 1.7 before it gets
> released?
Nothing here. I thought I had a man-page update, but after
Hi Valdis,
> "git mv" has you covered.
OK.
> "foo_del.c has merged with foo.c in the next."
>
> Best practice here is to generate a commit that *only* does
> the merge (plus any #include surgery, etc to make a clean compile),
> and explain it was a code migration in the commit comment.
Right.
Hi,
I'm in the Augean process of creating .h interface files for each of the
.c implementation files, depleting h/prototypes.h of content along the
way, to help show the dependencies between the modules. Something
that's obvious before and during is there's too many one-function C
files, often
Hi Valdis,
> > real0m1.184s
> > user0m0.599s
> > sys 0m0.585s
> >
> > Both have had the command previously run recently, but then
> > manipulation of an nmh folder tends to keep the interesting data in
> > memory.
>
> Yeah, the pain is in the cache-cold state. Especially
Hi Ken,
> BTW, it turns out it takes on average 0.66 seconds to append a message
> to a Gmail mailbox
So refiling the half a dozen emails that are a thread I've just finished
with would be about six seconds because that's appending? (I don't know
IMAP.)
> (tls-encrypted) => A2 SELECT "Enron"
Hi Valdis,
> > This topic popped up at the end of August, and a few years back when
> > Ken wanted to "garbage collect" it; Lyndon then said he made use of
> > it to spot identical parts across emails.
>
> Do enough MUAs/people generate the header for it to be useful for that
> purpose?
I
Hi Valdis,
> Given the deprecated nature of MD5, should we keep this around? When
> was the last time one of these was seen in the wild?
My .mh_profile specifies -check for a bunch of programs so Content-MD5
appears if I MIME-process an email, e.g. `forw -mime'. I don't rely of
it for
Hi,
Ken wrote:
> I think it would be VERY easy to write a simple tool which just opened
> a connection to your IMAP server, ran the IDLE command, waited for
> updates from the IMAP server and simply ran a script when it got new
> mail
There are heavyweights that do this, e.g.
Hi David,
> Fedora maintains its own spec,
> http://pkgs.fedoraproject.org/cgit/rpms/nmh.git/tree/nmh.spec
Ah, and that still has the "If you want to use nmh as a true email user
agent, you'll want to also install exmh to provide a user interface for
it". :-( I was hoping to get that altered
Hi David,
> One change that I'm not fond of: I think that "command line
> interface" should appear in the summaries. It's been that way in the
> Fedora spec since its beginning in 2005. And I think it more
> effectively conveys one of the advantages of nmh.
OK.
commit
Hi Kevin,
> I've packaged exmh for fedora and would be happy to share my spec
> file.
Sounds good, but that's more for
https://www.redhat.com/mailman/listinfo/exmh-workers :-)
I've pushed a change and mention both xmh and exmh as "external
projects" without stating either is available as a
Hi,
I'm tinkering with SPECS/nmh.spec and SPECS/nmh.cygport, in particular
removing the statement a GUI is required if nmh is to be used as one's
main MUA. :-)
nmh.cygport's description suggests the xmh package, and that does exist
in Cygwin, but I don't think exmh is packaged? And nmh.spec,
Hi Ken,
> But maybe you're bandwith-limited
Yes, in this large case. I can observe `ip -s a show dev ens35' before,
during, and after, and see it causes RX'd bytes to shift from idle to
full pelt.
The frequency of the timestamps of the network packets show they're
fairly even.
3
Hi Valdis,
> 0 [~] time bash -c '(scan +linux-kernel 1-10426 > /dev/null)'
>
> real 0m17.625s
> user 0m1.610s
> sys 0m3.358s
What does `scan -version' give?
Is 1-10426 actually 10,426 emails? :-)
If you have grep(1) read the files up to the end of the headers instead,
does it still take as
Hi Ken,
> I'd be interested why this variance occurs. You would think for the
> same mailbox it would always be the same.
The tests with that public IMAP server are presumably accessing content
that it has readily to hand, e.g. in RAM. I suspect a lot of commercial
IMAP servers, e.g. what
Hi Ken,
> > min ms avg max mdev
> >128.2.158.29 120.570 123.153 128.260 2.133
> >128.2.105.45 120.830 136.279 249.528 37.794
> >128.2.158.26 116.089 133.622 180.430 20.598
>
> For 128.2.158.29, I get: 22.161/22.480/22.843/0.216 ms
Repeating
Hi Ken,
> imaptest -host cyrus.andrew.cmu.edu -sasl -saslmech anonymous -user nobody
...
> Connect time: 0.018900 sec
For comparison, what's the `ping -c 10 $ip' statistics from your source
address?
min ms avg max mdev
128.2.158.29 120.570 123.153 128.260
Hi Ken,
> their particular bug is that their account registration email is sent
> as a base64-encoded text/html part (which SHOULD be fine) but rather
> than break the base64 encoding at the recommended 76 characters, it's
> all sent as one line and so an intervening SMTP server is breaking the
>
Hi Ken,
I wish you were a betting man. ;-)
> Ken wrote:
> > and that's the answer I usually get (if I get an answer at all).
...
> Speaking of which, I've emailed Corey.
And Laura and I heard back from Thomas Dohmke, HockeyApp's co-founder,
today saying a fix had been deployed. He's also keen
Hi,
Tom Rodman wrote off-list that he submitted an email to `sendmail -t -oi
-oem' with a To that was a group address with a single email address and
it made it to the destination unharmed.
So I typed SMTP to the local Postfix, giving it a To with two addresses
in a group, and a CC with one.
Hi Ken,
One thought, when perusing offlineimap I noticed it said Gmail doesn't
allow emails to be removed over IMAP in the normal manner. Instead, the
label `\Trash' must be added to move it, allowing Gmail to clean up
later. So not all IMAP servers are created equal, sadly, and that might
be a
Hi Jon,
> > > Don't know if there's anything that can be done about this given
> > > the nature of unicode and all, but I've been getting a lot of spam
> > > recently that looks like this:
> > >
> > > 代开发票。点数优惠。可验证后付款。13651402207叶先生 微信一致
>
> Not saying that it's not unicode, just that it makes a
Hi,
Ken wrote:
> and that's the answer I usually get (if I get an answer at all).
I've got a UK bank and a UK VM provider to fix it so far. Not all their
emails were broken, just ones from particular systems, e.g. the monthly
invoice and receipt. Most of the work is in getting through to
Hi Tom,
> I wanted for example a header like this as seen by a recipient:
>
> To: Membership Committee: pers...@foobar.com, pers...@baz.org ;
>
> to make it clear pers...@foobar.com, and pers...@baz.org are both in
> the "Membership Committee".
Yep, I've wanted that too in the past.
Hi Ken,
> > 代开发票。点数优惠。可验证后付款。13651402207叶先生 微信一致
>
> AFAICT ... that seems to be valid Unicode. I can view it fine and it
> shows up as the appropriate characters.
Same here.
I keep thinking, and then forgetting, that it would be nice to install a
folder of `test card' emails that punters can
Hi,
I don't use slocal(1). I prodded it recently and then observed some
strange behaviour from inc(1) that, given I'm running
1.7-RC3-4-g3dfc049a, had me worried, but it's not an RC3 problem.
Here's it condensed.
$ wc /var/spool/mail/ralph
0 0 0 /var/spool/mail/ralph
$
Hi kre,
> Resources were in limited supply back then, and simply retrying (often
> after a short sleep, though not always required) would often end up
> succeeding
Yes, this was sleep(5) after each failure.
Thanks, they're now all a simple single call to fork().
--
Cheers, Ralph.
Hi,
I fixed a bug today with one of the many copies of a for-loop that calls
fork(2) up to fives times until it succeeds. Ken wondered why we bother
with multiple attempts. It's a good point. Historically, they were
probably vfork(2), but even so... If anyone knows a good reason then
pipe up
Hi Ken,
> > I think a QUIT should be sent after the RSET. I suspect if a QUIT
> > was sent instead then Postfix might then log that a QUIT occurred
> > mid-flow.
I've tried rcpt-to then quit and Postfix 3.2.2-1 here didn't log
anything unusual.
> I think we can change the sm_end() in
Hi Paul,
> i've pushed two commits to master
Thanks.
> i did not augment the test suite.
It already has -prefer tests; they now fail. :-)
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
___
Nmh-workers mailing list
Hi,
I've a packed folder with nine emails and a user sequence called `mid'
for middle. Using pick(1) and tr(1) I blot out those that aren't picked
with `.'s. Here are the results, along with my comments. `R' stands
for a `reserved message name', and `U' for a user sequence.
all
Hi,
I use whatnow-whom a lot and notice Postfix complains.
postfix/submission/smtpd[42]: lost connection after RSET from
orac.inputplus.co.uk[::1]
It's because whom(1), really post(1), sends `RSET, waits for the reply,
and then closes the connection.
Hi Ken,
> > Well, that's the parsing side; making the `/subtype' optional. But
> > the above comment suggests RFC-violating `Content-Type: text' would
> > arrive from ATTMail when they sent to
> > internet!nongnu.org!nmh-workers.
>
> Sure, but ... I'm still trying to understand the difference
Hi Ken,
> I would agree this is easy to miss, and it is confusing at the top of
> the man page where you could definitely read it as saying the whole
> file is a mhbuild composition file, rather than just the body. Maybe
> you'd be willing to add some man page changes for 1.7?
I think 1.7
Hi,
Ken wrote:
> Paul Fox, what say you?
There's also the option of reversing the order, as in my earlier email.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
Hi Ken,
> > Well, at least it does if I'm doing comp, whatnow, mime, edit. If I
> > run mhbuild(1) then it always gives quoted-printable.
> >
> > $ mhbuild -
> > # > a£d
> > w£z
> > MIME-Version: 1.0
> > Content-Type: text/plain; charset="UTF-8"
> > Content-ID:
Hi Ken,
> Where it actually ends up segfaulting is in InitText(). The original
> code from mh-6.8.5 says:
>
> if (!*ci -> ci_subtype) /* XXX: attmail bogosity! */
> ci -> ci_subtype = add ("plain", ci -> ci_subtype);
...
> I guess maybe the idea was you could do:
>
> #
> Without
Hi Ken,
> > mhshow: -prefer text/plain
> >
> > How can I override that to get the default behavior for a single
> > invocation of mhshow?
>
> Hm. It doesn't look like that is currently possible. There should
> have been a -noprefer switch that would zero out the current prefer
> list
Or
Hi Ken,
> > Also, it SEGVs without the `/plain'. Probably because
> > get_ctinfo()'s
> >
> > 685 if (*cp != '/') {
> > 686 if (!magic)
> > 687 ci->ci_subtype = mh_xstrdup("");
> > 688 goto magic_skip;
> > 689 }
>
> You know ... I am
Hi,
I received a bounce for an email to a third party. I wanted to email
them directly, explain what had gone wrong, and pass on the original
message/rfc822 that was part 3 of the bounce email. I comp'd a new
email with a `#message/rfc822 /path/to/42.3.email' only to be told on
`mime'
Hi Ken,
> AFAIK, it's only in our interactions with network protocols like SMTP
> and POP3 that we see CRs because that's the definition.
Right, good.
> text/* that is encoded as base64 should technically include a CRLF. I
> BELIEVE I added the code that will convert that Unix line endings
Hi,
David wrote:
> Ken wrote:
> > Are you recoiling in horror, or think it's a good idea? I can't
> > tell :-)
>
> :-) I think it's a good idea. m_getfld() and its clients are
> difficult to maintain and expand.
It's not so much m_getfld()'s maintenance as getting it working. :-)
I've a
Hi Ken,
> > I figure it helps spot buggy corruption by something that handled
> > the bytes along the way, and I need all the help.
>
> I have to ask ... does that actually HAPPEN? Like, ever?
Only mid edit of code, and the test suite fails then too, since it prods
the various -check options.
Hi Ken,
> And nowadays nmh won't do that unless you specifically tell it to (via
> the -check switch to mhbuild).
I do that. :-) mhlist(1) and others also have -check. mh-chart(7)
lists the -check options, and some of them have the same meaning as
mhstore's and mhlist's.
> because of how
Hi,
exit(3) values are zero for success, non-zero for failure. The value is
eight bits wide but shells map signals onto [0x80, 0xff] so exit(128 +
14) would be ambiguous to the parent.
$ sh -c 'kill -14 $$'
Alarm clock
$ echo $? $(($? - 0x80))
142 14
Shells also nab the top few
Hi Ken,
> > I've reproduced similar symptoms with an mhbuild-produced email
> > where I tacked on CR to the end of every line after the blank line
> > after the headers. IOW, without the headers having CR. However, I
> > still think this is an invalid format email; why should we handle
> > CR
> Here is the information on the file command:
>
> $ file --version
> file-5.16
> magic file from /usr/share/misc/magic
> $ rpm -qf /usr/bin/file
> file-5.16-1.10.mga4
Thanks, jerry. The commit comments on https://github.com/file/file are
poor, but
git log -p FILE5_15..HEAD src/funcs.c
Hi jerry,
> $ file --brief --dereference --mime-type test/mhbuild/nulls
> binary
Could you tell us about that file(1). I found a site for Mageia
packages, but it didn't have one called `file' so I wasn't sure what
package contained the command, and where it got the source from, what
version,
Hi Kevin,
> - To: recipi...@example.com
> - From: sen...@example.com
> - Subject: mhfixmsg pass through on parse error
> - MIME-Version: 1.0
> - Content-Type: multipart/mixed; boundary="- =_aa0"
> -
> - --- =_aa0
> - Content-Type: text/plain; charset="iso-8859-1
> -
Hi David,
Ken wrote:
> The others are likely due to a xhost in your .cshrc/.tcshrc, so I
> think we can ignore them for now.
How about a test that's run at the start of all the test, i.e. before
ali(1)'s, that checks «$SHELL -c 'exit 42'» is silent and sets $? to 42?
If it's not silent then the
Hi Thomas,
> Oh, oops, I clearly didn't look there. How about mentioning in the
> welcome that differences from version 1.6 are noted in
> "$PREFIX/share/doc/nmh/NEWS"
I think that already happens.
$ inc -version
inc -- nmh-1.7-RC3 1.7-RC3-0-g106e6652 built 2017-08-23 19:31:10 + on
Hi Kevin,
Thanks for trying RC3.
> In some of the failures are lines like these in the diff's
>
> + localuser:kevinc being removed from access control list
>
> That's coming from my 'xhost -SI:localuser:kevinc' setting which I use
> exclusively to keep exmh happy. Ironic.
Yes, but where is
Hi Anthony,
> > It looks like you got bit by this change in 1.7, Anthony:
> >
> > - post now defaults to port 587 on 'smtp' message submission.
>
> Thanks. Since the relay only accepts connections from localhost, I was
> okay with adding "send: -port 25 -notls"
In case, like me, you wondered why
Hi everyone,
Ken wrote:
> I am feeling reasonably confident about the quality of nmh 1.7 release
> candidate 3.
I suspect Ken's waters have it right. There's two things you can do to
help. Build nmh on the varying systems you have, even if you only
normally use it on your main one, feeding us
Hi again David,
> ./configure \
> CC='ccache cc' \
> CFLAGS='-g -O3 -std=c99 -pedantic -pedantic-errors -Werror
> -fdiagnostics-color=auto' \
> -C \
It's the -C that's significant.
Without it, the second make doesn't loose _GNU_SOURCE.
But I'd like a cache as it's
Hi David,
> > > Should I cherry-pick that to 1.7-release, also?
> >
> > Please.
I still have problems.
make superclean
./autogen.sh
rm -f config.cache
./configure \
CC='ccache cc' \
CFLAGS='-g -O3 -std=c99 -pedantic -pedantic-errors -Werror
Hi David,
> Any objection to removing "nmh" from before "messages" from at least
> some of these?
...
> Does anyone have time to go through the others?
Doing it now.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
___
Nmh-workers mailing
Hi David,
> configure.ac added -D_FORTIFY_SOURCE to AM_CPPFLAGS. I just changed
> that to CPPFLAGS on master, that'll reduce the force with which we (I)
> try to impose it.
What's the semantic difference? One can be specified by the user, and
the AM_* is what configure (automake) works out is
Hi Paul,
> isn't that sort of the point of mhfixmsg? to fix poorly or illegally
> formatted email?
Good point, but I think it uses the stock nmh code for parsing emails
rather than have it own code that is cluttered with wart handling.
That's why there's
Hi Ken,
> Huh, the HEADERS have ^M on them?
I've reproduced similar symptoms with an mhbuild-produced email where I
tacked on CR to the end of every line after the blank line after the
headers. IOW, without the headers having CR. However, I still think
this is an invalid format email; why
Hi,
This is OK.
$ mhlist -noverbose
msg part type/subtype size description
8394 multipart/mixed363
1 text/plain 6
2 message/external-body 93
application/octet-stream
$
But my
commit 937ee92013bed7b3ebd30fff2c17a751d37b1a61
Author: Ralph Corderoy <ra...@inputplus.co.uk>
Date: Sat Aug 19 15:58:49 2017 +0100
test-sendfiles: Feed `lzma -cd' stdin rather than a filename.
Håkon Alstadheim reported that Debian's lzma-9.22-2 would complain at
Hi,
> Good point. I'm not too sure either; it depends what the current
> needs are...
So my email above had this part to it, that made it through the list
back to me.
> Content-Type: message/external-body; access-type="url";
> url="dict://dict.org/d:yagni:foldoc"
>
> Content-Type:
Hi,
> Good point. I'm not too sure either; it depends what the current
> needs are, or what they would be if the code was nicer. Options
> include: just using atexit(3); ...
With good timing, this just cropped up.
With gcc 4.9.2, `-O -D_FORTIFY_SOURCE=2', on
1.6-branchpoint-1494-g23645d5, I
Hi David,
> > valgrind here, 3.13.0-2, doesn't complain about the printf, and that
> > prints zero. That puzzles me.
>
> Yes, interesting. Have you tried with -O0?
gcc 7.1.1-4. valgrind 3.13.0-2.
With -D_FORTIFY_SOURCE=2:
-O0 Compile fails; optimisation needed.
-O2
Hi David,
> > There are probably various valid paths where a program exit(0)s that
> > don't write the context file.
>
> Yeah, yet another unification target.
Germany's was a cinch compared. :-)
> > sbr/done.c's done is a file pointer that often points to exit(3).
> > Is it just a poor man's
Hi,
I've been doing `inc -version' before and after upgrading the installed
nmh as 1.7-release changes to check it went OK. I noticed this
behaviour.
$ cat ~/mail/context
Current-Folder: inbox
Version: nmh-1.7-RC2
$ sed -i 2d ~/mail/context
$
$ inc -version
Hi,
David wrote:
> Ken wrote:
> > And dang, coming up with a test for the url external-body type is
> > going to be a pain.
How about
Content-Type: message/external-body; access-type="url";
url="http://google.com/robots.txt;
Could have https too. They could be skipped if a curl(1)
Hi Ken,
> Huh, the HEADERS have ^M on them?
I've tried slapping CR at various places on the email that was
originally attached and can't get mhfixmsg to go wrong. The original
that has the problem would be handy to find the issue and come up with a
minimum test case if it is a nmh bug. And it
Hi Håkon,
> Which is smaller. Update: You pointed out the carriage returns. Can
> you send the problem email as a .tar.gz or something that will leave
> everything alone.
It would still be useful to have that to reproduce the mhfixmsg problem
here.
> > > 11.tar: unknown suffix -- unchanged
>
Hi Håkon,
> $ mhlist -version
> mhlist -- nmh-1.7-RC2 built 2017-08-18 11:32:04 + on garbo
> $ mhlist 1
> mhlist: bogus multipart content in message 1
> msg part type/subtype size description
>1 multipart/mixed32K
And yet I got
> > $ mhlist -file
Hi Håkon,
> Trying to run mhfixmsg on it just removes the entire body of the mail.
Can you give a command that fails? It seems OK here.
$ mhfixmsg -version
mhfixmsg -- nmh-1.7-RC2 1.7-RC2-1-g42b75672 built 2017-08-18 06:44:22 +
on orac
$ scan -file 9707.2.email -format
Hi again,
> Same for a negative number. (Try passing -1718 to fmttest.)
$ fmttest -raw -format '_%4(putnumf)_' ''
_ 0_
$ fmttest -raw -format '_%0(putnumf)_' ''
^C
$ fmttest -raw -format '_%(putnumf)_' ''
^C
$
The last two get stuck.
--
Cheers, Ralph.
Hi Valdis,
> Actually, could use that now, I've been using a git tree copy for quite some
> time now... :)
Good show.
> man mh-format says:
>
>When a function or component escape is interpreted and the result will
>be printed immediately, an optional field width can be
Hi Ken,
> I'm not really liking the idea of having a code fix that only appears
> on the release branch. I'd rather have the same code in 1.7 and
> master. So I say apply the re-write to 1.7.
OK, I'll check-pick these across to the branch a little later on then.
Let me know if that's not the
Hi Ken,
> So, I guess I'm a liar ... turns out MacOS X _does_ define
> __WCHAR_MAX__. Although it seems like WCHAR_MAX is the correct macro
> according to POSIX, so maybe getcwidth.c should still switch?
Yes, I can't recall why I plumped for the __ version now. I've pushed a
fix. Indentifiers
Hi,
What use is whatnow(1)'s -prompt option? The man page says
The -prompt string switch sets the prompting string for whatnow.
It doesn't document that it's subject to printf(3) expansion and
provided with a single argument that's the program's name, i.e.
"whatnow", unless you copy it to
Hi,
I've opened https://savannah.nongnu.org/bugs/index.php?51693 to track
this because I don't have time at the moment, but I don't know who gets
those "bug opened" emails so here's a copy.
$ git describe
1.7-branchpoint-10-ga091c28b
$ uip/scan -format '' -file /dev/null
scan:
Hi David,
> > Sunglasses have a width of 1 here, that's why David and I don't see
> > the problem.
>
> I'm surprised that I didn't see the same behavior as Norm, because we
> use the same locale, en_US.utf8. Any idea why?
I'm en_GB.utf8, but I don't see it either. It's the wcwidth(3) answer
Hi,
David wrote:
> > inc seems to have a similar, if not identical problem.
>
> It's identical: inc uses the same code to print the scan line.
I was surprised recently when plodding through the source that inc(1)
actually uses the scan() function to do the inc-ing, with the scan as a
side
Hi Leonardo,
> At least regarding the `make check' (always on NetBSD/amd64 8.99.1),
> all 104 tests are passed and 7 tests were not run.
Great, thanks.
> Regarding the not run ones (all expected):
>
> ./test/oauth/test-inc: skipped: no oauth support
MACHINES says that's
Hi Leonardo,
> Sure! Here what I see with your patch applied:
>
> % scan -format '%(decode{subject})' +. 1
> mbtowc(0x20) = 1
> cntrl:0 space:1 blank:1 print:1
> mbtowc(0x1f576) = 4
> cntrl:0 space:0 blank:0 print:0
> wcwidth(0x1f576) = -1
Yeah, I think the code was assuming if it's
Hi Leonardo,
> (gdb) print wide_char
> $2 = 128374 L'\x1f576'
> (gdb) quit
>
> L'\x1f576' (in wide_char) is probably the `dark sunglasses' (U+1F576)
> unicode character
It is. One of three non-ASCII characters in that subject.
$ uip/scan -file 8759.2.email -format '%(decode{subject})'
Hi again Norm,
I wrote:
> Could you run this scan command with 1.7-RC1
With Leonardo's reply, there's no need to bother.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
Hi,
> Assertion failed: (w >= 0), function cpstripped, file
> ../nmh/sbr/fmt_scan.c, line 291.
char_len = mbtowc(_char, str, len);
if (char_len < 0) {
altstr = "?";
char_len = mbtowc(_char, altstr, 1);
}
I wonder if mbtowc()'s internal shift state
Hi Norm,
> scan applied to an Email like the attached dumps core. I will send
> more particulars, on request.
Could you run this scan command with 1.7-RC1 to make sure it still has
the assert(3) failure on the problem email.
scan -format '%(decode{subject})' cur
And then repeat that but
Hi Ken,
> Ooof, I get:
Like David, I don't. The Subject is two lots of base64 that I think
decode to
f0 9f 95 b6 53 75 6e e2 80 99 73 20 6f 75 74 2c |Sun...s out,|
0010 20 73 61 76 69 6e 67 73 20 4f 4e e2 80 94 73 68 | savings ON...sh|
0020 6f 70 20 6d 61 6a 6f 72
Hi Conrad,
> packf leaves "..map" files lying around my mail directory; this
> is documented in the man page as a "binary index". Is there a point to
> this file? Better documented elsewhere?
Support was deleted in
Hi,
I've seen this on and off and can now describe when it happens.
I normally run ./configure in a git checkout of master.
#! /bin/sh
cc='ccache cc' # -pg
opt=-O3
bs= #-DBUFSIZ=225
tls=yes
oauth=yes
readline=yes
rm -f config.cache
./configure \
Hi Ken,
> Ah, I remember why I use GPG; that's a savannah requirement that they
> put in place after a break-in. I think, when I looked at it, there
> wasn't an obvious cross-platform checksum program.
No, they've all slightly different names, but produce the same digest.
> To me, that's one
601 - 700 of 1424 matches
Mail list logo
