From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "David De La Harpe Golden" Newsgroups: gmane.emacs.devel Subject: Re: scroll-restore.el Date: Fri, 22 Feb 2008 19:41:56 +0000 Message-ID: <8e24944a0802221141i45a3c6a8xf9c92a695deb1557@mail.gmail.com> References: <87myq4saw1.fsf@catnip.gol.com> <86lk5f4fjb.fsf@timbral.net> <87ejb7babz.fsf@xmission.com> <85lk5fcod6.fsf@lola.goethe.zz> <8e24944a0802201446g3329febcw190f78145e3f5c4e@mail.gmail.com> <47BD2883.20009@gmx.at> <8e24944a0802220811s752c5c8axcfe92bed0402880b@mail.gmail.com> <47BF2337.2090003@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1203709420 8296 80.91.229.12 (22 Feb 2008 19:43:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 22 Feb 2008 19:43:40 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: "martin rudalics" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 22 20:43:53 2008 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.50) id 1JSdn3-0000pk-DA for ged-emacs-devel@m.gmane.org; Fri, 22 Feb 2008 20:42:37 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JSdmY-0002ZU-53 for ged-emacs-devel@m.gmane.org; Fri, 22 Feb 2008 14:42:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JSdmT-0002Ys-UR for emacs-devel@gnu.org; Fri, 22 Feb 2008 14:42:01 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JSdmS-0002Ya-Bj for emacs-devel@gnu.org; Fri, 22 Feb 2008 14:42:01 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JSdmS-0002YX-8f for emacs-devel@gnu.org; Fri, 22 Feb 2008 14:42:00 -0500 Original-Received: from gv-out-0910.google.com ([216.239.58.185]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JSdmR-00073I-SZ for emacs-devel@gnu.org; Fri, 22 Feb 2008 14:42:00 -0500 Original-Received: by gv-out-0910.google.com with SMTP id y18so369742gvf.17 for ; Fri, 22 Feb 2008 11:41:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=VS91kRJg89hvBZ+U7A1KUHaHZ4K5z5PsI5fntShS1H4=; b=uf0SR8kQn87VsLVU5SV+4lngy0SwHWJZJWwGiKhi4RDmt4aaqZfrd7bRZKAzZSpcN6Tot+ps2BVeUbLZjCUB1pDxD0qMpUjGgjOSCseojgV5ISsqHTzdX2ujwpYDJQ/ZqhWAEwiSNT9OmwpMCptBPQ/W80vskEb0gunS0WEGvmg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MGMXhHYs2IlUKLnny1OJDfPKVioCvuNJZVdglo9o9F3WeM4xkdYpyoCfjP7+UD5yvwdJSqc1KeXUh+noFzcX3iSP5ow7mxT2gsXgAYhs+GuUl/XG6GjYrxkwWZ/u1UbGhIVl7xveCPJnJgjiNzb/+Pm1h7L5tBJ46Dg5M6av7UU= Original-Received: by 10.142.131.18 with SMTP id e18mr357823wfd.36.1203709316679; Fri, 22 Feb 2008 11:41:56 -0800 (PST) Original-Received: by 10.143.17.10 with HTTP; Fri, 22 Feb 2008 11:41:56 -0800 (PST) In-Reply-To: <47BF2337.2090003@gmx.at> Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Google Wireless Transcoder (1) 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:90008 Archived-At: On 22/02/2008, martin rudalics wrote: > > Well, that is perhaps useful on its own. But just to note, some of > > the additional features are probably needed to address the > > transient-mark-mode region selection concern in the context where > > Martin introduced scroll-restore - e.g. handle-region and jump-back. > > (handle region just gives the appearance that an active region can go > > offscreen, > > > Yes. I found it useful when showing the same buffer in two windows. > Scrolling one window wouldn't relocate the region in the other. > > > > jump back is apparently then needed so that the region is > > really reset to the pre-scrolled region just before the kill, > > otherwise the real region at scrolled time is killed). > > > No. The region is restored automatically when the original position is > restored. ... But that means you would have to restore the position (e.g. by scrolling back "manually") before hitting kill? in other systems, it is conventional for the C-x/C-c cut/copy to do the kill of the partially or totally scrolled-offscreen active region (not of a different region, which is what happens without jump-back, unless I'm still misunderstanding) - i.e. for this purpose, jump back is involved so as to jump back to restore the point position so as to insta-restore the original region just before kill.