unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Accessing "Introduction to Emacs Lisp Manual" from Info within Emacs.
Date: Fri, 07 Jul 2023 22:12:33 +0300	[thread overview]
Message-ID: <83jzvbedsu.fsf@gnu.org> (raw)
In-Reply-To: <EzRlPRwB818usjhmWVo3oVty4GC9pg4TN1w5pJRftgMIfraGkTrUI8CgLw2BwIzN8k4wkYKihRdblLaR3UJzApu4nhoupaYyYY1E_5F1EyY=@proton.me> (message from uzibalqa on Fri, 07 Jul 2023 18:46:55 +0000)

> Date: Fri, 07 Jul 2023 18:46:55 +0000
> From: uzibalqa <uzibalqa@proton.me>
> Cc: help-gnu-emacs@gnu.org
> 
> ------- Original Message -------
> On Saturday, July 8th, 2023 at 6:14 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> 
> > > Date: Fri, 07 Jul 2023 16:02:51 +0000
> > > From: uzibalqa uzibalqa@proton.me
> > > Cc: help-gnu-emacs@gnu.org
> > > 
> > > If I am in Info (dir)Top, why not allow me using "g" without the parentheses.
> > 
> > 
> > You are not supposed to use 'g' in this situation.
> > 
> > You have taken the least useful response to your questions and
> > disregarded all the rest. The other responses would allow you to find
> > this manual much easier, without all the weird quirks that the 'g'
> > command requires. Using 'g' for going to another manual is considered
> > "advanced usage" of Info, so it uses tricky syntax, and newbies are
> > well advised to stay away.
> 
> Going to another manual should not be "advanced usage".

That's NOT what I said, please don't misquote!  I said that going to
another manual _using_the_'g'_command_ is advanced usage.  The usual
way to go to another manual, which is recommended to users, is either
via the DIR menu (to which you can go by pressing 'd'), or "C-h R",
which prompts for the manual.

> It would be neat to have the ability to use completion for the
> different manuals available on the\ system and also have it as a
> help feature.

Both 'm' in the DIR node and "C-h R" provide completion, so we already
have that.



  reply	other threads:[~2023-07-07 19:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 13:57 Accessing "Introduction to Emacs Lisp Manual" from Info within Emacs uzibalqa
2023-07-07 14:09 ` Eli Zaretskii
2023-07-07 14:34   ` uzibalqa
2023-07-07 14:49     ` Eli Zaretskii
2023-07-07 15:12       ` Stephen Berman
2023-07-07 15:41         ` uzibalqa
2023-07-07 15:48           ` Stephen Berman
2023-07-07 16:02             ` uzibalqa
2023-07-07 18:14               ` Eli Zaretskii
2023-07-07 18:46                 ` uzibalqa
2023-07-07 19:12                   ` Eli Zaretskii [this message]
2023-07-07 15:31       ` uzibalqa
2023-07-07 18:07         ` Eli Zaretskii
2023-07-07 18:32           ` uzibalqa
2023-07-07 19:07             ` Eli Zaretskii
2023-07-07 19:17               ` uzibalqa
2023-07-07 19:38                 ` Eli Zaretskii
2023-07-07 19:51                   ` uzibalqa
2023-07-07 19:53                     ` Eli Zaretskii
2023-07-07 20:10                       ` uzibalqa
2023-07-07 21:57                         ` Stephen Berman
2023-07-08  6:17                         ` Eli Zaretskii
2023-07-08 12:48                           ` uzibalqa

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=83jzvbedsu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).