From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: master 95e8c7d 1/2: ; Fix typos
Date: Fri, 09 Oct 2020 17:40:15 +0300 [thread overview]
Message-ID: <83tuv35upc.fsf@gnu.org> (raw)
In-Reply-To: <m2362n5wog.fsf@gmail.com> (message from Robert Pluim on Fri, 09 Oct 2020 15:57:35 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Fri, 09 Oct 2020 15:57:35 +0200
> Cc: Stefan Kangas <stefan@marxist.se>
>
> >>>>> On Fri, 9 Oct 2020 09:42:51 -0400 (EDT), stefankangas@gmail.com (Stefan Kangas) said:
>
> Stefan> (defmacro semantic-parse-tree-unparseable ()
> Stefan> - "Indicate that the current buffer is unparseable.
> Stefan> + "Indicate that the current buffer is unparsable.
> Stefan> It is also true that the parse tree will need either updating or
> Stefan> a rebuild. This state will be changed when the user edits the buffer."
> Stefan> '(setq semantic-parse-tree-state 'unparseable))
>
> Stefan> (defmacro semantic-parse-tree-unparseable-p ()
> Stefan> - "Return non-nil if the current buffer has been marked unparseable."
> Stefan> + "Return non-nil if the current buffer has been marked unparsable."
> Stefan> '(eq semantic-parse-tree-state 'unparseable))
>
> The highly accurate method of googling both and comparing the counts
> is not in favour of this change. The principle of making the
> documentation and the code align is *definitely* not in favour of this
> change.
See also
https://en.wiktionary.org/wiki/parsable
next prev parent reply other threads:[~2020-10-09 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201009134249.15265.31644@vcs0.savannah.gnu.org>
[not found] ` <20201009134252.81B3620A15@vcs0.savannah.gnu.org>
2020-10-09 13:57 ` master 95e8c7d 1/2: ; Fix typos Robert Pluim
2020-10-09 14:40 ` Eli Zaretskii [this message]
2020-10-09 21:01 ` Stefan Kangas
2020-10-09 21:14 ` Drew Adams
2020-10-10 6:56 ` Eli Zaretskii
2020-10-10 8:14 ` Stefan Kangas
2020-10-12 8:19 ` Robert Pluim
2020-10-12 14:58 ` Eli Zaretskii
2020-10-16 9:58 ` Stefan Kangas
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=83tuv35upc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
--cc=stefan@marxist.se \
/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.