mirror of
https://github.com/arsenetar/dupeguru.git
synced 2024-10-30 05:15:57 +00:00
Andrew Senetar
46d1afb566
- Remove trailing whitespace - Correct single newline at end of files (skip for json) - Update to formatting in a few places due to black
79 lines
3.8 KiB
ReStructuredText
79 lines
3.8 KiB
ReStructuredText
Preferences
|
|
===========
|
|
|
|
**Tags to scan:**
|
|
When using the **Tags** scan type, you can select the tags that will be used for comparison.
|
|
|
|
**Word weighting:**
|
|
See :ref:`word-weighting`.
|
|
|
|
**Match similar words:**
|
|
See :ref:`similarity-matching`.
|
|
|
|
**Match pictures of different dimensions:**
|
|
If you check this box, pictures of different dimensions will be allowed in the same
|
|
duplicate group.
|
|
|
|
.. _filter-hardness:
|
|
|
|
**Filter Hardness:**
|
|
The threshold needed for two files to be considered duplicates. A lower value means more
|
|
duplicates. The meaning of the threshold depends on the scanning type (see :doc:`scan`).
|
|
Only works for :ref:`worded <worded-scan>` and :ref:`picture blocks <picture-blocks-scan>`
|
|
scans.
|
|
|
|
**Can mix file kind:**
|
|
If you check this box, duplicate groups are allowed to have files with different extensions. If
|
|
you don't check it, well, they aren't!
|
|
|
|
**Ignore duplicates hardlinking to the same file:**
|
|
If this option is enabled, dupeGuru will verify duplicates to see if they refer to the same
|
|
`inode`_. If they do, they will not be considered duplicates. (Only for OS X and Linux)
|
|
|
|
**Use regular expressions when filtering:**
|
|
If you check this box, the filtering feature will treat your filter query as a
|
|
**regular expression**. Explaining them is beyond the scope of this document. A good place to
|
|
start learning it is `regular-expressions.info`_.
|
|
|
|
**Remove empty folders after delete or move:**
|
|
When this option is enabled, folders are deleted after a file is deleted or moved and the folder
|
|
is empty.
|
|
|
|
**Copy and Move:**
|
|
Determines how the Copy and Move operations (in the Action menu) will behave.
|
|
|
|
* **Right in destination:** All files will be sent directly in the selected destination, without
|
|
trying to recreate the source path at all.
|
|
* **Recreate relative path:** The source file's path will be re-created in the destination folder up
|
|
to the root selection in the Directories panel. For example, if you added
|
|
``/Users/foobar/SomeFolder`` to your Directories panel and you move
|
|
``/Users/foobar/SomeFolder/SubFolder/SomeFile.ext`` to the destination
|
|
``/Users/foobar/MyDestination``, the final destination for the file will be
|
|
``/Users/foobar/MyDestination/SubFolder`` (``SomeFolder`` has been trimmed from source's path in
|
|
the final destination.).
|
|
* **Recreate absolute path:** The source file's path will be re-created in the destination folder in
|
|
its entirety. For example, if you move ``/Users/foobar/SomeFolder/SubFolder/SomeFile.ext`` to the
|
|
destination ``/Users/foobar/MyDestination``, the final destination for the file will be
|
|
``/Users/foobar/MyDestination/Users/foobar/SomeFolder/SubFolder``.
|
|
|
|
In all cases, dupeGuru nicely handles naming conflicts by prepending a number to the destination
|
|
filename if the filename already exists in the destination.
|
|
|
|
**Custom Command:**
|
|
This preference determines the command that will be invoked by the "Invoke Custom Command"
|
|
action. You can invoke any external application through this action. This can be useful if,
|
|
for example, you have a nice diffing application installed.
|
|
|
|
The format of the command is the same as what you would write in the command line, except that there
|
|
are 2 placeholders: **%d** and **%r**. These placeholders will be replaced by the path of the
|
|
selected dupe (%d) and the path of the selected dupe's reference file (%r).
|
|
|
|
If the path to your executable contains space characters, you should enclose it in "" quotes. You
|
|
should also enclose placeholders in quotes because it's very possible that paths to dupes and refs
|
|
will contain spaces. Here's an example custom command::
|
|
|
|
"C:\Program Files\SuperDiffProg\SuperDiffProg.exe" "%d" "%r"
|
|
|
|
.. _inode: http://en.wikipedia.org/wiki/Inode
|
|
.. _regular-expressions.info: http://www.regular-expressions.info
|