unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27932@debbugs.gnu.org
Subject: bug#27932: 26.0.50; Feature request: prevent scroll commands from changing the buffer location of point
Date: Fri, 4 Aug 2017 08:34:11 +0200	[thread overview]
Message-ID: <CAH8Pv0j2rp6_NQ7Cmd_5ok7PW0RVvv0oRM4Vyj9aQkTboucK=w@mail.gmail.com> (raw)
In-Reply-To: <83ini3yi49.fsf@gnu.org>

On Fri, Aug 4, 2017 at 8:14 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> [Did you really mean to make this a private email?]

Oh no.  Sorry.  I'm adding the ticket address back.

>> > It would require a complete rewrite of most of the display engine
>> > code.  The Emacs display engine is based on the principle that point
>> > should always be visible, so whenever it becomes invisible, Emacs
>> > scrolls the window to make it visible again.  The display code checks
>> > this in many places, and they all will need to be changed in some, yet
>> > unspecified, way.
>>
>> I was afraid of the above.  Well it's your call to judge if this is worth it.
>
> I don't have anything against coding such a feature, but I myself
> won't be doing that any time soon, if ever.  It's just a too large
> project for my resources, and my motivation for doing this is zero,
> since I'm always annoyed by this behavior I find in MS Word.

I see.   :-(   :-)

>> > Emacs provides the mark and "C-x C-x" as a way to jump between two
>> > locations without requiring the feature you describe.  If the purpose
>> > of what you want is some other use case, I think it would be good to
>> > have it described.
>>
>> I can see several benefits in the requested feature:
>> * To have a way to explore a buffer without seeing a distracting
>> cursor jumping around.
>
> "Distracting cursor"?  If it distracts you, you can make it a bar
> instead of a block.

I want the cursor to be a block, so I can spot it easily on the
screen.  But I don't want to see it when I'm doing a "exploring trip"
in the buffer.

>> * To have a behavior which is standard in may other editors (where the
>> position of the cursor wrt the text is not altered by scrolling
>> commands).
>
> That's not a reasoning for the feature, because it doesn't provide any
> rationale in terms of utility.

Well, the point is that the requested behavior is a standard one among
many other editors.  I think this is something relevant to consider.

>> * To have an intuitive, quick and convenient way to explore the
>> neighborhood of point (e.g. using C-v, M-v or the mouse-wheel) and
>> then "return" (move the viewport back) to the point.
>
> How is this different from "C-x C-x"?

Well, it is similar, but "C-x C-x" requires you to push the mark
before you leave.  And users with little experience in Emacs may be
used to this workflow from their experience in other editors.

-- 
Dani Moncayo





  parent reply	other threads:[~2017-08-04  6:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 13:34 bug#27932: 26.0.50; Feature request: prevent scroll commands from changing the buffer location of point Dani Moncayo
2017-08-03 16:42 ` Eli Zaretskii
     [not found]   ` <CAH8Pv0gjYZZAfciNTaqKcj37C51dSdJOzD+4AZFFY2wjOu6Fgg@mail.gmail.com>
     [not found]     ` <83ini3yi49.fsf@gnu.org>
2017-08-04  6:34       ` Dani Moncayo [this message]
2017-08-04 21:36   ` Richard Stallman
2017-08-05  6:44     ` Eli Zaretskii
2017-08-05 20:19       ` Richard Stallman
2017-08-06 17:18         ` Eli Zaretskii
2017-08-06 21:00           ` Dani Moncayo
2017-08-07  2:28             ` Eli Zaretskii
2017-08-07  5:54               ` Dani Moncayo
2017-08-07 12:32                 ` Tak Kunihiro
2017-08-07 16:38                 ` Eli Zaretskii
2017-08-07 21:09                   ` Dani Moncayo
2017-08-03 17:56 ` martin rudalics
2017-08-03 23:16 ` Tak Kunihiro
2017-08-04  6:15   ` Eli Zaretskii
2017-08-04  6:39     ` Tak Kunihiro
2017-08-04  8:01       ` Eli Zaretskii
2017-08-04 10:33         ` Tak Kunihiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8Pv0j2rp6_NQ7Cmd_5ok7PW0RVvv0oRM4Vyj9aQkTboucK=w@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=27932@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).