From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Something like `without-redisplay'?
Date: Tue, 01 Sep 2015 18:57:03 +0300 [thread overview]
Message-ID: <83a8t6ceuo.fsf@gnu.org> (raw)
In-Reply-To: <CAKu-7WxJYYKFq9uPGr4begwOTUpaY5_zGX83UEiJ70kM+a4xFg@mail.gmail.com>
> Date: Tue, 1 Sep 2015 17:24:08 +0200
> From: Alexander Shukaev <haroogan@gmail.com>
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
>
> >> behave incorrectly when window has non-zero horizontal scroll. The
> >> problem might be deep in how Emacs implements `next-line' or
> >> `previous-line' or whatever.
> >
> > More likely, the function in question has bug.
> >
> >> But I found a solution, when I use `evil-previous-visual-line' and
> >> `evil-next-visual-line' in my own functions, I simply wrap their
> >> calls into the `devil-without-window-hscroll' macro, so that during
> >> their execution there is no horizontal scrolling.
> >
> > I'd suggest to find the bug in the function and fix it instead.
>
> I'd love to, but I'm no expert with these. Unfortunately, can't
> afford some time for this now.
Did you report the problem to the maintainer of that code? If not, I
suggest to do that.
> > It can in rare cases, if you scroll vertically. It all depends on
> > what the code does, exactly.
>
> OK, then here is an example
>
> (save-excursion (scroll-down 10)) ;; just scroll
> (previous-line 10) ;; then move point with the method we want
>
> I've tested it and so far, I see no problems with it. I think there
> is another option to do the same like this
>
> (save-window-excursion (previous-line 10)) ;; just move point with the
> method we want
> (save-excursion (scroll-down 10)) ;; then scroll
>
> Which one is more reliable? Can I even expect any problems with these codes?
Not with these, I think. I'm sorry, I cannot give any precise
instructions regarding what not to do, except repeating that in
general it is very unlikely that you will see point moving when Lisp
code takes care to return point to the same place and does not change
the window configuration. I just know that some code paths inside
redisplay are capable of moving point if they otherwise cannot satisfy
the constraints of vertical position of point, such as scroll-margin.
> > Horizontal scrolling doesn't move point, AFAIR.
>
> Even if `auto-hscroll-mode' is on (which it is by default)?
auto-hscroll-mode does the opposite: it scrolls the display to move
point into the view. It doesn't move point.
next prev parent reply other threads:[~2015-09-01 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 9:49 Something like `without-redisplay'? Alexander Shukaev
2015-08-31 14:23 ` Eli Zaretskii
2015-08-31 19:32 ` Alexander Shukaev
2015-08-31 23:37 ` Alexander Shukaev
2015-09-01 2:39 ` Eli Zaretskii
2015-09-01 13:56 ` Alexander Shukaev
2015-09-01 14:52 ` Eli Zaretskii
2015-09-01 15:24 ` Alexander Shukaev
2015-09-01 15:57 ` Eli Zaretskii [this message]
2015-09-01 16:10 ` Alexander Shukaev
2015-09-01 16:47 ` Alexander Shukaev
2015-09-01 17:00 ` Eli Zaretskii
2015-09-01 17:24 ` Alexander Shukaev
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=83a8t6ceuo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).