Re: [PATCH] Change mutt_buffer_concatn_path() to use fixed algorithm.
"Kevin J. McCarthy" <[email protected]> Tue, 19 May 2026 19:49:47 +0800
| Newsgroups | gmane.mail.mutt.devel |
|---|---|
| Message-ID | <agxOW0PGwysiRZdf@qinghai> |
On Tue, May 19, 2026 at 12:15:20PM +0200, Alejandro Colomar via Mutt-dev wrote:
>On 2026-05-19T13:56:45+0800, Kevin J. McCarthy wrote:
>> To see the change in mutt, start up mutt and
>> - :unset folder<enter>
>> - <change-folder>
>> - At the prompt: Open mailbox ('?' for list):
>> =usr/
>> then hit Tab twice.
>>
>> Before this commit mutt will try to expand "usr" in your cwd.
>> After this commit mutt will try to expand "/usr".
>
>Doesn't = mean it's a relative path? Is it correct to interpret it as
>/usr? I'm not very familiar with how these paths work, so I might be
>completely wrong.
Hi Alex,
= is a mailbox shortcut for the $folder directory. See the list of
different shortcuts at http://www.mutt.org/doc/manual/#shortcuts
So, to be clear, this example doesn't make much sense. They would be
expanding a mailbox shortcut for a shortcut that is unset.
While I'm not super concerned, it is technically a change in behavior.
I wanted make everyone aware of it, in case I missed something.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEiXWpszqjeRA4XFMIre92hIAxa9oFAmoMTlsACgkQre92hIAx a9on9g/+JEIZljcssoSUCdca2Uxf33vb7v6M65USPRR1KXFq4u0uBJCTZyxnDJHv jof+NzL8tIXUgPszgyGoo07z5I6EZ6ca9hA8oCYEqLbwXrN8rpjZlun6CexhaUpD ax3KIoWbYPtCh7F3VHEKLV92n08xL+G2xJdOvb0jv53QMM3PJXj2Duzf/boyyCDx O6hzqB1ZQsCMOZ8s3TP80DM4rWEkHG53XyDf68T+H0WpeTleduH6c0x8PoKh6Lr8 YQKMGshylm4OY9zuUBCOhErAWprGarftbqRkEAsuC8Jeb3QkRK4BLVSb8rVWBa46 ei1i/yo9gmy07fQFhkb/9LGSdFA3Yb3YzZ2EfeuumBh4Jb7FHIlMWZ5TeG+afjow ARD17IFF/yDPi/TmxaptRIkSKCMvrpQVmygC7pW7jqc0FyN2ip/QH2l6gA0T0d8Y LDmJ/dbd49j4A/hCrCg9Dd+74G8KClSr9gGvmELH/gv1RBVU3mIyFB6BXxH0QzUh Mb5fySyhIMW1U0YpPVY0vxTM37CnHY0tlMEP0nwH86uyDt6nNwHv+Z0Zm5rdRzID jsGl2F+yNHUU99nsuxdur7c7nBhjKu4E1mGnDkMB9/cQN9e+ow+8V+DpRTWNprMx WCKHkGRMayf6Mku9PxcDwpGOgBqi7NxFhYsEUOJAGz2ncWNSGf0= =yWQp -----END PGP SIGNATURE-----