all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eugene J." <w3techplayground@gmail.com>
To: martin rudalics <rudalics@gmx.at>, 24583@debbugs.gnu.org
Subject: bug#24583: Xpra compatibility
Date: Mon, 3 Oct 2016 11:43:04 +0300	[thread overview]
Message-ID: <CADZ8+p214UAuiQ5vsLT4OdNJAdD+mrx9Unjqh3x2DWm4WW0Q_w@mail.gmail.com> (raw)
In-Reply-To: <57F0D2CF.5080702@gmx.at>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

> But existing frames do, correct?
yes. When I set  ‘frame-resize-pixelwise’ to t only newly created frames
work properly.

> What happens when you explicitly call ‘x-wm-set-size-hint’ for such an
>existing frame?  After having customized ‘frame-resize-pixelwise’ to t,
>obviously.
The frame magically starts to resize properly O_O

On 2 October 2016 at 12:26, martin rudalics <rudalics@gmx.at> wrote:

> Please do CC to 24583@debbugs.gnu.org as I asked before.  This might be
> of interest for other people as well.
>
> > Yes new frame doesn't glitch.
>
> But existing frames do, correct?
>
> What happens when you explicitly call ‘x-wm-set-size-hint’ for such an
> existing frame?  After having customized ‘frame-resize-pixelwise’ to t,
> obviously.
>
> martin
>
>

[-- Attachment #2: Type: text/html, Size: 1773 bytes --]

  reply	other threads:[~2016-10-03  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01 12:50 bug#24583: Xpra compatibility Eugene J.
2016-10-01 18:49 ` martin rudalics
     [not found]   ` <CADZ8+p1a8Fx4sgWrD=WcLUmZXOXs6A5THrvLAvOJicSYEJWJ_w@mail.gmail.com>
2016-10-02  8:29     ` martin rudalics
     [not found]       ` <CADZ8+p1d_edCipxPWw7ARpS2Aw0RJ9ONzS48BS+GaBaAsSNzFw@mail.gmail.com>
2016-10-02  9:26         ` martin rudalics
2016-10-03  8:43           ` Eugene J. [this message]
2016-10-04  6:49             ` martin rudalics
2019-11-08  3:26 ` Stefan Kangas
2019-12-05 11:18   ` Stefan Kangas

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

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

  git send-email \
    --in-reply-to=CADZ8+p214UAuiQ5vsLT4OdNJAdD+mrx9Unjqh3x2DWm4WW0Q_w@mail.gmail.com \
    --to=w3techplayground@gmail.com \
    --cc=24583@debbugs.gnu.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.