"Full Path" vs. "Path and Name"

[kyle]

My apologies if I missed this in another forum post, but I couldn't find it when searching.

I had version 1396a installed up until a couple days ago and then installed version 1940a. This brought with it the change of the executable name from Everything64.exe to just Everything.exe. I noticed that with the new Everything.exe (1940a), there is no longer a "Full Path" column/property like there always was up through at least version 1396a. Now it seems the replacement for "Full Path" is "Path and Name"? Is that correct? I don't see that documented anywhere and I don't see it in the changelog. To be clear, I do see that there is a "Path and Name" property that you documented on September 7th. But I don't see anything about "Full Path" going away or "Path and Name" being its replacement. Could you please verify and maybe shed a little light on why it changed?

Thanks!

[void]

Everything 1.5 is in alpha.
The localization is currently being updated for a beta release.

Some properties and text will change.

Full Path should really have been Full Path and Name.
but this is too wordy, so I went with Path and Name.

Path in Everything means the location part.


I'm trying to make things clearer and more consistent..
eg: is 'Full Path' just the location part?


Filename parts in Everything:
Filename: C:\Windows\Notepad.exe
Name: Notepad.exe
Path: C:\windows

I've tried a few times to rename Path and Name to just Filename, but it never seems to stick..
I'm open to suggestions.

[kyle]

I mainly just wanted to understand what happened and make sure nothing got messed up with my install/config.

There's not a standard nomenclature across programming languages or operating systems. I don't think it matters all that much one way or the other as long as it's consistent and well documented. If it were me, I'd probably just go with

Full Path

,

Path

and

Name

. To me, that's most clear and less verbose.

But, it's like they say... the 2 hardest problems in computer science are Cache Invalidation, Naming Things and Off-By-One Errors.

[ChrisGreaves]

My apologies if I missed this in another forum post, but I couldn't find it when searching.

Hi Kyle; if you haven't tried the phpBB "advanced search" I suggest that you give it a try.

This Advanced Search returns just four posts out of the 65,659 currently available.

I read the posts in your topic and remembered that I was frustrated by terminology a couple of years ago. I think in (Windows) terms of drive, path, name, and extent.
You are not alone.
This topic seems to echo your problem.

I believe (but do not know) that the majority of Everything users arrive from the Windows platform, and for them those four items are the lexical atoms of our language (drive, path, name, and extent), and that the syntax of Everything should use those four atoms to construct other terms in the language used to identify a collection of data.
Cheers, Chris

[hamid56]

Dear David
about below naming challenge

I've tried a few times to rename Path and Name to just Filename, but it never seems to stick..
I'm open to suggestions.

may be "absolute path" be a good candidate

[void]

"Full path" and "Absolute path" are OK.

The issue I find is its too wordy and Everything always uses absolute/full paths, so it's kind of redundant.
Also, "path" in Everything means the location/path-part-only. (never the full path and name)

I do like "Filename", and when exporting I use "Filename" instead of "Path and Name"
The issue with Filename is it is vague on Windows.
When windows refers to the filename, it could be just the name part with extension, a relative filename or a full filename.

"Full filename" and "Absolute filename" are good candidates.

[kyle]

C# and PowerShell use

FullName

.

https://learn.microsoft.com/en-us/dotne ... ew=net-9.0

[void]

Everything 1.5.0.1401a reverts the "Full Path" to "Path and Name" changes.

[therube]

I'll just note, that when doing something like looking through a "raw" .ini,
then current, path_and_name, is more descriptive, more meaningful,
compared to the wrongly (IMO) named, full_path.

With path_and_name, you know what you're getting, with full_path, it's rather arbitrary.
(As far as "absolute", that to me connotates [path] like c:/abc/ vs. /abc/.)

(I hope I got that correct .)