From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 24979-done@debbugs.gnu.org
Subject: bug#24979: 24.5; Doc string of `current-word'
Date: Fri, 25 Nov 2016 07:36:27 -0800 (PST) [thread overview]
Message-ID: <759faee5-8fa2-45a1-bee1-df2df096cb75@default> (raw)
In-Reply-To: <<83fumf51k7.fsf@gnu.org>>
> > This part of the doc string is wrong:
> >
> > The function, belying its name, normally finds a symbol.
> >
> >
> > 1. There is no "normally". Do you mean often? Usually?
> > Sometimes? (When?)
>
> "Normally" is GNU and Emacs parlance for "by default", and is
> usually (as in this case) followed by the description of the
> non-default use case. You will find gazillions of this in
> the documentation.
If there are other cases where "normally" is used to convey
"by default" then I hope they get fixed too. If the
surrounding text makes clear, e.g. by explicitly contrasting,
that what is meant by "normally" is the default case, then
it could be OK (but should never be _preferred_ to stating
clearly and explicitly what the default behavior is).
In this case, "normally" might have been able to be understood
the way you say if the last two sentences were in their own
paragraph, so that the last more clearly qualified the
statement of the next-to-last, instead of appearing to stand
on its own.
> I think this is splitting hair, probably because "symbol" is
> ambiguous due to its being a Lisp object. E.g., if the doc
> string said
> Return the word at or near point, as a string.
> you wouldn't object, because "word" is not a Lisp object.
Correct. I wouldn't have objected about calling it a word.
But I would have objected about "near", which is not the
same as on-the-same-line-and-adjacent-to - it is quite
different, in fact.
> Anyway, I modified the doc string to say
>
> "Return the word at or near point, as a string.
Return the word at point or adjacent to it, as a string.
(or a bit less clear:
Return the word at or adjacent to point, as a string.)
See above.
The rest looks good. Thx.
next parent reply other threads:[~2016-11-25 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<d144109b-5a29-4b6c-b984-10a0d7106f94@default>
[not found] ` <<83fumf51k7.fsf@gnu.org>
2016-11-25 15:36 ` Drew Adams [this message]
2016-11-21 18:24 bug#24979: 24.5; Doc string of `current-word' Drew Adams
2016-11-25 9:52 ` 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=759faee5-8fa2-45a1-bee1-df2df096cb75@default \
--to=drew.adams@oracle.com \
--cc=24979-done@debbugs.gnu.org \
--cc=eliz@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).