From: Eli Zaretskii <eliz@gnu.org>
To: rgm@gnu.org, 9607-done@debbugs.gnu.org, david_lawless@flumedata.com
Subject: bug#9607: incorrect behavior with "auto-hscroll-mode nil" in ncurses/vt220 text operation; wrong in 23 but ok in 22.1
Date: Thu, 29 Sep 2011 16:06:13 +0300 [thread overview]
Message-ID: <83oby3ebwa.fsf@gnu.org> (raw)
In-Reply-To: <E1R8Qp6-0006b6-6J@fencepost.gnu.org>
> Date: Tue, 27 Sep 2011 02:07:20 -0400
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 9607@debbugs.gnu.org, david_lawless@flumedata.com
>
> The problem is that line-move-visual assumes that the move begins with
> cursor positioned at point, which is false when auto-hscroll-mode is
> turned off and point is scrolled out of view.
>
> Before I dive into this mess (again), do we even want to support
> auto-hscroll-mode nil _and_ visual line movement? What if we tell
> line-move to invoke logical line movement instead when
> auto-hscroll-mode is off? Would someone object?
No one objected, so I fixed this in revision 105959 on the trunk by
disabling visual line movement when auto-hscroll-mode is disable and
the window is hscrolled.
next prev parent reply other threads:[~2011-09-29 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201109262119.p8QLJ5eU004406@siobhan.>
2011-09-26 21:36 ` bug#9607: David Lawless
2011-09-27 0:33 ` bug#9607: incorrect behavior with "automatic-hscroll-mode nil" in ncurses/vt220 text operation; wrong in 23 but ok in 22.1 Glenn Morris
2011-09-27 0:47 ` David Lawless
2011-09-27 2:29 ` Stefan Monnier
2011-09-27 2:43 ` bug#9607: incorrect behavior with "auto-hscroll-mode " David Lawless
2011-09-27 4:01 ` Glenn Morris
2011-09-27 6:07 ` Eli Zaretskii
2011-09-29 13:06 ` Eli Zaretskii [this message]
2011-09-27 3:10 ` bug#9607: incorrect behavior with "auto-hscroll-mode nil" in ncurses/vt220 text operation; wrong in 23.2 but ok in 23.1 David Lawless
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83oby3ebwa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9607-done@debbugs.gnu.org \
--cc=david_lawless@flumedata.com \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.