unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 44929@debbugs.gnu.org
Subject: bug#44929: 28.0.50; Info-next-reference skips next reference
Date: Sat, 28 Nov 2020 21:44:19 +0200	[thread overview]
Message-ID: <83h7p9mfl8.fsf@gnu.org> (raw)
In-Reply-To: <87360tjnht.fsf@gmx.net> (message from Stephen Berman on Sat, 28 Nov 2020 20:21:50 +0100)

> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Sat, 28 Nov 2020 20:21:50 +0100
> 
> 0. emacs -Q
> 1. C-h r (if emacs is installed, otherwise `C-u h i /path/to/emacs.info
>    RET')
> 2. Repeat `C-n' until the cursor is on the '*' before the first menu
>    item 'Distrib'.
> 3. Type TAB
> => The cursor jumps over 'Distrib' and goes to the second menu item
>    'Intro'.
> 
> The same thing happens if the cursor is on the space between '*' and
> 'Distrib' and you then press TAB.  In both cases, I expected the cursor
> to go to the immediately following link instead of skipping it.

AFAIU, your expectation is wrong: TAB runs the command
Info-next-reference, where the "next" part means "not the current
one".  For the "current" reference, press RET.

The stand-alone Info reader behaves the same.  So this is not a bug,
and I don't think we can change that in Emacs, even if we'd agree with
you (and I don't think I do).

Thanks.





  reply	other threads:[~2020-11-28 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 19:21 bug#44929: 28.0.50; Info-next-reference skips next reference Stephen Berman
2020-11-28 19:44 ` Eli Zaretskii [this message]
2020-11-28 19:54   ` Stephen Berman
2020-11-28 20:10     ` Drew Adams
2020-11-28 20:22       ` Eli Zaretskii
     [not found] <<87360tjnht.fsf@gmx.net>
     [not found] ` <<83h7p9mfl8.fsf@gnu.org>
     [not found]   ` <<87tut9i7fa.fsf@gmx.net>
     [not found]     ` <<2cb435b4-7de8-4783-9830-44195c111aca@default>
     [not found]       ` <<83czzxmdtm.fsf@gnu.org>
2020-11-28 20:56         ` Drew Adams

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=83h7p9mfl8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44929@debbugs.gnu.org \
    --cc=stephen.berman@gmx.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.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).