GNU bug report logs - #48409
Text runs away before user can copy it

Previous Next

Full log

Message #64 received at 48409 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Alan Mackenzie <acm <at> muc.de>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 48409 <at> debbugs.gnu.org, juri <at> linkov.net
Subject: Re: bug#48409: Text runs away before user can copy it
Date: Wed, 19 May 2021 19:40:06 +0200

[Message part 1 (text/plain, inline)]

> The above is the basic scenario.  If the mouse is on the top line of the
> miniwindow when the mouse is clicked, the returned y coordinate at (ii)
> is in the mode line of the window above, and is determined relative to
> that window.

Are you sure?  If the click happens on the bottom line, it's still here
reported for the minibuffer window only that now the double click fuzz
rigmarole breaks in and says that the mouse has moved.

> I don't have any workable ideas on how to fix this bug.  The only idea
> which springs to mind is to move from expressing mouse positions
> relative to a window to expressing it relative to a frame.  Or, maybe
> the resizing of the miniwindow could be postponed till after the
> up-mouse event.

For clicks into the bottom line the attached might help.  Clicks above
must be caught elsewhere.  But you don't get a drag event and no error
message for them.

martin

[keyboard.c.diff (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.