bash-complete-partial-path
bash-complete-partial-path copied to clipboard
Better demo screencast
The screencast in the README was done in a hurry after next to no planning and probably fails to convey some of the important features of bash-complete-partial-path.
This issue is a place to discuss, plan and submit a better screencast.
Current screencast outline
https://asciinema.org/a/0zhzOYbkF22pWLmbx1RHCYyqQ
- Path completion:
- for files
- for directories (with
cd
)
- Tilde expansion:
- Simple (~)
- Advanced (~1 with
pushd
)
- Escaping special characters in file path
- A directory name with spaces
- Completion of special characters with opened quotes:
- '
- "
Possible enhancements
-
Resolving ambiguity in the middle of path
All the samples in current screencast differ only in the last element of the path. Perhaps a better example would be the one with ambiguity in the middle, like
/u/s/c -> /usr/share/cygwin, /usr/ssl/cert.pem, /usr/ssl/certs
-
Side-by-side comparison with traditional completion
It would be good to have an example that shows how many keystrokes can be saved with the enhanced path completion, e.g. with something like
/usr/share/perl5/core_perl
: it would take a lot of interim tabbing with default completion and only one tab after/u/s/p/core
with this project.
How you can help
- Suggest other illustrative examples that might attract users previously unfamiliar with such completion
- Suggest a whole new outline for a better screencast
- Comment on existing outline and suggestions
- Record a better screencast with or without discussing the outline first (some tips to get started, I also recommend
-w 0.5
or-w 0.4
).
The plan is to gather some feedback and to record a replacement screencast for the README. I can do the recording myself if no one else volunteers, I just need a better outline.