unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@flint.cs.yale.edu>
Cc: bob@rattlesnake.com, miles@gnu.org, emacs-devel@gnu.org,
	Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>
Subject: Re: Bold by moving pixels problem
Date: 21 Jan 2004 00:39:00 -0500	[thread overview]
Message-ID: <jwvd69d7te3.fsf@asado.iro.umontreal.ca> (raw)
In-Reply-To: E19NsRW-0002It-RR@fencepost.gnu.org

>     That's not quite accurate.  The updating is about as immediate with
>     my synchronous signal handler as it is with the current async
>     signal handler, because it can take place any time QUIT is used,
>     which means "also in the middle of elisp code".
> 
> Please forgive my confusion.
> 
>     I've been running with synchronous signal handlers since I mentioned
>     it on this list and I'm pretty happy with it.
> 
> I think it would be good for more people to try it.

I have installed patches to that effect.
By default, nothing's changed.  But if you define SYNC_INPUT, then signal
handlers will only set a variable and the actual processing will be done
from UNBLOCK_INPUT or from QUIT, whichever occurs sooner.

Please try it out.  Normally, the only problem you might encounter with the
patch is that Emacs gets unresponsive.  If that happens, please try to
figure out how to reproduce it, and also try to get a (bunch of) C backtrace
of when the unresponsiveness happens.

I've been using a very similar patch for a while now with no problems.

If SYNC_INPUT has no ill effect, it would be good to make it the default
unconditionally.  This would allow us to get rid of the ugly BLOCK_INPUT
wrappers in alloc.c, for one thing.  It would also make Emacs more stable by
removing a whole class of hard to reproduce bugs (we've squashed some of
those over time, but as the recent mallopt problem showed, there are still
several lurking).


        Stefan

  reply	other threads:[~2004-01-21  5:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04  8:54 Bold by moving pixels problem Richard Stallman
2003-06-04 14:35 ` Stefan Monnier
2003-06-05 10:58   ` Richard Stallman
2004-01-21  5:39     ` Stefan Monnier [this message]
2003-06-04 23:30 ` Kim F. Storm
     [not found]   ` <E19O2Z4-0002Rk-GY@fencepost.gnu.org>
2003-06-06  1:45     ` Kim F. Storm
2003-06-06  0:46       ` Miles Bader
  -- strict thread matches above, loose matches on Subject: below --
2003-08-07  6:04 last-sexp-toggle-display Richard Stallman
2003-08-07 16:56 ` last-sexp-toggle-display Luc Teirlinck
2003-08-11 12:53   ` last-sexp-toggle-display Richard Stallman
2003-08-11 17:59     ` last-sexp-toggle-display Luc Teirlinck
2003-08-11 18:54       ` Bold by moving pixels problem Robert J. Chassell
2002-11-13  5:42 Gtk version getting closer Eli Zaretskii
2002-11-13 13:21 ` Robert J. Chassell
2002-11-14 12:16   ` Richard Stallman
2002-11-14 16:46     ` Robert J. Chassell
2002-11-15  2:20       ` Miles Bader
     [not found]         ` <m18EUbO-000IeAC@localhost>
2002-11-20 22:08           ` Bold by moving pixels problem Miles Bader
2002-11-21  0:21             ` Robert J. Chassell
2002-11-21  1:33               ` Stefan Monnier
2002-11-21  1:44                 ` Miles Bader
     [not found]                   ` <m18HRR2-000IeBC@localhost>
2002-12-17  5:00                     ` Miles Bader
2002-12-17  6:28                       ` Miles Bader
2002-12-17  7:08                         ` Miles Bader
2002-12-18 10:01                           ` Miles Bader
2002-12-18 12:26                             ` Kim F. Storm
2002-12-19  8:34                               ` Miles Bader
2002-12-19 10:18                                 ` Miles Bader
2002-12-19 12:18                                 ` Kim F. Storm
2002-12-19 11:27                                   ` Miles Bader
2002-12-19 12:25                                     ` Miles Bader
2002-12-19 13:55                                       ` Kim F. Storm
2003-01-07 11:02                                       ` Kim F. Storm
2003-01-07 14:02                                         ` Miles Bader
2003-01-09  7:28                                         ` Richard Stallman
2003-01-09  7:52                                           ` Miles Bader
2002-12-18 14:25                             ` Robert J. Chassell
2002-12-17 10:31                       ` Kim F. Storm
2002-12-17 16:38                       ` Robert J. Chassell
2002-12-17 23:54                         ` Miles Bader
2002-11-21  6:01               ` Eli Zaretskii

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=jwvd69d7te3.fsf@asado.iro.umontreal.ca \
    --to=monnier+gnu/emacs@flint.cs.yale.edu \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).