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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#48409: closed (Text runs away before user can copy it)
Date: Fri, 14 May 2021 07:07:01 +0000

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

Your message dated Fri, 14 May 2021 10:07:03 +0300
with message-id <83fsypztd4.fsf <at> gnu.org>
and subject line Re: bug#48409: Text runs away before user can copy it
has caused the debbugs.gnu.org bug report #48409,
regarding Text runs away before user can copy it
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
48409: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48409
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <at> gnu.org
Subject: Text runs away before user can copy it
Date: Fri, 14 May 2021 14:32:54 +0800

Do e.g.,
M-! cat /etc/motd

OK now in the minibuffer are several lines of juicy text.

Now grab the mouse and attempt to copy that text.

Alas, upon clicking, the text disappears.

Pro users know better, but average bumpkin users will be frustrated.

So maybe have the minibuffer stay put / stay open during this sequence of events.

[Message part 3 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 48409-done <at> debbugs.gnu.org
Subject: Re: bug#48409: Text runs away before user can copy it
Date: Fri, 14 May 2021 10:07:03 +0300

> From: 積丹尼 Dan Jacobson
>  <jidanni <at> jidanni.org>
> Date: Fri, 14 May 2021 14:32:54 +0800
> 
> Do e.g.,
> M-! cat /etc/motd
> 
> OK now in the minibuffer are several lines of juicy text.
> 
> Now grab the mouse and attempt to copy that text.
> 
> Alas, upon clicking, the text disappears.
> 
> Pro users know better, but average bumpkin users will be frustrated.
> 
> So maybe have the minibuffer stay put / stay open during this sequence of events.

Please RTFM.  The doc string of M-! says, inter alia:

  If COMMAND ends in ‘&’, execute it asynchronously.
  The output appears in the buffer ‘*Async Shell Command*’.
  That buffer is in shell mode.  You can also use
  ‘async-shell-command’ that automatically adds ‘&’.

  Otherwise, COMMAND is executed synchronously.  The output appears in
  the buffer ‘*Shell Command Output*’.  If the output is short enough to
  display in the echo area (which is determined by the variables
  ‘resize-mini-windows’ and ‘max-mini-window-height’), it is shown
  there, but it is nonetheless available in buffer ‘*Shell Command
  Output*’ even though that buffer is not automatically displayed.

(The user manual has a similar text.)

So the text you want is still available in an Emacs buffer, and you
can take it from there.

Closing.

Previous Next

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