unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: Quiliro <quiliro@riseup.net>, 26199@debbugs.gnu.org
Subject: bug#26199: claws-mail needs to be built with libenchant support
Date: Fri, 24 Mar 2017 10:48:18 +0100	[thread overview]
Message-ID: <87h92jypi5.fsf@gnu.org> (raw)
In-Reply-To: <20170321190456.GA3855@jasmine> (Leo Famulari's message of "Tue, 21 Mar 2017 15:04:56 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Mon, Mar 20, 2017 at 04:51:24PM -0500, Quiliro wrote:
>> That says that the spell checker could not be started. And that the
>> dictionary none could not be started.
>> 
>> "claws-mail needs to be built with libenchant support"
>> "you can't add it afterwards"
>> That is what Claws-Mail's main developer said.
>> 
>> I guess guix does not build claws-mail with libenchant support by
>> default.
>
> Claws-mail is built with support for libenchant:
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/mail.scm#n928
>
> So, there must be another problem.

It may be the problem I identified there:

  https://bugs.gnu.org/25836

Namely, libaspell (used by libenchant) doesn’t honor $ASPELL_CONF, and
thus thinks it has zero dictionaries available.

I’ve been meaning to email upstream and ask for advice, let’s see.

Ludo’.

      parent reply	other threads:[~2017-03-24  9:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 21:51 bug#26199: claws-mail needs to be built with libenchant support Quiliro
2017-03-21 19:04 ` Leo Famulari
2017-03-21 20:09   ` Catonano
2017-03-22  9:44     ` Quiliro
2017-03-22  9:51       ` Catonano
2017-03-22 10:07         ` Quiliro
2017-03-22 11:57           ` Ricardo Wurmus
2017-03-22 18:06             ` Quiliro
2020-03-22 20:31               ` Leo Famulari
2022-01-05  0:10                 ` zimoun
2017-03-24  9:48   ` Ludovic Courtès [this message]

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=87h92jypi5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26199@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=quiliro@riseup.net \
    /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).