From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: highlight with mouse then shouldn't need kill-ring-save? Date: Fri, 28 Jan 2005 07:59:47 -0500 Message-ID: <87wttx3eie.fsf-monnier+emacs@gnu.org> References: <87hdl42khp.fsf@jidanni.org> <200501280341.j0S3fk026612@raven.dms.auburn.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1106919873 2458 80.91.229.6 (28 Jan 2005 13:44:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 28 Jan 2005 13:44:33 +0000 (UTC) Cc: emacs-devel@gnu.org, Luc Teirlinck , rms@gnu.org, jidanni@jidanni.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 28 14:44:19 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CuWQ7-00032A-00 for ; Fri, 28 Jan 2005 14:44:19 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CuWcV-00076d-FL for ged-emacs-devel@m.gmane.org; Fri, 28 Jan 2005 08:57:07 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CuWcC-00073g-Ng for emacs-devel@gnu.org; Fri, 28 Jan 2005 08:56:48 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CuWPu-0004jL-9a for emacs-devel@gnu.org; Fri, 28 Jan 2005 08:44:06 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CuWPd-0004RA-Tv for emacs-devel@gnu.org; Fri, 28 Jan 2005 08:43:50 -0500 Original-Received: from [209.226.175.34] (helo=tomts13-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CuVj2-00030n-Mo; Fri, 28 Jan 2005 07:59:48 -0500 Original-Received: from alfajor ([67.71.119.166]) by tomts13-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20050128125948.OUDJ1899.tomts13-srv.bellnexxia.net@alfajor>; Fri, 28 Jan 2005 07:59:48 -0500 Original-Received: by alfajor (Postfix, from userid 1000) id 484C4D7344; Fri, 28 Jan 2005 07:59:47 -0500 (EST) Original-To: David Kastrup In-Reply-To: (David Kastrup's message of "Fri, 28 Jan 2005 12:34:55 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:32606 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:32606 > Providing a transient region as an X selection would appear > independently useful, and normally what people would expect. I'm not sure if that's really what people expect. The region is often used for reasons unrelated to copy/kill/.... E.g. to "undo" only in the region, or to comment out a chunk of text, or ... Overwriting some other X selection in those cases may not be what people want. This is without considering the potential performance impact (at least if we use the CUT buffer). Furthermore, nobody ever complained about having to do M-w to put the region in the X selection. The only thing which was brought up is that there is no visual representation of the X selection: in some cases it's highlighted as the active region, in other cases it's not highlighted at all, in yet other cases, the active region is highlighted but has nothing to do with the X selection. Maybe we should highlight the X selection with something like the secondary-selection face, using a separate overlay (independent from the region), which would get unhighlighted as soon as the X selection is taken by some other X app. Stefan