in reply to RFC: fixname v 0.3

I don't have any annoying directories on my linux machine! I don't create directories with spaces in the directory name. My linux installation didn't come with any spaces in the directory names. In general, the names are all lowercase, or at worse, mixed case. I don't have any problem with how my directories are named in the first place.

You do know about filename (and directory) name completion features in your shell, right? It almost never matters exactly what the full file or directory name is, just that the first few letters are unique within the directory listing. Assuming that you structure your directories that way, file globbing or name completion make typing fairly minimal.

In short, this module sounds a lot like a solution in search of a problem.

Replies are listed 'Best First'.
Re^2: RFC: fixname v 0.3
by blazar (Canon) on Jan 17, 2006 at 09:23 UTC
    I don't have any annoying directories on my linux machine! I don't create directories with spaces in the directory name.

    Me too! But what's nice is that in those rare situations in which I have to deal with (supposed to be) annoying filenames, I can do that effortlessly. I can have a file with a "\n" in it's name and the shell will expand it just as fine as any other one. Well... and if the "\n" is the first charachter? Whatever, when I'm totally lost -and it happens very rarely- mc or a tool like that comes to the rescue!

    A friend of mine also used to use mc to delete (or rename, etc.) files with a leading "-". That is, before he discovered that -- ends the list of options.

    In any case to keep the discussion on topic -that is, Perl- at the very worst one can use it ad hoc to deal with "exotic" filenames:

    perl -e 'rename "\nbraindead\tname", "sensible_name"'

    [download]
[reply]
[d/l]
[select]

In Section Meditations