all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Agustin Martin <agustin.martin@hispalinux.es>
To: 6143-done@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#6143: 24.0.50; don't ispell-kill-ispell over and over
Date: Thu, 13 May 2010 13:05:07 +0200	[thread overview]
Message-ID: <20100513110507.GA17120@agmartin.aq.upm.es> (raw)
In-Reply-To: <jwv4oid5h95.fsf-monnier+emacs@gnu.org>

On Wed, May 12, 2010 at 10:28:26AM -0400, Stefan Monnier wrote:
> > 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
> 
> How about associating ispell processes with default-directories rather
> than just with buffers?  I.e. share ispell processes between buffers
> that share default-directory.  

That is current behavior unless buffers use different languages for
spellchecking or have a set of localwords defined (which may be different
for different buffers, needing process restart).

> And use $HOME whenever possible
> (i.e. when we can determine that there's no local dictionary in
> default-directory).

Doing this without the kill-ispell-on-kill-buffer machinery may still leave
some corner cases. 

Noticed that this dual personal dictionary behavior seems to be an ispell
only feature. If properly handling this is causing more harm than good, it
may even be dropped by forcing ispell-process-directory to always be $HOME.  

Anyway, I have commited a possible fix for jidanni's problem, making
parent-dir 'owner' of ispell process in a minibuffer'. Hope this fixes the
problem.

Closing bug report,

-- 
Agustin





  reply	other threads:[~2010-05-13 11:05 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 [this message]
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=20100513110507.GA17120@agmartin.aq.upm.es \
    --to=agustin.martin@hispalinux.es \
    --cc=6143-done@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.