unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Cadilhac <michael.cadilhac-@t-lrde.epita.fr>
Cc: micha@lrde.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [michael.cadilhac-@t-lrde.epita.fr: sit-for (detect_input_pending ?) and postfix input methods.]
Date: Wed, 05 Oct 2005 18:27:39 +0200	[thread overview]
Message-ID: <87y858udxg.fsf@mahaena.lrde> (raw)
In-Reply-To: <E1EN3ff-0002eS-00@etlken> (Kenichi Handa's message of "Wed, 05 Oct 2005 16:26:35 +0900")

Kenichi Handa <handa@m17n.org> writes:

> In article <E1EMIa9-0005hI-PX@fencepost.gnu.org>, "Richard M. Stallman" <rms@gnu.org> writes:
>
>> Would you please look at this, and ack?  (We have no maintainer for
>> flyspell now.)
>
> As for the original problem of flyspell, how about this
> workaround?
>
> *** flyspell.el	23 Sep 2005 10:59:25 +0900	1.75
> --- flyspell.el	05 Oct 2005 16:19:56 +0900	
> ***************
> *** 770,776 ****
>        ((get this-command 'flyspell-delayed)
>         ;; the current command is not delayed, that
>         ;; is that we must check the word now
> !       (sit-for flyspell-delay))
>        (t t)))
>      (t t)))
>
> --- 770,777 ----
>        ((get this-command 'flyspell-delayed)
>         ;; the current command is not delayed, that
>         ;; is that we must check the word now
> !       (and (not unread-command-events)
> ! 	   (sit-for flyspell-delay)))
>        (t t)))
>      (t t)))

   Thanks for your deep explanation !

   Note that with your workaround, you're disabling a flyspell feature
   which  is, when you  type a  world and  don't add  delimiters, this
   world will eventually be checked after `flyspell-delay' seconds.

   I think the  behavior of sit-for should be  corrected, or explained
   in the documentation.

   However, I'll use your workaround as this feature is less important
   to me than the bug fix.

   Thanks !

-- 
    Michael Cadilhac, a.k.a. Micha [mika] |
                    Epita/LRDE promo 2007 |  Please note that you should
  2 rue de la Convention | 08.70.65.13.14 |  s/-@t-/@/ my mail address.
94270 Le Kremlin Bicetre | 06.23.20.31.30 |

  reply	other threads:[~2005-10-05 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1EMIa9-0005hI-PX@fencepost.gnu.org>
2005-10-05  7:26 ` [michael.cadilhac-@t-lrde.epita.fr: sit-for (detect_input_pending ?) and postfix input methods.] Kenichi Handa
2005-10-05 16:27   ` Michael Cadilhac [this message]
2005-10-06  1:01     ` Kenichi Handa
2005-10-06 12:36       ` Michael Cadilhac
2005-10-06 12:45         ` Kenichi Handa
2005-10-05 17:42   ` Stefan Monnier
2005-10-06  1:17     ` Kenichi Handa
2005-10-10  4:15   ` Richard M. Stallman
2005-10-10  9:46     ` Kim F. Storm
2005-10-10 10:53       ` David Kastrup

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y858udxg.fsf@mahaena.lrde \
    --to=michael.cadilhac-@t-lrde.epita.fr \
    --cc=emacs-devel@gnu.org \
    --cc=micha@lrde.org \
    --cc=rms@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).