From: Agustin Martin <agustin.martin@hispalinux.es>
To: 6143@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#6143: 24.0.50; don't ispell-kill-ispell over and over
Date: Wed, 12 May 2010 12:26:07 +0200 [thread overview]
Message-ID: <20100512102606.GA12529@agmartin.aq.upm.es> (raw)
In-Reply-To: <20100511151826.GA13569@agmartin.aq.upm.es>
On Tue, May 11, 2010 at 05:18:26PM +0200, Agustin Martin wrote:
> I am still trying to think about something cleaner, or at least about a
> reasonable workaround.
I have been thinking about this, and about a fix that is XEmacs compatible.
Although current ispell.el and flyspell.el cannot be used out of the box in
XEmacs, I am using for Debian one of the versions before the CVS->bzr
migration heavily patched to also work for XEmacs and keep a consistent
spellchecking interface across different Emacs flavors. As a matter of fact
it is even patched to work with emacs 21.3, but this is something I do not
want to maintain any longer.
I am thinking about two possible approaches, one is a compromise, minibuffer
is somewhat special, so ispell process directory could be set to $HOME only
when spellchecking minibuffer, and name of buffer where ispell process is
started faked in this specific case, so process is not killed when buffer is
killed. Since process is asigned to $HOME no problems are expected when this
is done from a buffer in a removable device creating a minibuffer. However,
usual ispell behavior will not be fully honoured here, but this is a
side use.
Something like
(if (window-minibuffer-p)
(setq ispell-process-directory (expand-file-name "~/")
ispell-process-buffer-name
" *Minibuffer-1-has-spellcheck-enabled")
(setq ispell-process-directory default-directory
ispell-process-buffer-name (buffer-name)))
The second approach requires a clean and portable way of knowing the
parent buffer for the relevant minibuffer. In this case, just naming
ispell-process-buffer-name as parent buffer name may work.
I currently do not see a good way to do the second, so first approach should
be a reasonable compromise. I will test a bit more and commit if no further
problems appear.
--
Agustin
next prev parent reply other threads:[~2010-05-12 10:26 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 [this message]
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
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=20100512102606.GA12529@agmartin.aq.upm.es \
--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.