GNU bug report logs - #1348
set-frame-width and set-frame-position seem buggy on at least MSWindows

Previous Next

Package: emacs;

Reported by: "Themba Fletcher" <themba <at> shirleymachine.com>

Date: Fri, 14 Nov 2008 22:55:04 UTC

Severity: normal

Done: martin rudalics <rudalics <at> gmx.at>

Bug is archived. No further changes may be made.

Full log


Message #180 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 1348 <at> debbugs.gnu.org, grishka <at> gmx.de, jasonr <at> f2s.com,
        bug-gnu-emacs <at> gnu.org
Subject: Re: bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows
Date: Wed, 03 Dec 2008 20:32:50 +0200
> Date: Wed, 03 Dec 2008 11:17:13 +0100
> From: martin rudalics <rudalics <at> gmx.at>
> CC: 1348 <at> emacsbugs.donarmstrong.com, grishka <at> gmx.de, jasonr <at> f2s.com, 
>  bug-gnu-emacs <at> gnu.org
> 
> If we think that grischka's patch is wrong, we should be able to
> give an (at least hypothetical) example why.

I don't see a need for giving an example for something that is so
blatantly wrong: it calls one thread's code from within another.
Since the Emacs input thread was written _specifically_ to overcome
problems with delivering input asynchronously, it should be clear to
anyone that mixing such threads is dead wrong, period.





This bug report was last modified 10 years and 297 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.