Would it be possible to include, for tagging, also commata as "word start character" into the index?
Within the path parts, for example, a
\,r\
is found by searching for
\,r\
but not by searching just for
,r
And within the file name parts, in
someText ,r someOtherText
the ,r is not found either by searching for
,r
Whilst it's obvious that for tagging, the comma would be the ideal "leading code character" for then tags with 1 more character
,r meaning "tag r", or more characters, in
,ra or ,ras the r being the "tag" again, with the "a", or the "as", the respective value of tag "r".
Those "tag-commata" would have a space or no space before them, but would never have a space behind them, since the comma would be just the "starter-code", with then, as said, at least 1 char for the respective tag; after that, or those, "regular" characters then, a space or not.
(I have tried a dot instead, "with success", but since the dot separates the suffix from the filename, a search for
.r
will also find all .rtf files, and similar with other suffixes, so regularly indexing the comma would be the most elegant "file name tagging" solution.
EDIT:
Hello,
just seeing your answer. Yes, my error. I had switched back to 1.4, then had to discover I had simply not seen that my comma-tags, except within e.g. "\,r\", and (successfully) searched for by "\,r", were not found. So I have to find some other, special character, and being allowed in file names, for tagging, but that will not be as easy as just pressing a comma; again, "regular" commata immediately follow some "text", whilst a "tag comma" will either be after a "\", at the start, or after a space, and "regular" commata will be followed by a space, whilst a "tag-comma" will never have a space behind it, so it would technically be possible to distinguish them, and for the user anyway. Will now start trials with °,§, etc - successful use depending on their index treatment.
Commata in file names (for tagging) - Suggestion
Commata in file names (for tagging) - Suggestion
Last edited by 2530 on Mon Oct 23, 2023 5:18 am, edited 2 times in total.
Re: Commata in file names
You should see exactly the same results for ,r with Everything 1.4 and 1.5.
Were any search options enabled in Everything 1.5 under the Search menu? Match whole words maybe?
Do you have Match Path enabled on Everything 1.4?
Are you indexing the same number of files?
(total is shown in the status bar when the search is empty)
Import settings from Everything 1.4
Were any search options enabled in Everything 1.5 under the Search menu? Match whole words maybe?
Do you have Match Path enabled on Everything 1.4?
Are you indexing the same number of files?
(total is shown in the status bar when the search is empty)
Import settings from Everything 1.4
Re: Commata in file names (for tagging) - Suggestion
Does enabling Match Path under the Search menu help?
Re: Commata in file names (for tagging) - Suggestion
Sorry again, for having bothered you, it all works as expected: With "Search - Match Path" it works as expected for the path part, i.e. a simple search
,r
finds all paths with ",r", and in the file name part, it also works, for tagging as described.
(I had switched to 1.5, but without the settings or the stored indices, then shuffled a lot of data over the week-end, then "discovered" it wouldn't work as expected (which is not true), then switched back to 1.4 - new install -, again with my settings and indices lost, rebuild the indices again, and "discovered" it didn't work, then thought - and erroneously wrote - I had missed it hadn't been working as expected before, too... I then took 4 hours' night sleep in the morning I had missed by night, very glad I hadn't been "on the road" this very early morning without any night's sleep before. Sorry!)
As for the new title, it conveniently becomes a suggestion for fellow EV users:
Use ,x or ,xy (see first post above) tags in paths and in file names (with "Search - Match Paths" yes and "Search - "Match Whole Words" no); among other things, it allows you to find, at the same time, files (or whole subfolders) which are at the "correct" position in your folder hierarchy, and "displaced" files or folders which are not (and which would be "displaced" re another, and possibly even more important, criterion if you moved them instead). And with ",x" or ",xy" within the paths, you can even have \x\ as (the respective) value for one filing "category", and \,x\ as (the respective) value for another filing "category" - in fact, different "dimensions" -, "x" and ",x" both as short as they get, and never to be confused all the same, not only of interest for lesser typing, but especially since many Windows applications come with a max 260 character path length requirement, independently of your Windows "long path" settings. Using such "EV tags" is particularly useful when you (have to) spread similar data over different drives, and where the "factory" NTFS link and junction transclusion instruments thus don't help - and it's so much simpler anyway, last but not least at the backup stage.
,r
finds all paths with ",r", and in the file name part, it also works, for tagging as described.
(I had switched to 1.5, but without the settings or the stored indices, then shuffled a lot of data over the week-end, then "discovered" it wouldn't work as expected (which is not true), then switched back to 1.4 - new install -, again with my settings and indices lost, rebuild the indices again, and "discovered" it didn't work, then thought - and erroneously wrote - I had missed it hadn't been working as expected before, too... I then took 4 hours' night sleep in the morning I had missed by night, very glad I hadn't been "on the road" this very early morning without any night's sleep before. Sorry!)
As for the new title, it conveniently becomes a suggestion for fellow EV users:
Use ,x or ,xy (see first post above) tags in paths and in file names (with "Search - Match Paths" yes and "Search - "Match Whole Words" no); among other things, it allows you to find, at the same time, files (or whole subfolders) which are at the "correct" position in your folder hierarchy, and "displaced" files or folders which are not (and which would be "displaced" re another, and possibly even more important, criterion if you moved them instead). And with ",x" or ",xy" within the paths, you can even have \x\ as (the respective) value for one filing "category", and \,x\ as (the respective) value for another filing "category" - in fact, different "dimensions" -, "x" and ",x" both as short as they get, and never to be confused all the same, not only of interest for lesser typing, but especially since many Windows applications come with a max 260 character path length requirement, independently of your Windows "long path" settings. Using such "EV tags" is particularly useful when you (have to) spread similar data over different drives, and where the "factory" NTFS link and junction transclusion instruments thus don't help - and it's so much simpler anyway, last but not least at the backup stage.