From: Eli Zaretskii <eliz@gnu.org>
To: YE <yet@ego.team>
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: Thu, 04 Aug 2022 19:41:06 +0300 [thread overview]
Message-ID: <83czdg2c7x.fsf@gnu.org> (raw)
In-Reply-To: <m235ecgfhv.fsf@ego.team> (bug-gnu-emacs@gnu.org)
> Cc: yet@ego.team, uzibalqa@proton.me, larsi@gnus.org, 56870@debbugs.gnu.org
> Date: Thu, 04 Aug 2022 19:06:36 +0300
> From: YE via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> My take on the 'Init File' docs improvement is attached.
Thanks. However, this basically adds to the Emacs manual stuff whose
place is in the ELisp manual. So I'm not sure we should start on this
slippery slope. Users who need to write complex Lisp in their init
files need to read the ELisp manual anyway.
next prev parent reply other threads:[~2022-08-04 16:41 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 [this message]
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
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=83czdg2c7x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56870@debbugs.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).