Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mutt -f +file<tab> loses the + upon expansion #464

Open
mgedmin opened this issue Nov 11, 2020 · 0 comments · May be fixed by #465
Open

mutt -f +file<tab> loses the + upon expansion #464

mgedmin opened this issue Nov 11, 2020 · 0 comments · May be fixed by #465

Comments

@mgedmin
Copy link
Contributor

mgedmin commented Nov 11, 2020

With #463 applied I can expand mail folders with mutt -f =nam<tab>, but mutt -f +nam<tab> eats the + upon expansion, producing mutt -f name, which doesn't work.

PR incoming.

mgedmin added a commit to mgedmin/bash-completion that referenced this issue Nov 11, 2020
@mgedmin mgedmin linked a pull request Nov 11, 2020 that will close this issue
mgedmin added a commit to mgedmin/bash-completion that referenced this issue Nov 11, 2020
I haven't fully understood how exactly this happens, but sometimes
(Ubuntu 18.04) '=foo' ends up as a single word in COMP_WORDS, despite
COMP_WORDBREAKS containing '='.  At other times '=foo' is split into two
words, '=' and 'foo'.

If COMP_WORDS[$COMP_CWORD] had the '+' or '=' prefix, we need to make
sure COMPREPLY also includes it, or we'll lose it.

Closes scop#464, in a better way.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant