Sorry, I wasn't paying attention earlier in the thread.
> It sounds like there may be (or have been) a distinction between native app
> behavior vs unix/shell on MacOS. But I'm not in a position to test that.
That's correct. The general guidance is it's a good idea to avoid : in MacOS
filenames, because of this, but there's no hard prohibition nor, I think, a
security issue. Generally speaking GUI apps that use the system GUI routines
will exchange a : in a filename for a /, and vice-versa. For instance, if I
create a file called "a:a"
bash$ touch a:a
then the Finder (MacOS's file browser, equivalent to the Windows Explorer,
etc.) displays the file as "a/a".
This presents a lot of confusion and is good reason for users to avoid either
character in the contexts in which it is permitted, but not, I think, an issue
mutt needs to worry about overmuch.
> Cameron (or anyone else on MacOS), can you confirm ':' is allowed for files
> on your system, especially those created from a shell or launched by Mutt
> via mailcap?
Confirmed.
And this is not a recent change. It has been ever thus since MacOS X, the
Unix-based MacOS was introduced.
--
[email protected]
John Hawkinson
