Can one tell Explorer to accept filesnames containing only an extension?

  • Thread starter Thread starter Michael Moser
  • Start date Start date
M

Michael Moser

Again and again I run into this most annoying behavior of Explorer that
it does not accept filenames that only have an extension.

When dealing with certain packages that are designed to run across
multiple platforms (e.g. eclipse) one frequently has to deal with such
files (e.g. .plugin or .project - these are files that are supposed to
be normally hidden in *nix systems and so their name starts with a '.').
I then always have to fire up the DOS window to rename or otherwise
manipulate such files "manually".

Can't one tell Explorer to just shut up and accept such filenames, even
if they consist only of an extension and no name? Some registry tweak or
whatever?

Michael
 
Michael said:
When dealing with certain packages that are designed to run across
multiple platforms (e.g. eclipse) one frequently has to deal with such
files (e.g. .plugin or .project - these are files that are supposed to
be normally hidden in *nix systems and so their name starts with a '.').
I then always have to fire up the DOS window to rename or otherwise
manipulate such files "manually".
Click to expand...

If your files are text files use TextPad.
 
Roger said:
If your files are text files use TextPad.
Click to expand...

I know that other apps have no problem with that. But that means firing
up yet another application to do the job. And whether that's TextPad or
Cmd doesn't make much difference to me.
My question aimed at whether it isn't possible to configure/tweak
Explorer to accept such names in the first place.

Michael
 
Hi Michael
Michael said:
Again and again I run into this most annoying behavior of Explorer
that it does not accept filenames that only have an extension.

When dealing with certain packages that are designed to run across
multiple platforms (e.g. eclipse) one frequently has to deal with
such files (e.g. .plugin or .project - these are files that are
supposed to be normally hidden in *nix systems and so their name
starts with a '.'). I then always have to fire up the DOS window to
rename or otherwise manipulate such files "manually".
Click to expand...

I would say it is a poor crossplatform design if You have to rename
files to make it work.
Can't one tell Explorer to just shut up and accept such filenames,
even if they consist only of an extension and no name? Some registry
tweak or whatever?

Michael
Click to expand...

I think it will be easier to make *nix hide _name or !name
then it is to make explorer accept .name

Kind regards
Asger
 
Again and again I run into this most annoying behavior of Explorer that
it does not accept filenames that only have an extension.
Click to expand...
I have several files and folders with just an extension on my WinXP
Home installation. How are you trying to create these files?
 
Dacicus said:
I have several files and folders with just an extension on my WinXP
Home installation. How are you trying to create these files?
Click to expand...

Well - the actual problem at hand is, that I keep several copies of
config files aiming at different constellations.
To enable a specific one of them I rename the current one and give the
one I intend to use next the name that the program expects.
That name happens to be an <.extension only> name and I would appreciate
if I could simply rename that file in explorer than having to fire up
cmd (or whatever other app) each time.

Michael
 
Asger said:
Hi Michael

I would say it is a poor crossplatform design if You have to rename
files to make it work.
Click to expand...


I fully agree, but since these names have now become common and are used
in thousands of installations I doubt, that I have any chance to
convince people to change that name...
I think it will be easier to make *nix hide _name or !name
then it is to make explorer accept .name
Click to expand...

In principle, yes, but not in reality... The problem IMHO is, that
neither "camp" thinks about it early (or gives no damn...), whether "the
other camp" might have a problem with specific file names, so *nix
developers tend to use these .filenames while windows developers often
have no problem using filenames containing blanks, etc.

Michael
 
Back
Top