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: Sat, 08 Jul 2023 09:17:38 +0300 [thread overview]
Message-ID: <838rbrdj0d.fsf@gnu.org> (raw)
In-Reply-To: <FJ7HDoF8j78o8Z07RxIZRUGhXVzELgRM_PA7AihcfCm_crqk0Auz6zhN5MNXPdpZeRHfjsSRsTrp4Vny2CSAYtxsdZQNm6ZuvwyPSSNDyVo=@proton.me> (message from uzibalqa on Fri, 07 Jul 2023 20:10:57 +0000)
> Date: Fri, 07 Jul 2023 20:10:57 +0000
> From: uzibalqa <uzibalqa@proton.me>
> Cc: help-gnu-emacs@gnu.org
>
> > > > > Am not objecting to having Emacs-related items together. The suggestion is
> > > > > to sub-categorise the different Emacs-related items under the Emacs Heading.
> > > >
> > > > They are there already, you even show them in your original message.
> > >
> > > They are not.
> >
> >
> > Yes, they are: look at the file DIR that comes with Emacs.
>
> I am using GNU Emacs 29.0.50 and there exists no categorisation once
> you get to the Emacs parts.
If you built Emacs yourself, look at the file info/dir in the build
tree.
If someone else built it, ask them about it.
next prev parent reply other threads:[~2023-07-08 6: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
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 [this message]
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=838rbrdj0d.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).