unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Jim Rees <jim@rees.org>
Cc: acm@muc.de, Eli Zaretskii <eliz@gnu.org>, 65116@debbugs.gnu.org
Subject: bug#65116: 29.1; query-replace-read-args fails reading second arg in detached minibuf
Date: Fri, 12 Jan 2024 17:28:06 +0000	[thread overview]
Message-ID: <ZaF2pieafDHN8tOi@ACM> (raw)
In-Reply-To: <ZaFhzo19nGNoVL1k@rees.org>

Hello, Jim.

On Fri, Jan 12, 2024 at 09:59:10 -0600, Jim Rees wrote:
> Normally this happens when I'm trying to edit text in a buffer. I only
> mention the scratch buffer in the bug report because that's the easiest way
> to reproduce the problem.

> The mouse starts out somewhere in the window displaying the text I'm trying
> to edit. I type M-%, enter the 'from' text, and when I hit <enter> the mouse
> warps to the upper right corner of the window. I get the 'to' prompt but
> then I can't type anything because the focus is on the edit window, not on
> the minibuf.

> I don't think it matters where in the text window the mouse starts out, but
> it's hard to tell. About 10% of the time M-% works correctly but I can't
> figure out why. I'll try to see if it has something to do with mouse
> position.

> Can you try with twm? It is lightweight and should run with no
> configuration. I'm at a loss as to why I'm seeing this bug and no one else
> is.

I've installed twm which, as you say, is lightweight (~250 kB) but it
pulled in a ~750 kB font with it.  ;-)  No big deal (like it would have
been 30 years ago).

I can reproduce the bug with this set up.  With the mouse starting in
the text frame, the bug as you describe it happens, and the mouse must
be moved to the minibuffer frame to be able to type in the replacement
text.

If the mouse starts in the MB frame, typing M-% allows one to enter
original and replacement texts without moving the mouse, but this is
useless, since it then attempts to substitute in the mini-window.

I'll have a closer look at this to see if I can fix it.  But things with
detached minibuffers and focus are complicated and have given rise to
quite a few bugs over the years.  Add in focus follows mouse, and it
gets more complicated still.  ;-(

Reading between the lines, it would appear you're still on Emacs 28
because of this bug.  That's a pity, and it would be good to fix things.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2024-01-12 17:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 17:18 bug#65116: 29.1; query-replace-read-args fails reading second arg in detached minibuf Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-07 15:57 ` Eli Zaretskii
2024-01-12  6:26   ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 12:00     ` Eli Zaretskii
2024-01-12 14:38       ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 15:25       ` Alan Mackenzie
2024-01-12 15:37 ` Alan Mackenzie
2024-01-12 15:59   ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 17:28     ` Alan Mackenzie [this message]
2024-01-12 18:57       ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 21:44         ` Alan Mackenzie
2024-01-13  6:34           ` Eli Zaretskii
2024-01-13  9:23             ` Alan Mackenzie
2024-01-13 13:47               ` Alan Mackenzie
2024-01-13 17:00                 ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13 17:47                   ` Alan Mackenzie
2024-01-13 19:15                   ` Drew Adams
2024-01-13 20:18                     ` Alan Mackenzie
2024-01-13 21:19                       ` Drew Adams
2024-01-13 21:35                         ` Alan Mackenzie
2024-01-13 20:06                   ` Alan Mackenzie
2024-01-13 23:53                     ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  6:21                       ` Eli Zaretskii
2024-01-14 14:33                         ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 15:03                           ` Alan Mackenzie
2024-01-14 16:59                         ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 17:17                           ` Eli Zaretskii
2024-01-14 17:33                             ` Eli Zaretskii
2024-01-14 19:10                               ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 19:42                                 ` Eli Zaretskii
2024-01-15  0:27                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  1:29                                     ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  3:38                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  4:52                                         ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  6:31                                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 16:47                                             ` Jim Rees via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  0:27             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:14               ` Alan Mackenzie

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=ZaF2pieafDHN8tOi@ACM \
    --to=acm@muc.de \
    --cc=65116@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jim@rees.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).