From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Andrew W. Nosenko" Newsgroups: gmane.emacs.devel Subject: Re: C-x C-x Date: Tue, 21 Sep 2010 12:22:01 +0300 Message-ID: References: <87eicrx1ls.fsf@catnip.gol.com> <4C94E03D.8090002@gmail.com> <87fwx699pc.fsf@catnip.gol.com> <83tylmyclx.fsf@gnu.org> <4C961787.3090907@gmail.com> <878w2xsigj.fsf@gmail.com> <87zkvd5hwa.fsf@catnip.gol.com> <87ocbrv8mi.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1285061951 5898 80.91.229.12 (21 Sep 2010 09:39:11 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 21 Sep 2010 09:39:11 +0000 (UTC) Cc: emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 21 11:39:09 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OxzJX-0000f6-B8 for ged-emacs-devel@m.gmane.org; Tue, 21 Sep 2010 11:39:08 +0200 Original-Received: from localhost ([127.0.0.1]:32872 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OxzJS-00036J-5a for ged-emacs-devel@m.gmane.org; Tue, 21 Sep 2010 05:38:58 -0400 Original-Received: from [140.186.70.92] (port=51340 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OxzB2-0006Qz-1F for emacs-devel@gnu.org; Tue, 21 Sep 2010 05:30:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oxz34-0005H5-Gc for emacs-devel@gnu.org; Tue, 21 Sep 2010 05:22:07 -0400 Original-Received: from mail-qw0-f41.google.com ([209.85.216.41]:55220) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oxz34-0005Gu-ET; Tue, 21 Sep 2010 05:22:02 -0400 Original-Received: by qwf7 with SMTP id 7so5843417qwf.0 for ; Tue, 21 Sep 2010 02:22:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5c+rLQFu2nuyQ/vcy1fJ43VZ/DBLp7AhBK4ITmM7+pY=; b=wi4fu2apHaxTrj98QgrZ9xktR3whSqcesK02y2XtmhUodjbC6CVGQx3v9D5MxUFN9G oCRZcuKn5QiMD7r7BuUOvN9pTyOOlcidXX0bakHVT4s/eNcbyqJHKAJYXaPnO8UG7t2W CYVbZqawcxUCRiqYRUf9EvCHU1TkeGYyhmL2U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xqt4HF4NX4F+jXKlNWaScVTBiClTdZBHwPau/ifRvyHYnpny6rUbD0f3fDmvcJU3vD TQT3kLqlaGsuj6r7C1smeM1RBar/NgJ6AKfmJbB6uZ63Hm3mAF/IF+GU6Tyu9CRc5W4w IvXV6KYmbkKwfVWt0JzlDTux1Pls/FL0X7PM0= Original-Received: by 10.224.96.144 with SMTP id h16mr6546854qan.372.1285060921565; Tue, 21 Sep 2010 02:22:01 -0700 (PDT) Original-Received: by 10.229.25.201 with HTTP; Tue, 21 Sep 2010 02:22:01 -0700 (PDT) In-Reply-To: <87ocbrv8mi.fsf@lola.goethe.zz> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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: news.gmane.org gmane.emacs.devel:130569 Archived-At: On Tue, Sep 21, 2010 at 10:49, David Kastrup wrote: > "Andrew W. Nosenko" writes: > >> About stop activating region by C-x C-x. =A0I'm (of course) unable to >> speak for anyone who uses t-m-m, but for me C-x C-x, same as C-x C-x >> C-x C-x is intentionally thing for activating region. =A0And usual goal >> is to send this region to the external filter (as in C-x C-x C-u M-|). > > This works perfectly fine without activating the region first. May be :-) But I'm personally feel self very uncomfortable when don't see what going to be changed (the region in this concrete case). It is similar to search&replace: it very convinient to see the "going to be changed peice of text" highlighted and [for me] would be very uncomfortable if S&R would not highlight matched text. --=20 Andrew W. Nosenko