unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Anders Johansson <mejlaandersj@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 31341@debbugs.gnu.org
Subject: bug#31341: 26.1; setting ispell-base-dicts-override-alist no longer working
Date: Wed, 02 May 2018 21:20:02 +0200	[thread overview]
Message-ID: <87a7th9865.fsf@gmail.com> (raw)
In-Reply-To: <flbmdydmyl.fsf@fencepost.gnu.org>


A recipe for testing. Putting the following code in a file 
ispell-test.el and running ‘emacs -Q l ispell-test.el‘ gives a 
positive result for ispell.el byte-compiled without 
lexical-binding and negative result with lexical binding.
It also works to just add (defvar 
ispell-base-dicts-override-alist) in ispell.el.

--------------------
(load-library "ispell")

(add-hook 'ispell-initialize-spellchecker-hook 
#'ispell-extra-dicts-test)

(defun ispell-extra-dicts-test ()
  (setq ispell-base-dicts-override-alist
        '(("en_GB,sv_SE"
           "[[:alpha:]]" "[^[:alpha:]]"
           "[’'´.0-b:-]" t ("-d" "en_GB,sv_SE")
           nil utf-8))))

(ispell-set-spellchecker-params)

(if (assoc "en_GB,sv_SE" ispell-dictionary-alist)
    (message "It worked!")
  (message "it didn’t work"))

--------------------


On Wednesday  2 May 2018 at 18:46, Glenn Morris <rgm@gnu.org> 
wrote:

> Glenn Morris wrote:
>
>> Eli Zaretskii wrote:
>>
>>> Does recompiling ispell.el without lexical-binding solve this 
>>> problem?
>>
>> I think using
>>
>> (defvar ispell-base-dicts-override-alist nil)
>>
>> (to mark the var as dynamic) would be better.
>
> Or rather just
>
> (defvar ispell-base-dicts-override-alist)


-- 
Anders Johansson





  reply	other threads:[~2018-05-02 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 15:05 bug#31341: 26.1; setting ispell-base-dicts-override-alist no longer working Anders Johansson
2018-05-02 15:25 ` Eli Zaretskii
2018-05-02 16:39   ` Glenn Morris
2018-05-02 16:46     ` Glenn Morris
2018-05-02 19:20       ` Anders Johansson [this message]
2018-05-04 14:27         ` Eli Zaretskii
2018-05-02 17:19     ` 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=87a7th9865.fsf@gmail.com \
    --to=mejlaandersj@gmail.com \
    --cc=31341@debbugs.gnu.org \
    --cc=rgm@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).