emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Tom Schutter <t.schutter@comcast.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: linum-mode + org-indent-mode cursor movement problems [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2/lisp/org/)]
Date: Fri, 17 Nov 2017 23:30:50 +0100	[thread overview]
Message-ID: <87po8gtu5h.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <2478d6d8-e0f0-b5d2-f6d1-5a3a694a5042@comcast.net> (Tom Schutter's message of "Wed, 15 Nov 2017 16:58:00 -0700")

Hello,

Tom Schutter <t.schutter@comcast.net> writes:

> If both linum-mode (or nlinum-mode) and org-indent-mode are enabled,
> then moving the cursor to the previous line using <up> causes it to
> jump horizontally to the right.  The jump matches the current
> indentation.  I would expect the cursor to remain in the same column.
>
> Load linum.org (contents below) with minimal config.  linum.org will
> enable linum-mode and org-indent-mode:
>
>   emacs -Q linum.org
>
> Place your cursor on the "2" in the fourth line and press <up>.  The
> cursor will jump two columns to the right to the "4" in the third
> line. Press <up> again and the cursor will move to the "4" in the
> second line. Press <up> again and the cursor will jump back to the "e"
> in the first line.
>
> What is interesting is that you get different behavior when using
> <down>.  The cursor remains in the same column as you move down each
> line.  So starting on the "e" in the first line, pressing <down> moves
> the cursor to the "2" on the second line.
>
> If you insert a second level heading in between the first and the
> second line, then the jumps will be four columns instead of two.
>
> I discovered this problem first in nlimum-mode, but it is easier to
> reproduce using linum-mode when starting Emacs with -Q.
>
> Contents of linum.org:
>
>   * heading
>   1234 line 2
>   1234 line 3
>   1234 line 4
>   # Local Variables:
>   # eval: (org-indent-mode 1)
>   # eval: (linum-mode 1)
>   # End:

I don't think it's worth fixing: linum.el and nlinum.el are on their way
out since Emacs 26 will ship with the same feature, implemented at the
C level.

It would be nice to know, however, if there is the same problem with
that new implementation.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-11-17 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 23:58 Bug: linum-mode + org-indent-mode cursor movement problems [8.2.10 (release_8.2.10 @ /usr/share/emacs/25.2/lisp/org/)] Tom Schutter
2017-11-17 22:30 ` Nicolas Goaziou [this message]
2017-11-17 23:18   ` Tom Schutter
2017-11-18 10:32     ` Nicolas Goaziou
2017-11-18 13:17     ` Kaushal Modi
2017-11-19 14:24   ` Eric S Fraga
  -- strict thread matches above, loose matches on Subject: below --
2017-11-14 15:30 Tom Schutter

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87po8gtu5h.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=t.schutter@comcast.net \
    /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/org-mode.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).