From: Oleksandr Manzyuk <manzyuk@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 10457@debbugs.gnu.org
Subject: bug#10457: (Broken?) programmable completion in shell buffers
Date: Tue, 24 Jan 2012 18:28:14 +0000 [thread overview]
Message-ID: <CAAwZTsTCr47J1=zwEo9CPEiekCH2wjtHCentFxuHsy8qBgNktQ@mail.gmail.com> (raw)
In-Reply-To: <p4wr8hrmrj.fsf@fencepost.gnu.org>
On Tue, Jan 24, 2012 at 6:14 PM, Glenn Morris <rgm@gnu.org> wrote:
>
>>> When I am in a directory that doesn't contain files with a dash
>>> in the name, typing "ssh -" and hitting TAB produces only "No match"
>>> message in the minibuffer.
>
> I can't reproduce this. I get the expected completions buffer.
Meanwhile I purged the emacs-snapshot Ubuntu package and built Emacs
24.0.92 from sources, and I can confirm that this problem is gone.
The lockup issue is still there, but I have temporarily fixed it as
follows, following Thierry's idea:
(defadvice pcomplete-opt (around ensure-completions-pcomplete-opt)
"Temporary fix of bug#10457."
(or ad-do-it
(throw 'pcomplete-completions nil)))
(ad-activate 'pcomplete-opt)
--
Oleksandr Manzyuk
http://oleksandrmanzyuk.wordpress.com
next prev parent reply other threads:[~2012-01-24 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 19:40 bug#10457: (Broken?) programmable completion in shell buffers Oleksandr Manzyuk
2012-01-08 20:07 ` bug#10457: Oleksandr Manzyuk
2012-01-09 1:26 ` bug#10457: (Broken?) programmable completion in shell buffers Stefan Monnier
2012-01-09 5:56 ` Thierry Volpiatto
2012-01-09 11:17 ` Thierry Volpiatto
[not found] ` <mailman.1502.1326107965.15002.bug-gnu-emacs@gnu.org>
2012-01-10 23:27 ` manzyuk
2012-01-09 15:41 ` Oleksandr Manzyuk
2012-01-09 17:41 ` Oleksandr Manzyuk
2012-01-09 20:20 ` Oleksandr Manzyuk
2012-01-24 18:12 ` Glenn Morris
2012-01-24 18:14 ` Glenn Morris
2012-01-24 18:28 ` Oleksandr Manzyuk [this message]
2012-01-24 21:39 ` Glenn Morris
2012-01-24 22:29 ` Oleksandr Manzyuk
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='CAAwZTsTCr47J1=zwEo9CPEiekCH2wjtHCentFxuHsy8qBgNktQ@mail.gmail.com' \
--to=manzyuk@gmail.com \
--cc=10457@debbugs.gnu.org \
--cc=rgm@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).