From: Eli Zaretskii <eliz@gnu.org>
To: "Laimonas Vėbra" <laimonas.vebra@yahoo.com>
Cc: 24439@debbugs.gnu.org
Subject: bug#24439: ispell.el; cutom setting `ispell-library-directory'; patch
Date: Thu, 15 Sep 2016 20:20:46 +0300 [thread overview]
Message-ID: <83y42t5bbl.fsf@gnu.org> (raw)
In-Reply-To: <57DAD199.2010102@yahoo.com> (message from Laimonas Vėbra on Thu, 15 Sep 2016 19:51:37 +0300)
> Cc: 24439@debbugs.gnu.org
> From: Laimonas Vėbra <laimonas.vebra@yahoo.com>
> Date: Thu, 15 Sep 2016 19:51:37 +0300
>
> Eli Zaretskii wrote:
>
> > What I meant specifically is to use the -d switch to tell ispell where
> > to look for the dictionaries. The -d switch accepts absolute file
> > names, AFAIR, and will not try to look in ispell-library-directory for
> > such absolute file names.
>
> -d doesn't work, because of this code:
>
> ;; Include if the dictionary is in the library, or dir not defined.
> (if (and
> name
> ;; For Aspell, we already know which dictionaries exist.
> (or ispell-really-aspell
> ;; Include all dictionaries if lib directory not known.
> ;; Same for Hunspell, where ispell-library-directory is nil.
> (not ispell-library-directory)
> (file-exists-p (concat ispell-library-directory
> "/" dict-bname ".hash"))
> (file-exists-p (concat ispell-library-directory
> "/" dict-bname ".has"))))
> (push name dict-list)))
>
>
> > If that doesn't help, then maybe I don't understand what problem,
> > exactly, are you trying to solve. What bad things happen if you don't
> > change the value of ispell-library-directory from its default?
>
> Then it's not possible to add custom dictionaries (when using cygwin
> ispell) or dictionaries from other directory, than
> `ispell-library-directory', because they are ommited by
> `ispell-valid-dictionary-alist'.
>
> > Even if the dictionaries that are arguments of the -d switch are given
> > as absolute file names? If so, maybe that's the problem that needs
> > fixing.
>
> Yes.
OK, so adding a condition for dict-bname being an absolute file name
in the above snippet would solve your problem?
next prev parent reply other threads:[~2016-09-15 17:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 20:02 bug#24439: ispell.el; cutom setting `ispell-library-directory'; patch Laimonas Vėbra
2016-09-15 15:07 ` Eli Zaretskii
2016-09-15 15:56 ` Laimonas Vėbra
2016-09-15 16:34 ` Eli Zaretskii
2016-09-15 16:51 ` Laimonas Vėbra
2016-09-15 17:20 ` Eli Zaretskii [this message]
2016-09-15 17:53 ` Laimonas Vėbra
2016-09-15 18:48 ` Eli Zaretskii
2016-09-15 20:10 ` Laimonas Vėbra
2016-09-15 20:57 ` Ken Brown
2016-09-15 21:20 ` Laimonas Vėbra
2016-09-15 22:17 ` Ken Brown
2016-09-15 23:00 ` Laimonas Vėbra
2016-09-16 6:46 ` Eli Zaretskii
2016-09-16 6:25 ` Eli Zaretskii
2016-09-16 1:35 ` Laimonas Vėbra
2016-09-16 6:44 ` Eli Zaretskii
2016-09-24 17:47 ` Laimonas Vėbra
2016-10-06 10:33 ` Laimonas Vėbra
2016-10-07 8:58 ` Eli Zaretskii
2016-10-08 11:30 ` Agustin Martin
2016-10-08 12:18 ` 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=83y42t5bbl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24439@debbugs.gnu.org \
--cc=laimonas.vebra@yahoo.com \
/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).