On Thu, Apr 08, 2010 at 10:46:33AM +0100, Mark Wooding wrote: > Agustin Martin <agustin.mar...@hispalinux.es> writes: > > > I have to think about this more carefully, but using the directory > > where ispell is called as a directory that can contain personal > > dictionaries in parallel with the possible standard personal > > dictionary is usual ispell behavior when no explicit personal > > dictionary is set. > > Ahh, that complicates things rather. > > > A first workaround for that is very simple, also restart ispell > > process everytime local-directory changes. This improves things but > > leaves something pending, killing a buffer should kill the associated > > ispell process if no other buffer is using it. In my tests with the > > first change that is not happening once I open a second buffer and > > kill the first one (where I started an ispell process). Once I start > > an ispell process in the second buffer things work again. > > That would certainly be an improvement. I've just refreshed my memory > on various topics: a really `proper' fix looks rather hard to do.
Seems I was lucky, but still have to test I have been playing with adding a variable that is set to the name of the buffer where the ispell process is launched. I then use kill-buffer-hook to check if buffer to be killed has an associated ispell process and if so kill it too. I still have to test things better, but the concept seems reasonable and my preliminary tests worked well. I have put experimental packages at our alioth staging area, http://dict-common.alioth.debian.org/ Repository there is signed with a dict-common gpg key signed with my Debian gpg key (as are packages there). I hope to test this better during the weekend and if no problem appear will add more pending changes and upload, so we try the real life check. Cheers, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
