From: ludo@gnu.org (Ludovic Courtès)
To: Kevin Atkinson <kevina@gnu.org>
Cc: 25836@debbugs.gnu.org, aspell-devel@gnu.org
Subject: bug#25836: [aspell-devel] Honoring ‘ASPELL_CONF’ in libaspell
Date: Mon, 27 Mar 2017 10:26:53 +0200 [thread overview]
Message-ID: <87shlznn02.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1703261253200.2667@intel.home> (Kevin Atkinson's message of "Sun, 26 Mar 2017 12:57:48 -0400 (EDT)")
Hi Kevin,
From your reply it seems the second part of my message got lost; you can
see it at <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25836#14>.
Kevin Atkinson <kevina@gnu.org> skribis:
> It would be better to change the compiled in defaults. I believe
> the --enable-dict-dir configure option should change the default for dict-dir.
The problem is that dict-dir is typically
“$HOME/.guix-profile/lib/aspell”, so we can’t choose it at configure
time (unless Aspell expands “$HOME”?).
Even if we did, we’d like to offer users the ability to choose
dictionaries located in a different place.
How would you achieve that?
Thanks for your reply,
Ludo’.
next parent reply other threads:[~2017-03-27 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ98PDyRmcJEZTC6dOuuwXeH+j6ZtwYnMmtmD-0bj9N9yWfZMg@mail.gmail.com>
[not found] ` <87wpbx9z7b.fsf@gnu.org>
[not found] ` <87vaqwp2l8.fsf_-_@gnu.org>
[not found] ` <alpine.DEB.2.11.1703261253200.2667@intel.home>
2017-03-27 8:26 ` Ludovic Courtès [this message]
2017-05-03 16:49 ` bug#25836: [aspell-devel] Honoring ‘ASPELL_CONF’ in libaspell Catonano
2017-05-03 18:14 ` Kevin Atkinson
2017-05-17 14:21 ` Ludovic Courtès
2017-05-17 18:14 ` Kevin Atkinson
2017-03-30 11:57 ` bug#25836: [PATCH] gnu: Add gspell Thomas Danckaert
2017-03-30 12:08 ` Catonano
2017-05-17 14:24 ` Ludovic Courtès
2017-05-17 15:16 ` Thomas Danckaert
2017-05-17 19:56 ` Ludovic Courtès
2017-05-17 17:22 ` Catonano
2017-05-17 17:24 ` Catonano
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shlznn02.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25836@debbugs.gnu.org \
--cc=aspell-devel@gnu.org \
--cc=kevina@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/guix.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).