unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Howard Melman <hmelman@gmail.com>
To: 55527@debbugs.gnu.org
Subject: bug#55527: 28.1; Clearer abbrev docstrings
Date: Thu, 19 May 2022 16:38:42 -0400	[thread overview]
Message-ID: <lyczg9jm0d.fsf@new-host-2.home> (raw)
In-Reply-To: <D7770BA8-552C-41C6-AE35-20F809516341@gmail.com>

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Howard Melman <hmelman@gmail.com>
>> Date: Thu, 19 May 2022 15:30:18 -0400
>>
>> > I don't actually understand what's wrong with the original one,
>> > viz.:
>> >
>> >   Define last word before point as a global (mode-independent) abbrev.
>>
>> Because I'm not sure if the word will be used as the abbrev
>> or the expansion.
>
> If you add the expansion part, the line becomes too long, though:
>
>   Define last word before point as expansion of a global (mode-independent) abbrev.

I think you can loose the "mode-independent" part, as global
covers that pretty clearly, how about:

   Define last word before point as expansion of a global abbrev.

>> > I would say
>> >
>> >   Global abbrev that expands into "foo":
>> >   Expansion for a global abbrev "foo":
>>
>> Those would be fine with me.
>>
>> > But I'm not sure we can make these prompts so much longer than the
>> > original ones without overflowing the minibuffer into a second line,
>> > which is a disadvantage.
>>
>> I tend to use very short abbrevs that expand into longer
>> words, so it wouldn't be a problem for me.
>
> The problem in the first prompt is with "foo": it could be arbitrarily
> long.  And in the second prompt you are supposed to type the
> expansion, which again can be long.

Yes but I'm adding about 10 characters to the prompt, so
once you get to "arbitrarily long", 10 characters only
affects so many of them :)

>> >> 	(defun define-abbrev (table abbrev expansion &optional hook &rest props)
>> >> 	  "Define in TABLE an ABBREV and its EXPANSION and optionally a HOOK.
>> >
>> > This loses the explanation of what is HOOK, and is also a very awkward
>> > sentence that I think will be hard on non-native English
>> > speakers.
>>
>> I'm not sure that "call HOOK" is an "explanation".  I
>> already assumed a "hook" would be called and I was confused
>> when it would be called.
>
> It will be called, but by whom and when?

Yes that was *my* point.  The original says:

Define an abbrev in TABLE named NAME, to expand to EXPANSION and call HOOK.

which to me doesn't answer "by whom and when" and I think is
actually less clear than my rewording.  Perhaps better is:

  Define in TABLE an ABBREV and its EXPANSION and optionally its HOOK.

I don't think it's at all obvious how the original clauses
relate to each other (thankfully the full docstring is much
clearer) but as you brought up non-native english speakers I
would think the original is also difficult for them.

-- 

Howard






  reply	other threads:[~2022-05-19 20:38 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 [this message]
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
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=lyczg9jm0d.fsf@new-host-2.home \
    --to=hmelman@gmail.com \
    --cc=55527@debbugs.gnu.org \
    /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).