Subject: Re: bug#32610: Enhancement Request (Flyspell/Ispell): Customizing a NIL value for ispell-async-processp.

From: Keith David Bershatsky <[email-masked]>
Date: Sun, 02 Sep 2018 09:39:03 -0700

Thank you, Eli, for the detailed explanation regarding this issue.

Yes, please go ahead and close out this bug at your convenience.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

> Date: [09-02-2018 08:41:51] <02 Sep 2018 18:41:51 +0300>
> From: Eli Zaretskii <[email-masked]>
> To: Keith David Bershatsky <[email-masked]>
> CC: [email-masked]
> Subject: Re: bug#32610: Enhancement Request (Flyspell/Ispell): Customizing a NIL value for ispell-async-processp.
> 
> > Date: Sat, 01 Sep 2018 17:57:13 -0700
> > From: Keith David Bershatsky <[email-masked]>
> >
> > * * * OBSERVATION:  It appears to me from a review of the code that some initial work has already been done to permit Flyspell and/or Ispell to work with ispell-async-processp having a nil value; however, additional modification of the code is needed.
> 
> I don't expect anyone to work on this, since its only purpose is to
> support a system no one here is interested in.  And in any case, this
> is not what you want.
> 
> I think we should close this bug.