all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 48409-done@debbugs.gnu.org
Subject: bug#48409: Text runs away before user can copy it
Date: Fri, 14 May 2021 10:07:03 +0300	[thread overview]
Message-ID: <83fsypztd4.fsf@gnu.org> (raw)
In-Reply-To: <87cztt4yg9.5.fsf@jidanni.org>

> From: 積丹尼 Dan Jacobson
>  <jidanni@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.





  reply	other threads:[~2021-05-14  7:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  6:32 bug#48409: Text runs away before user can copy it 積丹尼 Dan Jacobson
2021-05-14  7:07 ` Eli Zaretskii [this message]
2021-05-14 17:58   ` Juri Linkov
2021-05-14 18:46     ` Eli Zaretskii
2021-05-15 12:29       ` 積丹尼 Dan Jacobson
2021-05-15 12:34         ` Eli Zaretskii
2021-05-14 19:45     ` Eli Zaretskii
2021-05-14 19:51       ` bug#48409: [External] : " Drew Adams
2021-05-14 20:13       ` Eli Zaretskii
2021-05-14 20:53         ` Alan Mackenzie
2021-05-15  5:56           ` Eli Zaretskii
2021-05-15 11:15             ` Alan Mackenzie
2021-05-17 20:53       ` Juri Linkov
2021-05-18 13:13         ` Eli Zaretskii
2021-05-18 18:42           ` Alan Mackenzie
2021-05-18 19:05             ` Eli Zaretskii
2021-05-18 20:23               ` Alan Mackenzie
2021-05-19 12:12                 ` Eli Zaretskii
2021-05-19 15:49                   ` Alan Mackenzie
2021-05-19 17:40                 ` martin rudalics
2021-05-20 16:54                   ` martin rudalics
2021-05-21 20:55                     ` Alan Mackenzie
2021-05-22  8:05                       ` martin rudalics
2021-05-22 11:42                         ` Alan Mackenzie
2021-05-22 14:36                           ` martin rudalics
2021-05-22 15:12                             ` Eli Zaretskii
2021-05-22 16:36                               ` martin rudalics
2021-05-30 15:44                           ` Alan Mackenzie
2021-05-31  7:55                             ` martin rudalics
2021-05-31 10:44       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83fsypztd4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48409-done@debbugs.gnu.org \
    --cc=jidanni@jidanni.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.