[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#6143: 24.0.50; don't ispell-kill-ispell over and over

From: Agustin Martin
Subject: bug#6143: 24.0.50; don't ispell-kill-ispell over and over
Date: Tue, 11 May 2010 15:20:08 +0200
User-agent: Mutt/1.5.20 (2009-06-14)

On Sun, May 09, 2010 at 09:21:45AM +0800, address@hidden wrote:
> Every time I even do a
>   S runs the command w3m-search, which is an interactive compiled Lisp
>   function in `w3m-search.el'.
> I see a
>   Starting new Ispell process [american] ...
> Looking in *Messages*
>   Note: file is write protected
>   Ispell process killed
>   Starting new Ispell process [american] ...
>   Mark set
>   Mark saved where search started [5 times]
>   Ispell process killed
>   Starting new Ispell process [american] ...
>   Ispell process killed
>   Making completion list...
>   Scanning for dabbrevs...100%
>   Starting new Ispell process [american] ...

The part of your dotfiles that triggers this is in .emacs-w3m

 (lambda ()
   (if(string-match "TEXT: \\| search: " (minibuffer-prompt))
       (flyspell-mode 1))))

and is related to my changes in bzr:#100056 killing ispell if buffer where
ispell process was generated is killed. (partially related to bzr:#100055)

The reason for that changes is that when emacs visits a file in a removable 
device and an ispell process is launched in that file, ispell process sets 
the dir in the removable device as default dir, so if one switch to other 
buffer outside the removable device and original buffer is killed, unless 
ispell process is restarted (personal dictionary, localwords, different 
language) or just killed, removable device stays bound and cannot be 

This is the reason for ispell process being killed when buffer where it was 
created is killed. Since you create a buffer (the minibuffer) and a new
ispell process for it, this is the behavior you get. Note that this will
not happen if in the main buffer you already have an ispell process started 
for the same language you will use in the minibuffer.

Will think about it, but I do not see an easy workaround to take care of
both things reliably.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]