From b74f2c59a75a867b1e7b2cf462d6e2b22d6e6085 Mon Sep 17 00:00:00 2001 From: contrapunctus Date: Tue, 4 Aug 2020 03:21:28 +0530 Subject: [PATCH] TODO - add example for #9 --- TODO.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/TODO.md b/TODO.md index bade93f..abb71d6 100644 --- a/TODO.md +++ b/TODO.md @@ -8,6 +8,6 @@ * When files are marked in Dired and we mark files in sxiv - replace the selection, or unmark the files marked this time * Other options like running recursively, modifying arguments, etc 6. [ ] When running with a lot of files, sxiv may take some time to start. Signal to the user that it is starting, and let them kill it if they want. -7. [ ] sxiv-exclude-strings does not work recursively, because only the directories are passed to the process. Adding all files to the path might cause it to fail (bash length limit), or take a long time. +7. [ ] `sxiv-exclude-strings` does not work recursively, because only the directories are passed to the process. Adding all files to the path might cause it to fail (bash length limit), or take a long time. 8. [ ] Make it work in find-dired buffers too -9. [ ] Bug - sometimes, if a lot of files (e.g. >50) are marked in sxiv, the input received by `sxiv-insert-subdirs` is incomplete (i.e. the first file name is a trailing segment of an actual existing filename). +9. [ ] Bug - sometimes, if a lot of files (e.g. >50) are marked in sxiv, the input received by `sxiv-insert-subdirs` is incomplete (i.e. the first file name is a trailing segment of an actual existing filename, e.g. if a file is called `"foo/bar_baz.jpg"`, I might get something like `"r_baz.jpg"` as the first element).