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:07:45 +0300 [thread overview]
Message-ID: <83lefree0u.fsf@gnu.org> (raw)
In-Reply-To: <1vb8ad2VV3RmiCeG915Z7HlXvEw15L1umde9g7lR8hqFQWvwIdVO9mhL_YwBlbUgF6gEaq7Bov_2Y49FVAc5Jicm5Wpnrk5TdESCUQ7Reas=@proton.me> (message from uzibalqa on Fri, 07 Jul 2023 18:32:21 +0000)
> Date: Fri, 07 Jul 2023 18:32:21 +0000
> From: uzibalqa <uzibalqa@proton.me>
> Cc: help-gnu-emacs@gnu.org
>
> > > Date: Fri, 07 Jul 2023 15:31:51 +0000
> > > From: uzibalqa uzibalqa@proton.me
> > > Cc: help-gnu-emacs@gnu.org
> > >
> > > Could we group the Emacs Nodes according to some categorisation ?
> >
> >
> > We already do.
>
> Nodes are not categorised when scrolling down Info (dir)Top and reaching Emacs.
> All Emacs nodes huddled together.
Which is exactly the categorization that we want to have there, to
make it easier for users to find Emacs-related items.
next prev parent reply other threads:[~2023-07-07 19:07 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
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 [this message]
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=83lefree0u.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).