Re: [PATCH] Header cache and slashes
On Wed, Mar 22, 2006 at 05:04:45PM +0100 I heard the voice of
Thomas Glanzmann, and lo! it spake thus:
>
> if we include something like that, let us do it right and use the
> bash unify path function and port it to mutt.
If we're going to go that far, we should just stop using pathnames
(which can never uniquely identify a file/dir anyway) and just start
hashing [device,inode] or something instead.
> The previous submitted pach should not be included. Because there
> were to much lines of code for the effect and it just fixes one case
> out of one hundred.
But it's the one case that covers 99% of the problem. I get to
mailboxes 2 ways, as a rule:
1) From the mailboxes directive, just jumping from folder to folder
with new mail. This always uses the same path (as itself; it's
tautological).
2) From manually typing =<mailbox> to jump to a specific one, using
tab completion which often sticks the trailing / on and cases all
the trouble.
The only other way I can ever remember getting there is occasionally
from the command line, which would refer to it the same (after
=-expansion).
Sure, there are all sorts of cases it doesn't handle. But far and
away the most _common_ problem (I hit it all the time, and I'm
apparently not the only one) is that trailing slash, which is easy to
knock off.
--
Matthew Fuller (MF4839) | fullermd@xxxxxxxxxxxxxxx
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.