During a (case-insensitive) dupe comparison, dupe lines distinguishes between different cases.
There is something to say for doing it this way, but in my opinion it makes more sense to respect the case setting.
dupe_lines vs case
-
NotNull
- Posts: 5961
- Joined: Wed May 24, 2017 9:22 pm
dupe_lines vs case
You do not have the required permissions to view the files attached to this post.
-
void
- Developer
- Posts: 19872
- Joined: Fri Oct 16, 2009 11:31 pm
Re: dupe_lines vs case
Thanks for the issue report NotNull,
Everything is incorrectly showing the dupe line between items when only the case has changed.
This issue will be fixed in the next alpha update.
Everything is incorrectly showing the dupe line between items when only the case has changed.
This issue will be fixed in the next alpha update.
-
therube
- Posts: 5723
- Joined: Thu Sep 03, 2009 6:48 pm
Re: dupe_lines vs case
(Actually that helped to point out to me files that were the same, but where I had changed case of 1 file but not its' backup version
.)
(Was your double-colon before 'n' intentional?)
(Was your double-colon before 'n' intentional?)
-
NotNull
- Posts: 5961
- Joined: Wed May 24, 2017 9:22 pm
Re: dupe_lines vs case
Yes, it was. According to the Search Modifier documentation:
Prefix a search modifier with :: to enable it globally.
For example, to enable match case for the rest of the search:
::case: FOO BAR
-
void
- Developer
- Posts: 19872
- Joined: Fri Oct 16, 2009 11:31 pm
Re: dupe_lines vs case
Everything 1.5.0.1355a makes the following changes:
dupe lines are now case insensitive.
To enable case sensitive dupe lines:
Dupe lines are shown for the current sort, not the current dupe command.
Added group_match_case ini setting.
Added group_lines ini setting.
This can be enabled to always show group lines, not just when using dupe:
To always show group lines:
Can also be enabled by including the following in your search:
group-lines:
distinct: without any properties specified will now find distinct names.
Same with unique:
Fixed an issue with case:dupe:
This wasn't working at all before..
Everything will now correctly case sort when using case:dupe: (for most property types: name, extension, path, secondary sorts, regmatches and columns 0-f)
dupe lines are now case insensitive.
To enable case sensitive dupe lines:
- In Everything 1.5, from the Tools menu, click Options.
- Click the Advanced tab on the left.
- To the right of Show settings containing, search for:
group - Select group_match_case.
- Set the value to: true
- Click OK.
Dupe lines are shown for the current sort, not the current dupe command.
Added group_match_case ini setting.
Added group_lines ini setting.
This can be enabled to always show group lines, not just when using dupe:
To always show group lines:
- In Everything 1.5, from the Tools menu, click Options.
- Click the Advanced tab on the left.
- To the right of Show settings containing, search for:
group - Select group_lines.
- Set the value to: true
- Click OK.
Can also be enabled by including the following in your search:
group-lines:
distinct: without any properties specified will now find distinct names.
Same with unique:
Fixed an issue with case:dupe:
This wasn't working at all before..
Everything will now correctly case sort when using case:dupe: (for most property types: name, extension, path, secondary sorts, regmatches and columns 0-f)
-
NotNull
- Posts: 5961
- Joined: Wed May 24, 2017 9:22 pm
Re: dupe_lines vs case
Nice!!
Something I noticed:
When Full row select is unchecked (Options > Results), the dupe line will only be shown in the name column, even if dupes are shown for other properties.
Would it be possible to make the dupe line 'full row' anyway?
(aklternative would be to (temporary) enable Full row select; that is what I do at the moment. No big deal)
Something I noticed:
When Full row select is unchecked (Options > Results), the dupe line will only be shown in the name column, even if dupes are shown for other properties.
Would it be possible to make the dupe line 'full row' anyway?
(aklternative would be to (temporary) enable Full row select; that is what I do at the moment. No big deal)
-
void
- Developer
- Posts: 19872
- Joined: Fri Oct 16, 2009 11:31 pm
Re: dupe_lines vs case
I have put on my TODO list to highlight the entire row.
Thank you for the suggestion.
Thank you for the suggestion.
-
void
- Developer
- Posts: 19872
- Joined: Fri Oct 16, 2009 11:31 pm
Re: dupe_lines vs case
Everything 1.5.0.1356a adds support for case: search modifier to sort:
For example:
A normal Name sort will look like:
USA C:\A-folder
usa C:\A-folder
USA C:\B-folder
usa C:\B-folder
case:sort:name
will show the results as:
USA C:\A-folder
USA C:\B-folder
usa C:\A-folder
usa C:\B-folder
To find files where the case changes, include the following in your search:
case:distinct: dupe:
(finds case sensitive distinct items first, then finds case insensitive duplicated items)
Everything 1.5.0.1356a also fixes an issue with the property being passed to distinct: when using distinctsort:
Everything will now use the property specified in distinct: instead of the property specified in distinctsort:
The dupe line will now fill the entire row when full row select is disabled.
For example:
A normal Name sort will look like:
USA C:\A-folder
usa C:\A-folder
USA C:\B-folder
usa C:\B-folder
case:sort:name
will show the results as:
USA C:\A-folder
USA C:\B-folder
usa C:\A-folder
usa C:\B-folder
To find files where the case changes, include the following in your search:
case:distinct: dupe:
(finds case sensitive distinct items first, then finds case insensitive duplicated items)
Everything 1.5.0.1356a also fixes an issue with the property being passed to distinct: when using distinctsort:
Everything will now use the property specified in distinct: instead of the property specified in distinctsort:
The dupe line will now fill the entire row when full row select is disabled.
-
therube
- Posts: 5723
- Joined: Thu Sep 03, 2009 6:48 pm
Re: dupe_lines vs case
case:distinct: dupe:This fits my use case a bit better:
case:distinct: dupe:name;size file:-
void
- Developer
- Posts: 19872
- Joined: Fri Oct 16, 2009 11:31 pm
Re: dupe_lines vs case
Everything 1.5.0.1360a makes a minor change to group_match_case.
group_match_case can now be one of the following values:
group_match_case can now be one of the following values:
- 0 = use current sort match case value (default)
- 1 = match case
- 2 = ignore case