From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Emacs terminology (not again!?) Date: Sat, 18 Jan 2014 00:53:50 -0800 Message-ID: <52DA411E.7090800@dancol.org> References: <877gact76s.fsf@gnu.org> <34c8c13b-c5c6-4e5a-9248-b09d5d1936da@default> <87eh4hkq6c.fsf@fencepost.gnu.org> <52D9E005.6030509@dancol.org> <52D9EEDD.9060109@dancol.org> <83wqhxk7sm.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1390035303 23598 80.91.229.3 (18 Jan 2014 08:55:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 18 Jan 2014 08:55:03 +0000 (UTC) Cc: per@starback.se, lennart.borgman@gmail.com, rms@gnu.org, dak@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 18 09:55:10 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W4RgK-0002gV-UR for ged-emacs-devel@m.gmane.org; Sat, 18 Jan 2014 09:55:09 +0100 Original-Received: from localhost ([::1]:41646 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W4RgK-00006v-Cn for ged-emacs-devel@m.gmane.org; Sat, 18 Jan 2014 03:55:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41009) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W4RgD-0008W9-1p for emacs-devel@gnu.org; Sat, 18 Jan 2014 03:55:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W4Rg8-00017u-AL for emacs-devel@gnu.org; Sat, 18 Jan 2014 03:55:00 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:45307) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W4Rft-00016h-IM; Sat, 18 Jan 2014 03:54:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=6XSijio9+0Y9kedx+hz9O6RMbExl4SKZUN2nha4bi4s=; b=jXxWX9mPeh7lBuNQzLDU9xFLkTHJ3cB31VQYPFQ6SVPUcaULWW/V/P9RDDFKQTWlDY2ENSdttGgpG/xcwNIyTIBbM8MCrrewbmSarbcq7SXSKTSjhXJWSVzyl0530kQm/e0Hc+wcGssyNeFvCzPeYl3uoGZ8jb7JNt1MDGbbXTS9aKA7uQesTT2H1nnE1ve39L/zVkQgpkiui7xLPSHwxE8vKb6g1oEx7cxmpkUF0V+U38Z4vFTKo/FfUhlGR6XYGqeJeedAC3gAIQgwCbJGj7QTOMtpIb4Gc9jnvevx5nz3i0oGBSKKY366FBv7DsTfmBzLEF1kPTmE9QyJp7mH2g==; Original-Received: from [173.252.71.189] (helo=[172.20.16.222]) by dancol.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1W4Rfp-0004E7-Qc; Sat, 18 Jan 2014 00:54:37 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: <83wqhxk7sm.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:168658 Archived-At: On 01/18/2014 12:34 AM, Eli Zaretskii wrote: >> Date: Fri, 17 Jan 2014 19:02:53 -0800 >> From: Daniel Colascione >> Cc: Per Starbäck , >> "Richard M. Stallman" , David Kastrup , >> "emacs-devel@gnu.org" >> >> Try making a mode that allows point to be off-screen while scrolling >> like it can be in most other editors. > > It is a common misconception that Emacs cannot do this. It can. How > do you think it pulls the trick of allowing you to scroll pixel-wise > through a very large image? Thanks. I never use Emacs to view images, so I didn't know we could do that. > It is a UI design decision in Emacs to always show point on screen. > But nothing prevents us from writing a mode that leaves point off > screen, or even abandoning that decision if we want (and I'm not > saying we do). The infrastructure is there, check out the vscroll > thingy and window-vscroll. Interesting. I may have to play with this functionality more after the feature freeze. Is (set-window-vscroll nil 500 t) supposed to move the window viewport? I didn't see anything change when I tried it in a quick test.