Re: [PATCH] wip: change ISSPACE to use ascii whitespace check.

Alejandro Colomar via Mutt-dev <[email protected]>
Newsgroups gmane.mail.mutt.devel
Message-ID <aZcarO4DR8UAYOsT@devuan>
Hi Kevin,

On 2026-02-19T20:49:59+0800, Kevin J. McCarthy wrote:
> On Thu, Feb 19, 2026 at 08:30:56PM +0800, Kevin J. McCarthy wrote:
> > I'm not dead set against it, but I've never thought the macros or naming
> > were confusing.
> > 
> > Making the implementation of each the same seems like a good idea, but I
> > think it would be a shame to get ride of the skip_xxx() and is_xxx()
> > macros.  To me they make the code more readable, not less.
> 
> I will add that veering into needing to implement our own strchrnul() and
> using not-yet standardized C constructs like '?:' feel like it's going a bit
> too far though, for a minor cleanup.  Mutt moves slowly, and still is meant
> to work on (somewhat) older systems.

Sure; I was just floating ideas.  We can incorporate them slowly, to
make sure users can still use mutt(1).


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es>
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEES7Jt9u9GbmlWADAi64mZXMKQwqkFAmmXGx0ACgkQ64mZXMKQ
wqnrmxAAr9j3Wz1agILkcYel+XOaRJJXz9Epve46UvampWOXYVKz7rJlCW2ZKJJS
6cYqomO4Sw646/NGyb7Rsp7Y1/svez2b/bNtC13ylUUmvbau+/+qby2zqvmemvA6
OPR9/J3vlQxw4LielzsrL1LRaUb4eFp2ko8Kg5AwhaRyljxYCYx20KVxpXHj/cb9
rAMOLorw74mY1+aG2vW3j8xilfeqo4F65XDPsq1VgLK9PKwqCTvqEYFZ+XybIn6E
Y2sYfQuS/+sNdaxQiGlp5+hJ5YUrBX69/xS9HpuQFtfMiUFT9OejHvDi84zEmQBJ
6BmihfXecGdT4MsRB8fRjJxdoaRDRyZpSAWMUqWcqLgnXqbDb/Wp6N4mnsBWSmub
LBlc8Prm/Cac8yOzOGwFlOyin6bBnlGHZvDcwb4x0HgOguEPpL1vC+qxiapFbecb
u7QJMChiAB8egqNuqBSX0jVPn6BfpuYfcr23JqgjGvzhkWzhYf1uv8QKO14NdKz7
9bDG61AZj4CD9yB6LJ9sNB1+UL17X9vLB3rjNOkzZM1DIrTUdwUS3h1PSYM7KBlZ
5wvFdD/PvQrk/xd6o8zWNkbc5CUJ3x5b2grP45NAPRWhS5iPva1+nzfa+PjT+5O3
WYhiTULOwOcx9U1to7LVsgAVvK0IBiuFFFawY90gd7eRa1I9tTc=
=FpgV
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.