From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.help Subject: Re: prevent scroll-lock-mode from scrolling? Date: Mon, 20 Jun 2016 10:33:44 +0200 Message-ID: <20160620083344.GC18825@tuxteam.de> References: <871t3waaa8.fsf@heimdali.yagibdah.de> <83eg7wcnwj.fsf@gnu.org> <8760t7l8cg.fsf@heimdali.yagibdah.de> <834m8qc2nb.fsf@gnu.org> <87mvmgpwf9.fsf@heimdali.yagibdah.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed X-Trace: ger.gmane.org 1466411674 11415 80.91.229.3 (20 Jun 2016 08:34:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Jun 2016 08:34:34 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jun 20 10:34:29 2016 Return-path: Envelope-to: geh-help-gnu-emacs@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 1bEuf7-0008UI-FV for geh-help-gnu-emacs@m.gmane.org; Mon, 20 Jun 2016 10:34:29 +0200 Original-Received: from localhost ([::1]:42079 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEuf6-0007np-LA for geh-help-gnu-emacs@m.gmane.org; Mon, 20 Jun 2016 04:34:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45369) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEued-0007ms-OV for help-gnu-emacs@gnu.org; Mon, 20 Jun 2016 04:34:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bEueX-0004r7-Tw for help-gnu-emacs@gnu.org; Mon, 20 Jun 2016 04:33:58 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]:52020 helo=tomasium.tuxteam.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bEueX-0004o6-O1 for help-gnu-emacs@gnu.org; Mon, 20 Jun 2016 04:33:53 -0400 Original-Received: from tomas by tomasium.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1bEueO-0005ID-Rt for help-gnu-emacs@gnu.org; Mon, 20 Jun 2016 10:33:44 +0200 In-Reply-To: <87mvmgpwf9.fsf@heimdali.yagibdah.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 5.199.139.25 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:110522 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Jun 20, 2016 at 01:54:02AM +0200, lee wrote: > Eli Zaretskii writes: [...] > > No, the problem is that your terminology is very different from what > > we use in Emacs. When you say "point moves", the usual meaning of > > this is that point changes its buffer position. But what you actually > > mean is "cursor changes its screen position". > > I was assuming that 'point' means the position where letters appear when > I type, i. e. where the cursor is. Yes, but the question is "relative to what"? Q: where are you? A: I'm here, in the middle of the living room Now, if the question came from an intergalactic starship zipping around at 0.95c, one would have to take Earth's exquisite dance around itself, around the Sun, Sun's dance around... you get the idea. [...] > The position of the cursor /within the buffer/ is irrelevant for where > it is /on the screen/. It is relevant to me where the cursor is /on the > screen/ and /which buffer contents/ are around this screen position > (because I want to see them). It is pretty much irrelevant at which > position /within the buffer/ the contents I want to see are. I need > them displayed on the screen in a desirable way, and when programming, > the order and content of the lines I'm looking at are most of the time > much more important than it is where within the buffer they are. (It > doesn't matter whether a function 'foo' is at line 500 or at line 5000 > as long as it is declared before being used (which isn't required, but > it is what I do.)) The only sense I can make of that is: you don't want point to move relative to the window *and* you don't want window to move relative to buffer. I know you can't mean that. At least it doesn't make sense to me, because it would inhibit any movement. So I must be misundertanding you. regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAldnqmgACgkQBcgs9XrR2kYepACfVwqOXafH0GW2Lzd2GIiWWdUK hSIAniP6N4aysyOfW43P87xW6SBJqtns =ljbq -----END PGP SIGNATURE-----