unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 5042@debbugs.gnu.org, 9917@debbugs.gnu.org,
	monnier@iro.umontreal.ca, dmoncayo@gmail.com
Subject: bug#9917: bug#5042: bug#9917: 24.0.90; Make `goto-line' consistent with the line number from the minibuffer
Date: Fri, 30 Oct 2020 09:27:43 +0200	[thread overview]
Message-ID: <87r1pgch84.fsf@mail.linkov.net> (raw)
In-Reply-To: <83sg9xaysh.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Oct 2020 16:31:58 +0200")

>> 2. Re-bind 'M-g g' to goto-line-relative as many asked to do
>>    with the reasoning that 'M-g g' should use by default the
>>    same numbering scheme as is displayed by display-line-numbers-mode;
>
> Two comments:
>
>  1) display-line-numbers-mode by default behaves the same as
>     line-number-mode
>  2) display-line-numbers-mode has the display-line-numbers-widen
>     option which disregards narrowing, so if you want to follow
>     display-line-numbers-mode, you will need to heed that option as
>     well
>
>> 3. Leave the existing 'M-g g' bound to goto-line, but allow changing
>>    the numbering scheme using a prefix arg and a user option.
>
> I like this the best.

If making the current goto-line 'M-g g' more DWIM is not easy to do,
maybe really a user option could help with such choices:

- always use absolute line numbers;
- always use relative line numbers;
- follow the value of display-line-numbers-widen;
...

Also more explicit keys are needed, e.g.:

M-g l a   - with mnemonics: goto line absolute
M-g l r   - with mnemonics: goto line relative





  reply	other threads:[~2020-10-30  7:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 14:31 bug#9917: 24.0.90; Make `goto-line' consistent with the line number from the minibuffer Dani Moncayo
2011-11-01  9:35 ` Juri Linkov
2011-11-01 17:56   ` Stefan Monnier
2011-11-01 22:35     ` Juri Linkov
2011-11-01 23:22       ` Drew Adams
2011-11-02  9:48         ` Juri Linkov
2011-11-02 12:59           ` Drew Adams
2011-11-02  9:46     ` Juri Linkov
2020-09-19 17:42 ` bug#5042: " Lars Ingebrigtsen
2020-09-19 18:01   ` Stefan Monnier
2020-09-19 19:27     ` bug#9917: bug#5042: " Drew Adams
2020-09-19 19:56       ` Eli Zaretskii
2020-09-19 18:33   ` Eli Zaretskii
2020-09-20  9:28     ` Lars Ingebrigtsen
2020-09-21 19:03       ` Juri Linkov
2020-09-22 14:37         ` Lars Ingebrigtsen
2020-09-22 18:08           ` Juri Linkov
2020-09-22 20:10             ` Drew Adams
2020-09-23 14:14               ` bug#5042: bug#9917: " Eli Zaretskii
2020-09-23 13:18             ` Lars Ingebrigtsen
2020-09-23 17:58               ` Drew Adams
2020-09-24  7:39                 ` Robert Pluim
2020-09-24 17:31                   ` bug#9917: " Drew Adams
2020-10-29  9:19           ` Juri Linkov
2020-10-29 14:31             ` Eli Zaretskii
2020-10-30  7:27               ` Juri Linkov [this message]
2020-10-30  8:19                 ` Eli Zaretskii
2020-10-29 16:44             ` bug#5042: " Drew Adams
2020-10-30  9:49             ` Lars Ingebrigtsen
2020-10-31 19:28               ` Juri Linkov
2020-10-31 20:00                 ` bug#5042: " Eli Zaretskii
2020-10-27 20:52         ` Juri Linkov
2020-10-28  9:48           ` bug#5042: " Lars Ingebrigtsen
2020-10-28 11:58             ` Dmitry Gutov
2020-10-30  9:44               ` Lars Ingebrigtsen
     [not found] <<CAH8Pv0jBbJoyJfW+Xh-m3kqGQnVc0eO2+kM40SJ23JOKiBrx-A@mail.gmail.com>
     [not found] ` <<877dspmzo3.fsf@gnus.org>
     [not found]   ` <<jwv4kntbqep.fsf-monnier+emacs@gnu.org>
     [not found]     ` <<28534d1c-6652-4cfe-acb4-f0a30624f878@default>
     [not found]       ` <<83tuvt1qwq.fsf@gnu.org>
2020-09-19 20:22         ` Drew Adams
2020-09-19 20:27           ` bug#9917: " Eli Zaretskii
     [not found]   ` <<83zh5l1uqw.fsf@gnu.org>
     [not found]     ` <<87wo0osspd.fsf@gnus.org>
     [not found]       ` <<87lfh3dtoj.fsf@mail.linkov.net>
     [not found]         ` <<878sd1j2rv.fsf@gnus.org>
     [not found]           ` <<871ritbs6t.fsf@mail.linkov.net>
     [not found]             ` <<cd8f2969-6705-46c8-b090-03e284b0ba0c@default>
     [not found]               ` <<83zh5gvauy.fsf@gnu.org>
2020-09-23 18:09                 ` bug#5042: " Drew Adams
2020-09-23 19:40                   ` Juri Linkov
     [not found] <<<CAH8Pv0jBbJoyJfW+Xh-m3kqGQnVc0eO2+kM40SJ23JOKiBrx-A@mail.gmail.com>
     [not found] ` <<<877dspmzo3.fsf@gnus.org>
     [not found]   ` <<<jwv4kntbqep.fsf-monnier+emacs@gnu.org>
     [not found]     ` <<<28534d1c-6652-4cfe-acb4-f0a30624f878@default>
     [not found]       ` <<<83tuvt1qwq.fsf@gnu.org>
     [not found]         ` <<1cfba469-3adf-4287-a1fa-647e4e5e83e2@default>
     [not found]           ` <<83pn6h1pie.fsf@gnu.org>
2020-09-19 21:10             ` Drew Adams
2020-09-20  5:34               ` bug#9917: " Eli Zaretskii

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=87r1pgch84.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=5042@debbugs.gnu.org \
    --cc=9917@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).