all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: `ido.el' small, but annoying bug
Date: Mon, 06 Dec 2004 14:15:50 +0100	[thread overview]
Message-ID: <m3llcbr2ih.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <200412042030.49707.pogonyshev@gmx.net> (Paul Pogonyshev's message of "Sat, 4 Dec 2004 20:31:03 +0200")

Paul Pogonyshev <pogonyshev@gmx.net> writes:

> Kim F. Storm wrote:
>> Paul Pogonyshev <pogonyshev@gmx.net> writes:
>> > Type `C-x b', use left/right arrow to select a different buffer
>> > and then `C-k' to kill it.  With my Emacs (a recent CVS) the
>> > list of buffers disappears, but can be reshown again by e.g.
>> > pressing left/right arrow.
>> >
>> > The following smallish patch seems to fix it.  However, `ido.el'
>> > maintainer should certainly review it.
>>
>> You patch looks ok, but I don't see the bug myself, so I wonder why it
>> happens for you.  Does it happen if you enable ido in emacs -q ?
>
> Actually, my patch doesn't fully solve the problem.  When you hit
> `C-x b C-k' (without left/right arrow), the bug persists with the
> patch too.

If I start emacs -Q and use your customizations, the problem is
still not visible to me.

I suspect the problem is with some interference with some other
package which tries to use the minibuffer or echo area when you
kill a buffer.

Can you start with emacs -Q, and then gradually enable the
various customizations you use to see which one triggers the bug.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2004-12-06 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 18:05 `ido.el' small, but annoying bug Paul Pogonyshev
2004-12-04  0:51 ` Kim F. Storm
2004-12-04  1:13   ` Paul Pogonyshev
2004-12-04 18:31   ` Paul Pogonyshev
2004-12-06 13:15     ` Kim F. Storm [this message]
2004-12-06 16:25       ` Urban Engberg
2004-12-06 17:49         ` Paul Pogonyshev

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=m3llcbr2ih.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.