From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: eggert@cs.ucla.edu, iperryman@xtreme-eda.com, 23842@debbugs.gnu.org
Subject: bug#23842: 24.4; Runaway background process
Date: Mon, 27 Jun 2016 18:49:41 +0300 [thread overview]
Message-ID: <83lh1qy6lm.fsf@gnu.org> (raw)
In-Reply-To: <02ecaa18-2108-e5c7-c7c4-56896a9c2869@cornell.edu> (message from Ken Brown on Mon, 27 Jun 2016 09:24:06 -0400)
> From: Ken Brown <kbrown@cornell.edu>
> Date: Mon, 27 Jun 2016 09:24:06 -0400
> Cc: 23842@debbugs.gnu.org
>
> ;; Show possible completions in a temporary buffer.
> (with-output-to-temp-buffer "*Completions*"
> (display-completion-list allcomp))
> ;; Wait for a key press. Then delete *Completion* window
> (momentary-string-display "" (point))
> (delete-window (get-buffer-window (get-buffer "*Completions*")))))
>
> It's hard to see how this could possibly work. As soon as you click in
> the *Completion* window, the window is deleted.
It could perhaps work if we didn't check the window for being a live
one.
Anyway, the code is definitely broken and should be fixed.
next prev parent reply other threads:[~2016-06-27 15:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 19:08 bug#23842: 24.4; Runaway background process Ian Perryman
2016-06-24 20:02 ` bug#23842: Dribble files Ian Perryman
2016-06-25 7:00 ` Eli Zaretskii
2016-06-26 0:55 ` Ian Perryman
2016-06-25 6:50 ` bug#23842: 24.4; Runaway background process Eli Zaretskii
2016-06-25 20:49 ` Noam Postavsky
2016-06-26 2:37 ` Eli Zaretskii
2016-06-26 8:51 ` Paul Eggert
2016-06-26 17:04 ` Glenn Morris
2016-06-26 19:02 ` Ian Perryman
2016-06-26 19:50 ` Paul Eggert
2016-06-27 12:46 ` Ian Perryman
2016-06-27 13:24 ` Ken Brown
2016-06-27 13:51 ` Ian Perryman
2016-08-14 2:36 ` npostavs
2016-12-20 3:58 ` npostavs
2016-06-27 15:49 ` Eli Zaretskii [this message]
2016-06-27 16:54 ` Ken Brown
2016-06-26 19:48 ` Paul Eggert
2016-12-21 23:37 ` Wilson Snyder
2016-12-22 2:44 ` npostavs
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=83lh1qy6lm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23842@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=iperryman@xtreme-eda.com \
--cc=kbrown@cornell.edu \
/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).