all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Matt Armstrong <matt@rfc20.org>
Cc: 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 21:25:24 +0300	[thread overview]
Message-ID: <83zggj27e3.fsf@gnu.org> (raw)
In-Reply-To: <87zggjrjb4.fsf@rfc20.org> (message from Matt Armstrong on Thu, 04 Aug 2022 10:48:47 -0700)

> From: Matt Armstrong <matt@rfc20.org>
> Cc: yet@ego.team, uzibalqa@proton.me, larsi@gnus.org, 56870@debbugs.gnu.org
> Date: Thu, 04 Aug 2022 10:48:47 -0700
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> 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.
> 
> 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.





  reply	other threads:[~2022-08-04 18:25 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zggj27e3.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.