From: Benjamin Petrenko <benjamin.petrenko@gmail.com>
To: 20980@debbugs.gnu.org
Subject: bug#20980: Re: bug#20980: 24.5; Bash completion doesn't work properly
Date: Sun, 05 Jul 2015 18:03:38 +0000 [thread overview]
Message-ID: <87mvzaxz0l.fsf@gmail.com> (raw)
In-Reply-To: <87twtj514x.fsf@gmail.com>
I guess "bash completion" is a wrong term, since in this case Emacs does
the auto-completion. What did I expect? I expected a *Completions*
buffer with possible completions to show up. Instead, I saw "No match"
in the minibuffer.
next prev parent reply other threads:[~2015-07-05 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 16:38 bug#20980: 24.5; Bash completion doesn't work properly Benjamin Petrenko
2015-07-04 18:58 ` Stefan Monnier
2015-07-05 18:03 ` Benjamin Petrenko [this message]
2019-09-29 22:50 ` Stefan Kangas
2019-10-30 20:31 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvzaxz0l.fsf@gmail.com \
--to=benjamin.petrenko@gmail.com \
--cc=20980@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).