diff options
| author | lukeflo | 2025-10-14 16:28:20 +0200 |
|---|---|---|
| committer | lukeflo | 2025-10-14 16:28:20 +0200 |
| commit | 3cd41cb1bc2046f1710175999305ab08508bae69 (patch) | |
| tree | 1377609211732c99b5f2ba44fae0aaed21579e68 /CITEKEYS.md | |
| parent | 9b21727bd151a3fda2133b9da12eec588068130e (diff) | |
| download | bibiman-3cd41cb1bc2046f1710175999305ab08508bae69.tar.gz bibiman-3cd41cb1bc2046f1710175999305ab08508bae69.zip | |
option to reformat citekey-based basenames of attachment files
Diffstat (limited to 'CITEKEYS.md')
| -rw-r--r-- | CITEKEYS.md | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/CITEKEYS.md b/CITEKEYS.md index 19bd497..828e557 100644 --- a/CITEKEYS.md +++ b/CITEKEYS.md @@ -147,11 +147,17 @@ should be built. - Most importantly: *always use the **`--dry-run`** option first*! This will print a list of old and new values for all citekeys in the file without changing anything. For the test file of this repo and using the pattern from - the [section below](#examples) `----dry-run` produces the following output: + the [section below](#examples) `--dry-run` produces the following output: [](https://postimg.cc/bs4pRJmX) - After finding a good overall pattern, *use the `--output=` option* to create a new file and don't overwrite your existing file. Thus, your original file isn't broken if the key formatter produces some unwanted output. +- Its possible to update citekey based PDF and note files directly when + formatting the citekeys using the `-u`/`--update-attachments` option. Thus, + all PDFs and notes are already linked to the correct entries after updating + the citekeys. Since this operation can break things, use it with `--dry-run` + first. As with regular citekeys this will print all changes without processing + anything. - Even very long patterns are possible, they are not encouraged, since it bloats the bibfiles. - The same accounts for *too short* patterns; if the pattern is to unspecific, |