On Thu, Dec 4, 2008 at 1:13 PM, Charles Campbell wrote:
>
> Matt Wozniski wrote:
>> Looking at the code, the way this is done seems fundamentally
>> broken... If I'm understanding things correctly, you're trying to
>> separate the priority from the filename with a "separator character",
>> and then using s/\d\{3}SEPCHR// to remove it later. If I'm not
>> misunderstanding that, it seems that it would be completely impossible
>> to choose a separator character which is an invalid character in
>> filenames on all systems. An ext2 filesystem could have a file named
>> "123\xFF" or "123\x01"; in fact the only two invalid characters on the
>> filesystem are NUL and forward slash, and neither of those are
>> suitable for what use here - vim strings can't contain a NUL byte, and
>> 123/ is a valid name for a directory that you may need to sort. I
>> suppose one work-around might be to substitute all \ for \\ and all /
>> for \/ and then use / as a separator character, replacing \\ with \
>> and \/ with / afterwards, but even that idea seems fragile. Am I
>> completely off base? Is the way it's currently being done safer than
>> it appears to me?
>>
> "Fundamentally broken", huh?
Fundamentally broken, as in there's no separator character that can be
used on all systems, and requiring users to try to come up with their
own character that probably won't be used is completely
unreasonable...
~Matt
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
