all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: chad <yandros@MIT.EDU>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12193@debbugs.gnu.org
Subject: bug#12193: 24.1.50; 24.1.50; Completion broken in revno 109116
Date: Mon, 13 Aug 2012 14:04:47 -0700	[thread overview]
Message-ID: <AE989CC9-BD62-4ED1-B88C-A423D8000E11@mit.edu> (raw)
In-Reply-To: <83sjbqk3fx.fsf@gnu.org>


On 13 Aug 2012, at 12:16, Eli Zaretskii <eliz@gnu.org> wrote:

>> From: chad <yandros@MIT.EDU>
>> Date: Mon, 13 Aug 2012 11:23:33 -0700
>> 
>> 1. Run `emacs -Q'.
>> 2. Type: `C-x 1' (make sure there is only one window)
>> 3. Type: `C-x C-f /tm TAB'
>> 4. Emacs creates a new window for the completions, but puts the cursor
>>   in the wrong window (it's back in the original window, not
>>   *Completions* or the minibuffer.
> 
> I cannot reproduce this with the current trunk.

I'm still seeing the problem, but my recipe was off.  Try this instead:

1. mkdir /tmp/emacsbug-foo1 /tmp/emacsbug-foo2
2. Run `emacs -Q'.
3. Type: `C-x C-f /tmp/emacsbug-foo TAB'
4. Emacs creates a new window for the completions, but puts the cursor
  in the wrong window (it's back in the original window, not
  *Completions* or the minibuffer.

It seems to be important that there is more than one completion for the current prefix string, presumably so emacs will create the *Completions* buffer. That was true on my system but probably not generally true.

With this recipe, it still happens in revno 109117.

Thank you.
*Chad






  reply	other threads:[~2012-08-13 21:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 18:23 bug#12193: 24.1.50; 24.1.50; Completion broken in revno 109116 chad
2012-08-13 19:16 ` Eli Zaretskii
2012-08-13 21:04   ` chad [this message]
2012-08-14  2:50     ` Daiki Ueno
2012-08-14  3:19       ` Daiki Ueno
2012-08-14  3:29         ` chad
2012-08-14 15:41           ` Eli Zaretskii
2012-08-14 15:59             ` chad
2012-08-14  4:37       ` Chong Yidong
2012-08-14  2:50     ` Eli Zaretskii

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=AE989CC9-BD62-4ED1-B88C-A423D8000E11@mit.edu \
    --to=yandros@mit.edu \
    --cc=12193@debbugs.gnu.org \
    --cc=eliz@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.