unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Matt Armstrong <matt@rfc20.org>
To: carlmarcos@tutanota.com
Cc: YE <yet@ego.team>, uzibalqa <uzibalqa@proton.me>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	56870@debbugs.gnu.org
Subject: bug#56870: company-dabbrev variable documentation
Date: Thu, 04 Aug 2022 10:09:30 -0700	[thread overview]
Message-ID: <878ro4rl4l.fsf@rfc20.org> (raw)
In-Reply-To: <N8_1vEG--3-2@tutanota.com>

carlmarcos@tutanota.com writes:

> Aug 3, 2022, 18:41 by matt@rfc20.org:
>
>> I think the maintainers are quite receptive to improvements like
>> this.
>
> I completely disagree.  The experience with maintainers has shown how
> unreceptive they often get towards improvements like this.  Lars
> thought there isn't anything to fix in Emacs and decided to close this
> bug report.

I think reasonable people can disagree about what is and is not a
problem, is or is not an improvement, or even misunderstand eachother
entirely.  Sometimes patience and additional explanations are the way to
move forward.

In this case, I agree with Lars that the company-dabbrev docstring is
consistent with Emacs' usual way of writing docstrings.  I don't
actually see a clear way to improve the one docstring in isolation
without it becoming inconsistent with the rest of Emacs.  And so, I
would expect any improvement here to involve some discussion, since the
path forward isn't obvious.





  reply	other threads:[~2022-08-04 17:09 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 [this message]
     [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
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=878ro4rl4l.fsf@rfc20.org \
    --to=matt@rfc20.org \
    --cc=56870@debbugs.gnu.org \
    --cc=carlmarcos@tutanota.com \
    --cc=larsi@gnus.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).