unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Kevin Ryde <user42@zip.com.au>
Cc: 6221@debbugs.gnu.org
Subject: bug#6221: 23.1; checkdoc-ispell-lisp-words when ispell already running
Date: Wed, 20 Jan 2021 22:15:56 +0100	[thread overview]
Message-ID: <87lfcnl377.fsf@gnus.org> (raw)
In-Reply-To: <87wnw7l4b0.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 20 Jan 2021 21:52:03 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I've now changed this as you suggest in Emacs 28, but after committing
> I'm not 100% sure that this is the correct thing to do, since this means
> that "keymap" etc will now be valid in other buffers you use flyspell
> in, too?  I think?
>
> Should checkdoc kill the ispell process and start a new one?

Indeed.  The comment says:

;;   There is a list of Lisp-specific words which checkdoc will
;; install into Ispell on the fly, but only if Ispell is not already
;; running.  Use `ispell-kill-ispell' to make checkdoc restart it with
;; these words enabled.

So I've reverted the change, and instead added this text to the
checkdoc-spellcheck-documentation-flag doc string.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-01-20 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 23:29 bug#6221: 23.1; checkdoc-ispell-lisp-words when ispell already running Kevin Ryde
2021-01-20 20:52 ` Lars Ingebrigtsen
2021-01-20 21:15   ` Lars Ingebrigtsen [this message]

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=87lfcnl377.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=6221@debbugs.gnu.org \
    --cc=user42@zip.com.au \
    /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).