unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Accessing "Introduction to Emacs Lisp Manual" from Info within Emacs.
Date: Fri, 07 Jul 2023 16:02:51 +0000	[thread overview]
Message-ID: <E4wDpgDc7lPCF3W8hP2_qxEPNUKcxcQGI4sjnEy1vFyerlUPy0I1jjDpjJrIGzV9sM-jKkAY0w208bpCqCY0HwDHzX9AG1mJt2AQGhZpIWM=@proton.me> (raw)
In-Reply-To: <87h6qfiuy5.fsf@rub.de>

------- Original Message -------
On Saturday, July 8th, 2023 at 3:48 AM, Stephen Berman <stephen.berman@gmx.net> wrote:


> On Fri, 07 Jul 2023 15:41:01 +0000 uzibalqa uzibalqa@proton.me wrote:
> 
> > ------- Original Message -------
> > On Saturday, July 8th, 2023 at 3:12 AM, Stephen Berman
> > stephen.berman@gmx.net wrote:
> > 
> > > On Fri, 07 Jul 2023 17:49:54 +0300 Eli Zaretskii eliz@gnu.org wrote:
> > > 
> > > > > Date: Fri, 07 Jul 2023 14:34:35 +0000
> > > > > From: uzibalqa uzibalqa@proton.me
> > > > > Cc: help-gnu-emacs@gnu.org
> > > > > 
> > > > > > > Date: Fri, 07 Jul 2023 13:57:32 +0000
> > > > > > > From: uzibalqa uzibalqa@proton.me
> > > > > > > 
> > > > > > > How can I access "Introduction to Emacs Lisp Manual" from Info
> > > > > > > within Emacs.
> > > > > > 
> > > > > > It's on the Help menu, under "More Manuals".
> > > > > > 
> > > > > > Alternatively, "C-h i" shows a large menu, where you should be able to
> > > > > > find this manual as one of the possibilities.
> > > > > 
> > > > > I can easily get the "Emacs Manual", the "Emacs Lisp Manual". Both with
> > > > > "C-h i m" . So way skip "Emacs Lisp Intro".
> > > > > 
> > > > > I do not have to search for the two aforementioned manuals, so let's not
> > > > > have users search for "Emacs Lisp Intro" either.
> > > > > 
> > > > > This is my suggestion
> > > > > 
> > > > > C-h i m elintr <Ret>
> > > > 
> > > > We have a better one: "C-h i m Emacs Lisp Intro RET"
> > > 
> > > This also works:
> > > 
> > > g, then at the prompt: (eintr) RET
> > 
> > Managed to get it to work. It would be quicker to forego the need
> > for parentheses when using "g".
> 
> 
> Without the parentheses `g' only recognizes nodes in the current Info
> file. The parentheses are needed to jump to a different Info file, and
> you can add a node name after the parentheses; omitting the node name
> sends you to the top-level node of the file named in the parentheses.
> 
> Steve Berman

If I am in Info (dir)Top, why not allow me using "g" without the parentheses.
After all, why require users to know the different info file names.  I do not see
it easy to find the list of info files directly from "The Info Directory" (dir)Top.

All these things are not self evident for newbies, who want to view the manuals.
And I do not see an Intro for newbies on how to use Info within Emacs to view manuals.

Perhaps there can be a categorisation of Info File Names that can be perused ?




  reply	other threads:[~2023-07-07 16:02 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 [this message]
2023-07-07 18:14               ` Eli Zaretskii
2023-07-07 18:46                 ` uzibalqa
2023-07-07 19:12                   ` Eli Zaretskii
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='E4wDpgDc7lPCF3W8hP2_qxEPNUKcxcQGI4sjnEy1vFyerlUPy0I1jjDpjJrIGzV9sM-jKkAY0w208bpCqCY0HwDHzX9AG1mJt2AQGhZpIWM=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=help-gnu-emacs@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.
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).