:open navigation

[sebastinas]

On GitLab by @dmfay on May 10, 2022, 05:40

---

hi! Right now completion makes opening files trickier or at least more effortful than necessary. In particular, pressing tab always completes the very first possible entry immediately, e.g. entering :o <tab> yields :open /home/dian/most/recent/file.pdf, or :o ~/downloads<tab> yields :open /home/dian/downloads/last/known/file/there.pdf (even if that file doesn't exist anymore). I have a few ideas for improvements:

• use arrow keys to move up or down the current completion list, if one is visible
• tab-complete more like the shell over the union of recent files (filtered by current path, if any), openable files in the current path if it's a directory, and subdirectories visible from the current path (if a directory)
• initial tab press completes only to ambiguity (:o <tab> yields :open /home/dian/ since I've never opened a pdf elsewhere, add tax<tab> to resolve up to /home/dian/taxes/20)
• subsequent tabs cycle through the current filtered list (keep pressing tab to cycle through tax years)

[CrispDeserving]

Good day. On the specific point that @dmfay mentioned, I wanted to be able to change the keybinding on navigating the completion list, so we have more options than just <tab>/<s-tab>. Thanks.

[nickmarks00]

Bumping this - it would be ideal to be able to navigate more easily through the completion list. Currently as others have mentioned <tab> will open the completion list but highlight the top entry (since I have recent files showing, this is my most recent file). It would be good if there were ways to move through both lists (Perhaps <Ctrl-n> and ` for Vim-like shortcuts)