From: Agustin Martin <agustin.martin@hispalinux.es>
To: 6143@debbugs.gnu.org
Cc: jidanni@jidanni.org
Subject: bug#6143: 6143 ispell not fixed
Date: Thu, 29 Jul 2010 13:41:21 +0200 [thread overview]
Message-ID: <AANLkTikm9O=EMKsr0uDKWNvQNtuPfmJABSqEwQW-7KRO@mail.gmail.com> (raw)
In-Reply-To: <yxqsk34vj8q.fsf@fencepost.gnu.org>
2010/7/27 Dan Nicolaescu <dann@gnu.org>:
> Agustin Martin <agustin.martin@hispalinux.es> writes:
>
>> On Sat, Jul 24, 2010 at 01:35:06AM -0400, Dan Nicolaescu wrote:
>>>
>>> You can get the "Ispell process killed" message by doing:
>>>
>>> $ echo $LANG
>>> C
>>> $ emacs -Q
>>> M-: (add-hook 'text-mode-hook 'flyspell-mode) RET
>>>
>>> C-x C-f A_FILE_UNDER_VERSION_CONTROL_FOR_EXAMPLE_MANAGED_BY_GIT
>>> type something
>>> C-x v v
>>> type something in the log-edit buffer.
>>> C-c C-c
>>>
>>> now look at the *Messages* buffer and see the "Ispell process killed"
>>
>> Strange, I get a different result (although also with an error),
>>
>> $ LANG=C LC_ALL=C emacs-snapshot -Q &
>> M-: (add-hook 'text-mode-hook 'flyspell-mode) RET
>> C-x C-f A_FILE_UNDER_GIT_VERSION_CONTROL (kkk.txt)
>> type something
>> C-x v v
>> type something in the log-edit buffer.
>>
>> Error during redisplay: (error No match 4 in highlight (4 font-lock-warning-face))
>>
>> C-c C-c
>>
>> Buffer kkk.txt modified; save it? (y or n)
>> Error during redisplay: (error No match 4 in highlight (4 font-lock-warning-face))
>>
>> But no ispell process restart.
>
> When I ispell-kill-ispell is invoked the backtrace looks like this:
>
> ispell-kill-ispell(t)
> (if (equal ispell-process-buffer-name (buffer-name)) (ispell-kill-ispell t))
> (lambda nil (if (equal ispell-process-buffer-name ...) (ispell-kill-ispell t)))()
> kill-buffer(#<buffer *VC-log*>)
> vc-finish-logentry()
> call-interactively(vc-finish-logentry)
> log-edit-done()
> call-interactively(log-edit-done nil nil)
>
>
> So this is caused by:
>
> (add-hook 'kill-buffer-hook
> '(lambda ()
> (if (equal ispell-process-buffer-name (buffer-name))
> (ispell-kill-ispell t))))
>
>
> ispell-process-buffer-name is "*VC-log*"
Thanks for debugging, Dan
I guess your original A_FILE_UNDER_GIT_VERSION_CONTROL file is not a
text-mode file. If so, this is the currently expected behavior, do not
leave unused ispell processes behind. So, no ispell process is
started for initial file, and only when you start the text mode buffer
"*VC-log*", an ispell process is started. Since there was no previous
process "owned" by a previous buffer, this is killed on buffer kill.
Note that I was playing with a text file, so an ispell process is
started for it and, since it does not contain neither localwords nor
an explicit language different from default, same process is used for
"*VC-log*" buffer and is not killed on "*VC-log*" kill since it was
initiated from original buffer. That is the difference I find. What
happened before for me is that I probably did not use the file as
kkk.txt, but as plain kkk.
This being too noisy or not is open for discussion, others may argue
that leaving unused ispell processes behind is also a bug. I
personally do not find this noisy enough. Opinions welcome.
If this is considered too noisy and leaving unused ispell processes
behind not a problem I think the way to go is to always use "~/" as
ispell process directory, so problem with removable media that used
the kill-on-kill gets also fixed. Better if there is a not too
complicated way of having an exception when Ispell is the
spellchecking engine and original directory contains an Ispell
directory dictionary for given language. This way if using Ispell,
current directory is used as ispell-default-directory only if contains
appropriate directory personal dictionary and process is killed on
buffer kill only if so (IIRC someone already proposed this, but I do
not find original mail). Otherwise we lose support for this Ispell
funcionality. Have to think a bit about this.
PS: I have been lately with limited time and connectivity. Do not
expect something quickly.
--
Agustin
next prev parent reply other threads:[~2010-07-29 11:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <handler.6143.D6143.127374871827801.notifdone@debbugs.gnu.org>
2010-05-09 1:21 ` [emacs-w3m:11218] 24.0.50; don't ispell-kill-ispell over and over jidanni
2010-05-11 13:20 ` bug#6143: " Agustin Martin
2010-05-11 14:40 ` Stefan Monnier
2010-05-11 15:18 ` Agustin Martin
2010-05-12 10:26 ` Agustin Martin
2010-05-12 13:30 ` Lennart Borgman
2010-05-12 14:35 ` Agustin Martin
2010-05-12 14:28 ` Stefan Monnier
2010-05-13 11:05 ` Agustin Martin
2010-05-28 13:45 ` bug#6143: closed (Re: bug#6143: 24.0.50; don't ispell-kill-ispell over and over) jidanni
2010-06-20 4:47 ` bug#6143: ispell killing still not fixed jidanni
2010-06-21 12:10 ` Agustin Martin
2010-06-23 2:19 ` jidanni
2010-06-24 11:35 ` Agustin Martin
2010-06-24 14:43 ` jidanni
2010-06-24 15:23 ` Agustin Martin
2010-06-24 15:51 ` Agustin Martin
2010-06-24 16:16 ` Agustin Martin
2010-06-24 23:52 ` jidanni
2010-06-25 8:30 ` Agustin Martin
2010-07-10 2:30 ` bug#6143: totally " agustin.martin
2010-07-22 19:11 ` bug#6143: 6143 ispell " jidanni
2010-07-23 11:18 ` Agustin Martin
2010-07-24 5:35 ` Dan Nicolaescu
2010-07-26 9:38 ` Agustin Martin
2010-07-26 9:59 ` Agustin Martin
2010-07-26 10:25 ` Agustin Martin
2010-07-27 12:03 ` Agustin Martin
2010-07-27 18:16 ` Dan Nicolaescu
2010-07-27 19:04 ` Dan Nicolaescu
2010-07-29 11:41 ` Agustin Martin [this message]
2010-07-29 13:07 ` Stefan Monnier
2010-09-02 12:47 ` Agustin Martin
2010-09-02 13:03 ` jidanni
2010-10-26 10:20 ` bug#6143: ispell killing still " Agustin Martin
2010-09-02 16:01 ` bug#6143: 6143 ispell " Stefan Monnier
2010-09-03 10:19 ` Agustin Martin
2010-07-23 19:30 ` jidanni
2010-07-26 3:54 ` jidanni
2010-07-26 14:21 ` jidanni
2010-07-27 17:35 ` jidanni
2010-07-29 20:42 ` jidanni
2010-08-13 14:20 ` jidanni
2010-10-26 12:07 ` bug#6143: ispell killing still " jidanni
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikm9O=EMKsr0uDKWNvQNtuPfmJABSqEwQW-7KRO@mail.gmail.com' \
--to=agustin.martin@hispalinux.es \
--cc=6143@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.