From: "Jan D." <jan.h.d@swipnet.se>
To: martin rudalics <rudalics@gmx.at>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
"19972@debbugs.gnu.org" <19972@debbugs.gnu.org>
Subject: bug#19972: 24.4; Font size change doesn't update (window-total-width)
Date: Tue, 03 Mar 2015 12:05:19 +0100 [thread overview]
Message-ID: <54F5956F.10009@swipnet.se> (raw)
In-Reply-To: <54F58A29.30709@gmx.at>
martin rudalics skrev den 2015-03-03 11:17:
> > Actually not. NS also only changes stuff when it gets an event that
> informs about resize.
>
> IIUC Emacs doesn't run a timer when issuing a resize request on NS. So
> I have no idea how two subsequent resize requests are handled there.
> Consider the case where Lisp code sends a height change request first
> and a width change request afterwards: Which is the height Emacs asks
> for in the second request? The one before the first request or the one
> after the first request has been honored?
Lisp code that expects resize changes to be handeled synchronously and
in order are fundamentally broken.
That said, it may very well be a race here, i.e. the wrong height gets
sent. But this is only because bad Lisp code assumes synchronous handling.
Jan D.
next prev parent reply other threads:[~2015-03-03 11:05 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 2:31 bug#19972: 24.4; Font size change doesn't update (window-total-width) Joost Kremers
2015-03-01 15:14 ` martin rudalics
2015-03-01 15:28 ` Eli Zaretskii
2015-03-01 15:54 ` martin rudalics
2015-03-01 17:07 ` Joost Kremers
2015-03-01 17:46 ` Eli Zaretskii
2015-03-01 20:43 ` Joost Kremers
2015-03-02 3:30 ` Eli Zaretskii
2015-03-02 3:59 ` Joost Kremers
2015-03-02 14:04 ` Eli Zaretskii
2015-03-02 17:08 ` martin rudalics
2015-03-02 17:35 ` Eli Zaretskii
2015-03-02 18:12 ` martin rudalics
2015-03-02 18:25 ` Eli Zaretskii
2015-03-02 18:43 ` martin rudalics
2015-03-02 18:46 ` Eli Zaretskii
2015-03-02 22:26 ` Joost Kremers
2015-03-03 3:36 ` Eli Zaretskii
2015-03-03 8:07 ` martin rudalics
2015-03-03 9:06 ` Jan Djärv
2015-03-03 10:17 ` martin rudalics
2015-03-03 11:05 ` Jan D. [this message]
2015-03-03 11:26 ` martin rudalics
2015-03-03 12:08 ` Jan D.
2015-03-03 12:08 ` Joost Kremers
2015-03-03 8:06 ` martin rudalics
2015-03-02 17:08 ` martin rudalics
2015-03-02 17:07 ` martin rudalics
2015-03-02 17:06 ` martin rudalics
2015-03-01 17:06 ` Joost Kremers
2015-03-02 3:18 ` Joost Kremers
2015-03-02 17:09 ` martin rudalics
2015-03-02 17:24 ` Eli Zaretskii
2015-03-02 18:12 ` martin rudalics
2015-03-02 18:26 ` Eli Zaretskii
2015-03-03 10:38 ` martin rudalics
2015-03-03 12:23 ` Joost Kremers
2015-03-04 15:10 ` martin rudalics
2017-10-02 8:48 ` martin rudalics
2015-03-02 7:57 ` bug#19972: " Steve Purcell
2015-03-02 13:27 ` Eli Zaretskii
2015-03-02 14:07 ` Steve Purcell
2015-03-02 14:09 ` Steve Purcell
2015-03-02 14:24 ` Eli Zaretskii
2015-03-02 17:37 ` Jan D.
2015-03-02 14:23 ` Eli Zaretskii
2015-03-02 17:42 ` Jan D.
2015-03-02 17:56 ` Eli Zaretskii
2015-03-02 19:06 ` Jan D.
2015-03-02 19:52 ` Eli Zaretskii
2015-03-02 20:19 ` Jan D.
2015-03-03 16:11 ` Eli Zaretskii
2015-03-03 17:47 ` martin rudalics
2015-03-03 18:02 ` Eli Zaretskii
2015-03-03 18:36 ` martin rudalics
2015-03-03 18:38 ` Eli Zaretskii
2015-03-04 15:10 ` martin rudalics
2015-03-04 17:47 ` Eli Zaretskii
2015-03-04 18:45 ` martin rudalics
2015-03-04 18:59 ` Eli Zaretskii
2015-03-04 19:25 ` Jan D.
2015-03-05 8:06 ` martin rudalics
2015-03-05 16:34 ` Eli Zaretskii
2015-03-05 18:14 ` martin rudalics
2015-03-05 20:22 ` Eli Zaretskii
2015-03-05 21:15 ` martin rudalics
2015-03-06 8:09 ` Eli Zaretskii
2015-03-06 9:21 ` martin rudalics
2015-03-06 10:58 ` Eli Zaretskii
2015-03-02 14:44 ` Drew Adams
2015-03-02 15:02 ` Steve Purcell
2015-03-02 17:10 ` martin rudalics
2015-03-02 17:23 ` Steve Purcell
2015-03-02 18:12 ` martin rudalics
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=54F5956F.10009@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=19972@debbugs.gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=rudalics@gmx.at \
/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).