all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: short *Shell Command Output* and mouse "bait and switch"
Date: Fri, 03 May 2002 13:35:39 +0300	[thread overview]
Message-ID: <1225-Fri03May2002133538+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <m2k7qmniol.fsf_-_@jidanni.org> (message from Dan Jacobson on 03 May 2002 09:06:50 +0800)

> From: Dan Jacobson <jidanni@deadspam.com>
> Newsgroups: gnu.emacs.bug
> Date: 03 May 2002 09:06:50 +0800
> 
> You must admit that it is a bug to make things disappear when the user
> is about to cut and paste them.  What other software acts this way?

Many programs behave similarly when such ``transient'' messages are
involved.  For example, fire up your Web browser, then move the mouse
pointer above some link.  Most browsers will display the URL of that
link down below, in the area that resembles the Emacs echo area.  But
if you try to move the mouse there, with the intent of copying the
URL into the clipboard or the X selection, the URL disappears.

Anyway, I'm not trying to say Emacs shouldn't allow to copy the
messages, I was just trying to help you find the specific elusive
message you mentioned.

> <escape> ! s e q SPC 1 SPC 1 SPC 5 <return>
> now try to copy say, the "3" with your mouse.
> Is all the flashing and error messages not a bug?
> Why not just let the user copy what he sees?

The CVS code places you in the *Messages* buffer when you click in the
echo area, so you should be able to copy the text from taht buffer.

      reply	other threads:[~2002-05-03 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02  0:37 short *Shell Command Output* buffer afraid of mice and everything else Dan Jacobson
2002-05-02 15:54 ` Eli Zaretskii
2002-05-03  1:06   ` short *Shell Command Output* and mouse "bait and switch" Dan Jacobson
2002-05-03 10:35     ` Eli Zaretskii [this message]

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=1225-Fri03May2002133538+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=bug-gnu-emacs@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.