Path parts definitions

[Stamimail]

We need understandable and agreed terminligny for path parts.

What is Path? (Location or Location+Filename)
What is Filename (Filename or FIlename+extension)

I can't understand this:
"full paths and filenames"?

btw,
I suggest to use this:
Copy Path (C:\Folder\filename.ext)
Copy as Path ("C:\Folder\filename.ext")
"Copy Path" ("C:\Folder\filename.ext")
Copy Location (C:\Folder)
"Copy Location" ("C:\Folder")

In my suggestion, there is no FullPath in terminology. Path is always FullPath.

I don't have an idea how to distinguish between:
Filename
Filename.ext

Is there a better way than:
Copy Filename
Copy Filename.ext

[therube]

("folder" or "directory" ?
[I wonder why "folder" even came about.]
I'm thinking, from time to time, there may be some slight confusion, but more often it is here in these forums when wanting to describe a particular situation where someone might say "file" or "path" or "pathname" thinking in their mind a particular meaning, where others read it differently, & less of an issue in the program UI & working, itself.)

[NotNull]

It is very hard to come up with a good and clear definition. Maybe even too hard (otherwise there would be a good naming standard by now, I guess)
To add to the confusion, my idea ( :-p)

Drive = C:
Path = \Program Files\Eveything\
Base name = Everything
Extension = .exe
Fully qualified filename: c:\program files\everything\everything.exe

(so C:\file.txt has a path: "\")


But that's still not clear enough:

- Should the extension be .exe or just exe?
- Modern Windows filesystems support more namespaces beyond the good old DOS one: \\?\C: ... (to support very long filenames (eh ...) ) \\?\UNC\.. \\.\ (to bypass the filesystem and talk on a device level to the files). And there is the good old \\server\share syntax
Should those all be called "drive" too?

P.S: I like "location"! Thats a good description.

[void]

Currently, Everything uses "path" to describe the "path part" internally and in the UI.

The "Path" column should be changed to "Folder" to match Windows Explorer.
Windows Explorer also uses "Location" or "Folder Path" (See the file properties page).

"Full path and filename" should be "fully qualified file name" or just "path".

Everything uses "Name Part" or "Name Part Only" when the extension is not wanted (see namepartdupe:).
This is still not clear as "Name part" often includes the extension. Windows usually does not deal with the name part only.

[Stamimail]

Currently, Everything uses "path" to describe the "path part" internally and in the UI.

It's not clear what is the "path part".
when you say Copy Path what will be the intention:
C:\Folder\filename.ext
or
C:\Folder

The "Path" column should be changed to "Folder" to match Windows Explorer.
Windows Explorer also uses "Location" or "Folder Path" (See the file properties page).

I think using the term Folder can lead to misunderstanding.
C:\Folder\Folder
RightClick > Copy Folder

I would prefer:
RightClick > Copy Location

"Full path and filename" should be "fully qualified file name" or just "path".

just "path" is ok, but we need to be consistent after the decision is taken.
If people can be confused how to interpret Path, I'm ok with FullPath. (and not using Path at all)

Everything uses "Name Part" or "Name Part Only" when the extension is not wanted (see namepartdupe:).
This is still not clear as "Name part" often includes the extension. Windows usually does not deal with the name part only.

Yes, I think we need to get more suggestions to find a definition that will distinguish between
Filename
and
Filename.ext

maybe:
Filename
and
File.name (with a dot)

Copy Filename
Copy File.name

Copy Filename
Copy FileN.ame

Copy Name
Copy N.ame
(mixture of folders and files)

or:

Copy Name
Copy FullName

[void]

path part = the folder location.
C:\Folder for C:\Folder\filename.ext

I think using the term Folder can lead to misunderstanding.
C:\Folder\Folder
RightClick > Copy Folder

I would prefer:
RightClick > Copy Location

I prefer location here too, put on my TODO list.
"Folder Location" could also work.

[Stamimail]

I prefer location here too, put on my TODO list.
"Folder Location" could also work.

I can say, that currently in my local Everything, I have:
|Location| (as column header, instead of Path)

RCMenu:
Open
Open Location
Copy Path to clipboard
Copy Location to clipboard

(Path in my Everything always means FullPath)

[void]

File name part proposal for Everything 1.5:

For Example, if the file is: C:\Program Files\Everything\Everything.exe

• Full Path and Filename: C:\Program Files\Everything\Everything.exe
  Folder or Folder Location: C:\Program Files\Everything
  Filename: Everything.exe
  Name Part: Everything
  Parent Path: C:\Program Files\Everything
  Extension (always without dot): exe

https://stackoverflow.com/questions/223 ... -of-a-path

Path on its own is vague, I would like to keep using full path and filename to clarify that it is the fully qualified path and filename.

For filename functions, pathpart and namepart should remain unchanged, I'll add parentpath (same function as pathpart) and change the documentation.

[Stamimail]

Path on its own is vague

Since the word "Path" has many meanings which can cause confusion,
Do you think it is possible not to use the word "Path" at all?

https://stackoverflow.com/questions/223 ... -of-a-path

I think someone needs to take the world one step further.

[void]

Do you think it is possible not to use the word "Path" at all?

On its own, yes.
I would like to use it only when specifying full path and filename or fully qualified path and filename.

[Stamimail]

Do you think it is possible not to use the word "Path" at all?

On its own, yes.
I would like to use it only when specifying full path and filename or fully qualified path and filename.

Do you think it is possible not to use the word "Path" at all? To find terminology alternatives also to "full path and filename" or "fully qualified path' and filename"?