all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: uyennhi.qm@gmail.com, 42050-done@debbugs.gnu.org
Subject: bug#42050: 27.0.91; Clarify Info-next docstring
Date: Fri, 26 Jun 2020 10:43:12 +0300	[thread overview]
Message-ID: <83d05ms25r.fsf@gnu.org> (raw)
In-Reply-To: <87a70qkei9.fsf@calancha-pc.dy.bbexcite.jp> (message from Tino Calancha on Thu, 25 Jun 2020 23:43:42 +0200)

> Cc: eliz@gnu.org,uyennhi.qm@gmail.com
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Thu, 25 Jun 2020 23:43:42 +0200
> 
> When I am reading a section of the Emacs manual, then I
> often assume that `p' and `n' behavior is like when you are
> reading a book, i.e. jump to the prev/next page; i.e., my
> natural expectation is that `n' is bound to `Info-forward-node'.
> 
> I think their docstrings could add some
> description and mention to the other existent command.
> 
> You get my point in this patch:

Thanks, I fixed this in a slightly different way.

P.S. Do you really use [ and ] in Info when reading a manual?





  reply	other threads:[~2020-06-26  7:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 21:43 bug#42050: 27.0.91; Clarify Info-next docstring Tino Calancha
2020-06-26  7:43 ` Eli Zaretskii [this message]
2020-06-26  8:41   ` Basil L. Contovounesios
2020-06-26 10:31     ` Eli Zaretskii
2020-06-26 11:32       ` Basil L. Contovounesios
     [not found] ` <handler.42050.D42050.159315742012378.notifdone@debbugs.gnu.org>
2020-06-26 15:36   ` bug#42050: closed (Re: bug#42050: 27.0.91; Clarify Info-next docstring) Tino Calancha
2020-06-26 17:53     ` Eli Zaretskii
2020-06-28 16:48       ` Tino Calancha

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=83d05ms25r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42050-done@debbugs.gnu.org \
    --cc=tino.calancha@gmail.com \
    --cc=uyennhi.qm@gmail.com \
    /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.