From: "Ángel González" <ingenit@zoho.com>
To: util-linux@vger.kernel.org
Subject: Wrong more(1) bash-completion on filenames with spaces
Date: Mon, 01 Jul 2013 16:49:00 +0200 [thread overview]
Message-ID: <51D196DC.9070401@zoho.com> (raw)
The bash completion for more(1) treats the space-separated pieces of
filenames as different files.
$ touch foo\ bar
$ more foo<TAB>
bar foo
Trying to hint the space doesn't help, either:
more foo\<TAB> → more foo\\
more foo\\<TAB> → more foo\\\\
more foo\\ <TAB> → more foo\\\
Workaround: Remove the bash completion and use the default one:
$ chmod a-r /usr/share/bash-completion/completions/more
next reply other threads:[~2013-07-01 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 14:49 Ángel González [this message]
2013-09-30 13:51 ` Wrong more(1) bash-completion on filenames with spaces Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51D196DC.9070401@zoho.com \
--to=ingenit@zoho.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox