unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#7272: 24.0.50; Enabling Flyspell mode gave an error
@ 2010-10-23 20:21 jidanni
  2010-10-23 21:13 ` Eli Zaretskii
                   ` (2 more replies)
  0 siblings, 3 replies; 8+ messages in thread
From: jidanni @ 2010-10-23 20:21 UTC (permalink / raw)
  To: 7272; +Cc: rfrancoise

$ emacs -Q /etc/motd -nw -f flyspell-mode
Enabling Flyspell mode gave an error

In GNU Emacs 24.0.50.1 (i486-pc-linux-gnu, GTK+ Version 2.20.1)
 of 2010-10-16 on elegiac, modified by Debian
 (emacs-snapshot package, version 1:20101016-1)





^ permalink raw reply	[flat|nested] 8+ messages in thread

* bug#7272: 24.0.50; Enabling Flyspell mode gave an error
  2010-10-23 20:21 bug#7272: 24.0.50; Enabling Flyspell mode gave an error jidanni
@ 2010-10-23 21:13 ` Eli Zaretskii
  2010-10-24  2:23 ` jidanni
  2010-10-26 12:03 ` jidanni
  2 siblings, 0 replies; 8+ messages in thread
From: Eli Zaretskii @ 2010-10-23 21:13 UTC (permalink / raw)
  To: jidanni; +Cc: 7272, rfrancoise

> From: jidanni@jidanni.org
> Date: Sun, 24 Oct 2010 04:21:47 +0800
> Cc: rfrancoise@debian.org
> 
> $ emacs -Q /etc/motd -nw -f flyspell-mode
> Enabling Flyspell mode gave an error

How about showing that error message?  (No, I don't see any errors
with today's bzr.)





^ permalink raw reply	[flat|nested] 8+ messages in thread

* bug#7272: 24.0.50; Enabling Flyspell mode gave an error
  2010-10-23 20:21 bug#7272: 24.0.50; Enabling Flyspell mode gave an error jidanni
  2010-10-23 21:13 ` Eli Zaretskii
@ 2010-10-24  2:23 ` jidanni
  2010-10-26 10:46   ` Agustin Martin
  2010-10-26 12:03 ` jidanni
  2 siblings, 1 reply; 8+ messages in thread
From: jidanni @ 2010-10-24  2:23 UTC (permalink / raw)
  To: eliz; +Cc: 7272, rfrancoise

>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>> From: jidanni@jidanni.org
>> Date: Sun, 24 Oct 2010 04:21:47 +0800
>> Cc: rfrancoise@debian.org
>> 
>> $ emacs -Q /etc/motd -nw -f flyspell-mode
>> Enabling Flyspell mode gave an error

EZ> How about showing that error message?  (No, I don't see any errors
EZ> with today's bzr.)

One can see it in the minibuffer and with view-echo-area-messages C-h e:
("emacs" "/etc/motd" "-f" "flyspell-mode")
For information about GNU Emacs and the GNU system, type C-h C-a.
Note: file is write protected
Starting new Ispell process [default] ...
Enabling Flyspell mode gave an error

Maybe a Debian guy can confirm it.





^ permalink raw reply	[flat|nested] 8+ messages in thread

* bug#7272: 24.0.50; Enabling Flyspell mode gave an error
  2010-10-24  2:23 ` jidanni
@ 2010-10-26 10:46   ` Agustin Martin
  0 siblings, 0 replies; 8+ messages in thread
From: Agustin Martin @ 2010-10-26 10:46 UTC (permalink / raw)
  To: jidanni, 7272

On Sun, Oct 24, 2010 at 10:23:38AM +0800, jidanni@jidanni.org wrote:
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> >> From: jidanni@jidanni.org
> >> Date: Sun, 24 Oct 2010 04:21:47 +0800
> >> Cc: rfrancoise@debian.org
> >> 
> >> $ emacs -Q /etc/motd -nw -f flyspell-mode
> >> Enabling Flyspell mode gave an error
> 
> EZ> How about showing that error message?  (No, I don't see any errors
> EZ> with today's bzr.)
> 
> One can see it in the minibuffer and with view-echo-area-messages C-h e:
> ("emacs" "/etc/motd" "-f" "flyspell-mode")
> For information about GNU Emacs and the GNU system, type C-h C-a.
> Note: file is write protected
> Starting new Ispell process [default] ...
> Enabling Flyspell mode gave an error

Cannot reproduce that here,

$ emacs -Q /etc/motd -nw -f flyspell-mode
("emacs" "/etc/motd" "-f" "flyspell-mode")
For information about GNU Emacs and the GNU system, type C-h C-a.
Note: file is write protected
Starting new Ispell process [default] ...

No errors. Same with the X variant,

$ emacs -Q /etc/motd -f flyspell-mode

Glenn Morris has committed a change to make flyspell show what is the error
when flyspell.el finds an error. That should already be included in last
emacs-snapshot Debian package prepared by Romain Francoise (emacs-snapshot
1:20101024-1). Can you try with that newer emacs-snapshot, so we have more 
info about the problem?

> Maybe a Debian guy can confirm it.

Note that Debian emacs-snapshot package uses pristine spellchecking files 
from FSF Emacs bzr repo, no Debian specific changes are applied.

Thanks for your feedback,

-- 
Agustin





^ permalink raw reply	[flat|nested] 8+ messages in thread

* bug#7272: 24.0.50; Enabling Flyspell mode gave an error
  2010-10-23 20:21 bug#7272: 24.0.50; Enabling Flyspell mode gave an error jidanni
  2010-10-23 21:13 ` Eli Zaretskii
  2010-10-24  2:23 ` jidanni
@ 2010-10-26 12:03 ` jidanni
  2010-10-26 13:45   ` Agustin Martin
  2 siblings, 1 reply; 8+ messages in thread
From: jidanni @ 2010-10-26 12:03 UTC (permalink / raw)
  To: agustin.martin; +Cc: 7272

>>>>> "AM" == Agustin Martin <agustin.martin@hispalinux.es> writes:
AM> 1:20101024-1). Can you try with that newer emacs-snapshot, so we have more 
AM> info about the problem?
Bingo,
Error enabling Flyspell mode:
(Error: No word lists can be found for the language "zh_TW".)
So at least we now know what is going on.
However, how might I suppress this message without changing my ENV
variables or touch(1)ing empty files etc.?





^ permalink raw reply	[flat|nested] 8+ messages in thread

* bug#7272: 24.0.50; Enabling Flyspell mode gave an error
  2010-10-26 12:03 ` jidanni
@ 2010-10-26 13:45   ` Agustin Martin
  2010-10-27  4:41     ` jidanni
  0 siblings, 1 reply; 8+ messages in thread
From: Agustin Martin @ 2010-10-26 13:45 UTC (permalink / raw)
  To: jidanni, 7272

On Tue, Oct 26, 2010 at 08:03:19PM +0800, jidanni@jidanni.org wrote:
> >>>>> "AM" == Agustin Martin <agustin.martin@hispalinux.es> writes:
> AM> 1:20101024-1). Can you try with that newer emacs-snapshot, so we have more 
> AM> info about the problem?
> Bingo,
> Error enabling Flyspell mode:
> (Error: No word lists can be found for the language "zh_TW".)
> So at least we now know what is going on.
> However, how might I suppress this message without changing my ENV
> variables or touch(1)ing empty files etc.?

I guess you are using aspell (emacs-snapshot defaults to aspell if 
present), your LANG envar points to zh_TW, and there is no zh_TW aspell
dictionary present. Note that, unless an explicit dict is given, aspell 
will try to get its default dictionary after variables LANG or 
LC_MESSAGES. 

If so, the error you get is exactly what is expected, you tell flyspell 
to start spellchecking and since no specific dictionary is selected it 
tries to use one after LANG variable. Since the dict is not found 
aspell fails and flyspell catches the error.

Error should be similar when you just try spellchecking a test file
in the same ENV without an explicit dict option,

$ aspell check test.txt

If you want to avoid that error for emacs without touching your .emacs 
file (that  is, avoiding the error even when using the -Q option) or
for all aspell uses, you need to explicitly tell aspell about your 
desired dict, either in your aspell personal configuration file 
(~/.aspell.conf) or in the global one if you want to set that for all 
users.

An entry in aspell configuration file with something like

lang de_CH

pointing to your desired language should do the work. See 'man aspell' for
details.

I am probably guessing too much, but there is a good chance that this is
indeed the problem. If so, please close this bug report.

Hope this helps,

-- 
Agustin





^ permalink raw reply	[flat|nested] 8+ messages in thread

* bug#7272: 24.0.50; Enabling Flyspell mode gave an error
  2010-10-26 13:45   ` Agustin Martin
@ 2010-10-27  4:41     ` jidanni
  2010-10-27 10:01       ` Agustin Martin
  0 siblings, 1 reply; 8+ messages in thread
From: jidanni @ 2010-10-27  4:41 UTC (permalink / raw)
  To: Agustin Martin; +Cc: 7272-done

On Tue, Oct 26, 2010 at 03:45:59PM +0200, Agustin Martin wrote:
> An entry in aspell configuration file with something like
> 
> lang de_CH
> 
> pointing to your desired language should do the work. See 'man aspell' for
> details.
I was just wondering if there was a way to say that in .emacs, so I don't have to maintain a second file.





^ permalink raw reply	[flat|nested] 8+ messages in thread

* bug#7272: 24.0.50; Enabling Flyspell mode gave an error
  2010-10-27  4:41     ` jidanni
@ 2010-10-27 10:01       ` Agustin Martin
  0 siblings, 0 replies; 8+ messages in thread
From: Agustin Martin @ 2010-10-27 10:01 UTC (permalink / raw)
  To: jidanni, 7272

On Wed, Oct 27, 2010 at 12:41:25PM +0800, jidanni@jidanni.org wrote:
> On Tue, Oct 26, 2010 at 03:45:59PM +0200, Agustin Martin wrote:
> > An entry in aspell configuration file with something like
> > 
> > lang de_CH
> > 
> > pointing to your desired language should do the work. See 'man aspell' for
> > details.
> I was just wondering if there was a way to say that in .emacs, so I don't have to maintain a second file.

Not it you call emacs with -Q option, which will make ~/.emacs be 
ignored. If init file is read (no -Q or -q), just setting 
`ispell-dictionary' variable in ~/.emacs to an available dictionary 
should work.

IIRC you have a valid default dict entry in your .emacs file, so this
problem should not appear in normal use. If it appeared, it is a 
problem.

Was this error already present before you tried with 

  $ emacs -Q /etc/motd -f flyspell-mode

for the bug report?

-- 
Agustin






^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2010-10-27 10:01 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-23 20:21 bug#7272: 24.0.50; Enabling Flyspell mode gave an error jidanni
2010-10-23 21:13 ` Eli Zaretskii
2010-10-24  2:23 ` jidanni
2010-10-26 10:46   ` Agustin Martin
2010-10-26 12:03 ` jidanni
2010-10-26 13:45   ` Agustin Martin
2010-10-27  4:41     ` jidanni
2010-10-27 10:01       ` Agustin Martin

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).