From: YE via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: matt@rfc20.org, yet@ego.team, uzibalqa@proton.me, larsi@gnus.org,
56870@debbugs.gnu.org
Subject: bug#56870: [PATCH] Re: bug#56870: company-dabbrev variable documentation
Date: Sat, 06 Aug 2022 15:42:15 +0300 [thread overview]
Message-ID: <m2edxt5ys8.fsf@ego.team> (raw)
In-Reply-To: <83a68j0wwy.fsf@gnu.org> (message from Eli Zaretskii on Fri, 05 Aug 2022 14:09:17 +0300)
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
>> Eli Zaretskii:
>> From: YE
>> Which part _exactly_ you don't find suitable for the Emacs manual?
>
> All of it. You explain some basics of Emacs Lisp, which any user who
> is serious about customizing his/her Emacs should already know about,
> by reading the relevant parts of the ELisp manual.
>> Don't Symbols deserve the same attention as Numbers, Strings,
>> Characters described extensively in `(emacs) Init Syntax'?
>
> No, I don't think so. And this is a slippery slope anyway, because
> there's more about Lisp objects than just telling what you suggest to
> tell.
>> What part of the patch touches the "complex Lisp"?
>
> Why does this text have to talk about doc strings, and what does it
> have to do with the syntax of the init file? And the node to which
> you refer is a large and complex node, which is too much for simple
> customizations that Init Syntax intends to cover.
>
Thank you for the detailed response.
>> From: Matt Armstrong
>> Eli, perhaps a single link to the ELisp manual near the beginning of
>> "(emacs) Init Syntax" would be acceptable?
>
> Yes, that's a better idea.
One more tiny patch is attached.
It links 'Init Syntax' to the ELisp manual Introduction node.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Link from Init Syntax to ELisp Introduction --]
[-- Type: text/x-patch, Size: 806 bytes --]
From 68a2732383e48096296da208215590c5afc62971 Mon Sep 17 00:00:00 2001
From: YugaEgo <yet@ego.team>
Date: Sat, 6 Aug 2022 15:20:09 +0300
Subject: [PATCH] Link from (emacs)Init Syntax to (elisp)Introduction
* doc/emacs/custom.texi (Init Syntax): Link to the ELisp manual (Bug#56870)
---
doc/emacs/custom.texi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
index 6ed43bcb79..efaf0dfd38 100644
--- a/doc/emacs/custom.texi
+++ b/doc/emacs/custom.texi
@@ -2452,6 +2452,9 @@ Init Syntax
Write a single-quote (@code{'}) followed by the Lisp object you want.
@end table
+ For more information on the Emacs Lisp syntax, @pxref{Introduction,,,
+elisp, The Emacs Lisp Reference Manual}.
+
@node Init Examples
@subsection Init File Examples
--
2.34.1
next prev parent reply other threads:[~2022-08-06 12:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 3:54 bug#56870: company-dabbrev variable documentation uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:24 ` Matt Armstrong
2022-08-01 21:32 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:49 ` Matt Armstrong
2022-08-01 21:55 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-01 21:49 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-02 10:20 ` Lars Ingebrigtsen
2022-08-02 10:34 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-03 10:07 ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-03 18:41 ` Matt Armstrong
2022-08-03 18:50 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 17:09 ` Matt Armstrong
[not found] ` <878ro4rl4l.fsf@rfc20.org-N8dpYwc----2>
2022-08-04 21:59 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 16:06 ` bug#56870: [PATCH] " YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 16:41 ` Eli Zaretskii
2022-08-04 17:48 ` Matt Armstrong
2022-08-04 18:25 ` Eli Zaretskii
2022-08-05 9:10 ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:09 ` Eli Zaretskii
2022-08-05 11:36 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-06 12:42 ` YE via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-06 13:19 ` Eli Zaretskii
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=m2edxt5ys8.fsf@ego.team \
--to=bug-gnu-emacs@gnu.org \
--cc=56870@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=matt@rfc20.org \
--cc=uzibalqa@proton.me \
--cc=yet@ego.team \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).