unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 19:34:05 +0300	[thread overview]
Message-ID: <831t0l6s1u.fsf@gnu.org> (raw)
In-Reply-To: <57DAC4B6.9040204@yahoo.com> (message from Laimonas Vėbra on Thu, 15 Sep 2016 18:56:38 +0300)

> Cc: 24439@debbugs.gnu.org
> From: Laimonas Vėbra <laimonas.vebra@yahoo.com>
> Date: Thu, 15 Sep 2016 18:56:38 +0300
> 
> > ispell-library-directory is not supposed to be customized by users,
> > it's an internal variable set and used by ispell.el.  To change the
> > location of dictionaries, users are supposed to customize
> > ispell-local-dictionary-alist.  Why can't you do that instead?
> 
> I do understand, that it's internal variable, though it it useful (and i 
> would say crucial) for customization. How am i suppose to customize
> `ispell-local-dictionary-alist'?

It's a defcustom, so using Customize is the preferred way.  Of course,
you can also set it from Lisp.

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.

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?

> AFAICS dictionaries, that are added 
> there, are not visible to `ispell-change-dictionary', because 
> `ispell-library-directory' points to a wrong directory

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.





  reply	other threads:[~2016-09-15 16:34 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 [this message]
2016-09-15 16:51       ` Laimonas Vėbra
2016-09-15 17:20         ` Eli Zaretskii
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=831t0l6s1u.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).