Re: [newbie] emacs flyspell not understands well accented chars

[Mario Giammarco]

Oliver Scholz wrote:

> Mario Giammarco <mgiammarco@nospam.supereva.it> writes:
> 
>> Oliver Scholz wrote:
>>
>>
>>>> I obtain at the start of emacs this error: Symbol value as variable is
>>>> void
>>> 
>>> This error message is about the symbol
>>> `ispell-local-dictionary-alist', I presume?
>>> 
>>> Very, very strange, it seems to be preloaded on my Emacs. Does it
>>> work, if you put a
>>> 
>>> (require 'ispell)
>>> 
>>> immediately before the `(add-to-list ... )'?
>>> 
>>
>> I have put (require 'ispell) as you said but the error persists, this is
>> the backtrace:
>>
>> Debugger entered--Lisp error: (void-variable               )
>>   (add-to-list (quote ispell-local-dictionary-alist)               
>>   (quote
> [...]
> 
> Huh? This looks very, very wrong. Did you modify this backtrace
> somehow?

NO, cut and paste


> ... alright let's go about this methodically:
> 
> 1) Please remove the `add-to-list' expression from your .emacs and
>    start it as usual. Then type `M-x locate-library RET ispell RET'
>    and post what you see in the echo area (messages are collected in a
>    special buffer *Messages*, you can copy&paste the line from there).
> 
>    One possible reason why you Emacs behaves in a different way than
>    mine could be that you have a second ispell.el library in your
>    load-path which shadows the ispell.el that comes with Emacs. If
>    that's the case, we'll find it out with `M-x locate-library'.
> 

I have done it and it seems that it is in the right place where debian puts
it.
This evening I will do a apt-get --purge remove emacs bla bla and reinstall
it
> 
> 2) Please start Emacs from a command line like this:
> 
>    emacs -q --no-site-file
> 
>    This makes sure that Emacs does not load your configuration file,
>    which makes sure that there is no other, unrelated problem that
>    could interfere here.
> 
>    Then insert the `(add-to-list ... )' expression into the buffer
>    named *scratch*. Move the cursor behind the last parenthesis and
>    type `C-x C-e'. Do you get a similar error? If so, please post the
>    whole backtrace (per copy&past) 

I HAVE NOT MODIFIED ANYTHING, SIMPLE COPY AND PASTE!


Debugger entered--Lisp error: (void-variable              )
  (add-to-list (quote ispell-local-dictionary-alist)               (quote
("italianx" "[[:alpha:]]" "[^[:alpha:]]" "[']"  t ... "~latin1"
 iso-8859-15)))
  eval((add-to-list (quote ispell-local-dictionary-alist)              
(quote ("italianx" "[[:alpha:]]" "[^[:alpha:]]" "[']"  t ... "~latin1"
 iso-8859-15))))
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp)


>    `ispell-local-dictionary-alist' with `ispell-dictionary-alist':
> 
> (add-to-list 'ispell-dictionary-alist
> '("italianx"
> "[[:alpha:]]"
> "[^[:alpha:]]"
> "[']" t
> ("-C" "-d" "italian")
> "~latin1" iso-8859-15))
> 
>    Again, put point behind the last parenthesis and hit `C-x C-e'. Do
>    you get an error then, too?

Debugger entered--Lisp error: (void-variable              )
  (add-to-list (quote ispell-dictionary-alist)               (quote
("italianx" "[[:alpha:]]" "[^[:alpha:]]" "[']"  t ... "~latin1"
 iso-8859-15)))
  eval((add-to-list (quote ispell-dictionary-alist)               (quote
("italianx" "[[:alpha:]]" "[^[:alpha:]]" "[']"  t ... "~latin1"
 iso-8859-15))))
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp)
  recursive-edit()
  byte-code("Æ !ˆÇ ˆÈ   !ˆ\nƒ?

HERE CUT AND PASTE DOES NOT WORK CAUSE COMPILED LISP

> 
>>> Aah, I suspected something like that.
>>> 
>>> This expression is wrong. It doesn't give an error, of course, but in
>>> fact it does absolutely nothing.
>>> 
>> Sigh I newer will be a lisp programmer :-(
> 
> If everything is alright, you normally shouldn't have to expose
> yourself to Lisp in order to use Emacs. Unfortunately sometimes things
> go wrong as in your case.
> 
> Personally I found Lisp very easy as my first programming language. I
> think, if you already know other programming languages, you could
> have slightly more problems with it, because it is so very different,
> constituting a whole family of its own.
> 

Thanks for the lisp mini tutorial!
But anyway I would like to know also emacs-lisp "api" to make my own
beautiful macros...

Because a programmer must know how to program is editor...
Perhaps one day I will have time to learn!