unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>, martin rudalics <rudalics@gmx.at>
Cc: 9366@debbugs.gnu.org
Subject: bug#9366: Display geometry change hook
Date: Sat, 19 Sep 2020 18:42:23 +0300	[thread overview]
Message-ID: <838sd53h9c.fsf@gnu.org> (raw)
In-Reply-To: <87363dpyz3.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat,  19 Sep 2020 17:28:48 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 19 Sep 2020 17:28:48 +0200
> Cc: 9366@debbugs.gnu.org
> 
> > +#ifdef HAVE_XRANDR
> > +    /* xrandr extension may or may not be present on a display =>
> > +       can't check for it as a constant C "case" arg, hence "if" here  */
> > +    if (dpyinfo->xrandr_present &&
> > +        (event.type == (dpyinfo->xrandr_event_base + RRScreenChangeNotify)))
> > +      {
> > +        /* FIXME: is XRRUpdateConfiguration actually called by the toolkit/gtk+?
> 
> But looking through the code, it doesn't seem like Emacs has grown this
> capability over the years?  But I may be looking in the wrong places.
> 
> In any case, it sounds useful?  I haven't tried applying the patch,
> though, so I don't know how much work that would be to bring it up to
> date.
> 
> Anybody got any opinions here?

Do we really have to do this on such a low level?  Why cannot we call
such a hook from change_frame_size, which would allow us to do that in
platform-independent manner?

Martin, am I missing something here?





  reply	other threads:[~2020-09-19 15:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  5:16 bug#9366: Display geometry change hook David De La Harpe Golden
2011-08-25  5:55 ` Eli Zaretskii
2011-08-25 12:42   ` David De La Harpe Golden
2011-08-31 17:43 ` bug#9366: Attempting to add myself to this bug's CC list Edward O'Connor
2020-09-19 15:28 ` bug#9366: Display geometry change hook Lars Ingebrigtsen
2020-09-19 15:42   ` Eli Zaretskii [this message]
2020-09-20  8:14     ` martin rudalics
2020-09-20  8:25       ` Lars Ingebrigtsen
2020-09-20  8:56       ` Eli Zaretskii
2020-09-20 12:24         ` martin rudalics
2020-09-20 12:59           ` Eli Zaretskii
2020-09-21  7:26             ` martin rudalics
2020-09-21 14:21               ` Eli Zaretskii
2020-09-22  7:16                 ` martin rudalics
2020-09-22 14:16                   ` Eli Zaretskii
2020-09-23  7:15                     ` martin rudalics
2020-09-23  7:47                       ` Corwin Brust
2020-09-23  8:14                         ` martin rudalics
2020-09-23 14:35                           ` Eli Zaretskii
2020-09-23 14:29                       ` Eli Zaretskii
2020-09-23 17:41                         ` martin rudalics
2020-09-23 18:03                           ` Eli Zaretskii
2020-09-22 15:04                   ` Lars Ingebrigtsen

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=838sd53h9c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=9366@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --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).