From: uzibalqa <uzibalqa@proton.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Accessing "Introduction to Emacs Lisp Manual" from Info within Emacs.
Date: Fri, 07 Jul 2023 14:34:35 +0000 [thread overview]
Message-ID: <2sitMI6nW5Y3rIrngsL4du7rLEnIgUbpwGln8UxaetmJz9fv2R8jrwT5hxYGUQk4gKBVifswq8OHLpCnUDMyWWBMPm1DlQtDkwnytFxWtCI=@proton.me> (raw)
In-Reply-To: <83a5w7g6ec.fsf@gnu.org>
------- Original Message -------
On Saturday, July 8th, 2023 at 2:09 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > 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>
Furthermore, please note that after calling 'm' users cannot input strings
with spaces for "Emacs Lisp Intro".
next prev parent reply other threads:[~2023-07-07 14:34 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 [this message]
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
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='2sitMI6nW5Y3rIrngsL4du7rLEnIgUbpwGln8UxaetmJz9fv2R8jrwT5hxYGUQk4gKBVifswq8OHLpCnUDMyWWBMPm1DlQtDkwnytFxWtCI=@proton.me' \
--to=uzibalqa@proton.me \
--cc=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).