[Bash-completion-devel] [bash-completion-Bugs][312881] mutt completion chokes on piped 'source' argument

bash-completion-bugs at alioth.debian.org bash-completion-bugs at alioth.debian.org
Mon Dec 20 21:48:18 UTC 2010


Bugs item #312881, was changed at 2010-12-11 17:38 by Ville Skyttä 
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312881&group_id=100114

>Status: Closed
Priority: 3
Submitted By: Nobody (None)
>Assigned to: Ville Skyttä  (scop-guest)
Summary: mutt completion chokes on piped 'source' argument 
Distribution: --Distribution-Agnostic--
Originally reported in: None
>Milestone: 2.0
>Status: Fix Committed
Original bug number: 


Initial Comment:
My IMAP and SMTP passwords for mutt are secured in an encrypted file. I extract them when mutt starts using `source "gpg --no-mdc-warning -d ~/.mutt/muttrc.pwd.gpg |"` in my muttrc. Bash completion then gives the error 'sed: can't read gpg: No such file or directory'. Basically, the regexp looking for sourced files in the '_muttconffiles()' function of the mutt bash_completion script should ignore lines that end in a pipe '|'. As an easier alternative, the script could silently ignore arguments that don't resolve to existing files.

----------------------------------------------------------------------

>Comment By: Ville Skyttä  (scop-guest)
Date: 2010-12-20 23:48

Message:
http://git.debian.org/?p=bash-completion/bash-completion.git;a=commitdiff;h=2d4ebba

----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312881&group_id=100114



More information about the Bash-completion-devel mailing list