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 19:17:31 +0000 [thread overview]
Message-ID: <iQ0IFk4NhVUSwoP3fW1hTxh2qaHtduJQYpmS5Hvavgdbb3ehVhL03vodeH8bGBcoXTRWp6ARLealKZWFOmpHdEEbYpRDZuCQTHR9ehNrPb8=@proton.me> (raw)
In-Reply-To: <83lefree0u.fsf@gnu.org>
------- Original Message -------
On Saturday, July 8th, 2023 at 7:07 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > 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.
Am not objecting to having Emacs-related items together. The suggestion is
to sub-categorise the different Emacs-related items under the Emacs Heading.
Obviously, some are basic (e.g. emacs and elisp manuals), others are about
special modes (CC, Octave, Org), whilst others are much more advanced (mail
systems and other interfaces).
next prev parent reply other threads:[~2023-07-07 19:17 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
2023-07-07 19:17 ` uzibalqa [this message]
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='iQ0IFk4NhVUSwoP3fW1hTxh2qaHtduJQYpmS5Hvavgdbb3ehVhL03vodeH8bGBcoXTRWp6ARLealKZWFOmpHdEEbYpRDZuCQTHR9ehNrPb8=@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).