From: Eli Zaretskii <eliz@gnu.org>
To: Howard Melman <hmelman@gmail.com>
Cc: 55527@debbugs.gnu.org
Subject: bug#55527: 28.1; Clearer abbrev docstrings
Date: Sat, 21 May 2022 21:06:01 +0300 [thread overview]
Message-ID: <83bkvq92wm.fsf@gnu.org> (raw)
In-Reply-To: <96FE2CC0-8A4C-4099-A3D5-5FDD351C739F@gmail.com> (message from Howard Melman on Sat, 21 May 2022 13:49:48 -0400)
> From: Howard Melman <hmelman@gmail.com>
> Date: Sat, 21 May 2022 13:49:48 -0400
> Cc: 55527@debbugs.gnu.org
>
> The existing docstrings for these commands had "word(s)" in them
> and I don't think that's what made them unclear. I also think it's a
> common case to define an abbrev for a multi-word expansion.
I disagree, and let's leave it at that.
> Also, I see now that the inverse- versions of these command treat a
> negative argument as reversing the direction to find the word to use
> as the abbreviation but the (old and new) docstrings fails to mention
> this. I'm not sure if that's intentional or not (IMO it's an odd use case).
This is unrelated. The effect of negative argument was implied; I've
now made it explicit.
Our disagreement aside, are there any other issues left?
next prev parent reply other threads:[~2022-05-21 18:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 18:32 bug#55527: 28.1; Clearer abbrev docstrings Howard Melman
2022-05-19 18:52 ` Eli Zaretskii
2022-05-19 19:30 ` Howard Melman
2022-05-19 19:46 ` Eli Zaretskii
2022-05-19 20:38 ` Howard Melman
2022-05-20 5:48 ` Eli Zaretskii
2022-05-20 13:35 ` Howard Melman
2022-05-20 15:59 ` Eli Zaretskii
2022-05-20 17:03 ` Howard Melman
2022-05-21 7:23 ` Eli Zaretskii
2022-05-21 13:41 ` Howard Melman
2022-05-21 14:09 ` Eli Zaretskii
2022-05-21 17:49 ` Howard Melman
2022-05-21 18:06 ` Eli Zaretskii [this message]
2022-05-21 18:26 ` Howard Melman
2022-05-21 18:46 ` Eli Zaretskii
2022-05-20 7:41 ` Juri Linkov
2022-05-20 13:12 ` Howard Melman
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=83bkvq92wm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55527@debbugs.gnu.org \
--cc=hmelman@gmail.com \
/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).