Ken Hornstein wrote:
> I don't quite understand how you made it work BEFORE 1.6; mhshow wouldn't
> do any character conversion, for one. Also, it still won't reflow text
> that's too wide.
You could use profile entries like mhshow-charset-iso-8859-1 to run a
script that would run iconv. The scrip
On Sun, 08 Jun 2014 10:08:12 -0400, Ken Hornstein writes:
>I am hoping that this release will be good enough to be the basis of
>the 1.6 final release, so I would encourage everyone to download it
>and try it out.
i've just packaged and uploaded the debian build of this version, and
things look pr
Thus spake Ken Hornstein:
>
> Your problem is probably the same one I ran into; isspace() would interpret
> 0xA0 as a non-breaking space and replace it with a "real" space, messing
> up UTF-8 sequences.
>
> This isn't perfect; in a perfect world you'd pull in the bytes and call
> wcwidth() on eac
Hi Alexander,
> e.g. all manpages to go in as whatever.1mh instead of whatever.1
OOI, why's that? And is that a recentish change on Debian as this old
Ubuntu doesn't do that. Does that mean co(1) is co.1rcs, etc. too?
Cheers, Ralph.
___
Nmh-workers
>1. the automatic debian build daemons and build environments are very
>stripped down, without guarantees wrt. particular locales being configured.
>
>it makes no sense to attempt the tests that only work if en_US.UTF-8 is
>available, so i've made the affected tests check that and skip if
>necessar
>You could use profile entries like mhshow-charset-iso-8859-1 to run a
>script that would run iconv. The script would sometimes get a filename
>and sometimes a command from, e.g, the mhshow-show-text/html profile
>entry so it wasn't simple. It is much much simpler now so thanks for the
>changes. It
Ken wrote:
> I am not sure about that shell syntax; someone else will have to confirm
> if it's portable enough.
! isn't portable. Neither is egrep -q.
David
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinf
ken wrote:
> >1. the automatic debian build daemons and build environments are very
> >stripped down, without guarantees wrt. particular locales being configured.
> >
> >it makes no sense to attempt the tests that only work if en_US.UTF-8 is
> >available, so i've made the affected tests check
david wrote:
> Ken wrote:
>
> > I am not sure about that shell syntax; someone else will have to confirm
> > if it's portable enough.
>
> ! isn't portable. Neither is egrep -q.
huh. shows what i know. :-)
paul
=--
paul fox, p...@foxharp.boston.ma.us (arlington, ma,
Hi David,
> > I am not sure about that shell syntax; someone else will have to confirm
> > if it's portable enough.
>
> ! isn't portable. Neither is egrep -q.
What kind of portability are we aiming at? ! is in POSIX;
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_
Ralph wrote:
> Hi David,
>
> > ! isn't portable. Neither is egrep -q.
>
> What kind of portability are we aiming at? ! is in POSIX;
> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_
> 18_09_02
> Similarly, `grep -Eq' is too;
I should have typed "grep" instead of
On Jun 11, 2014, at 3:54 PM, David Levine wrote:
> Pretty much. I test with heirloom sh and posh. So the limits
> are reasonably well defined and it's easy to detect attempts to
> go outside them. Until we need more, I'd like to stick with them.
Just redirect stdout to /dev/null and you can
12 matches
Mail list logo
