bug#24583: Xpra compatibility

bug#24583: Xpra compatibility

[Eugene J.]

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

 All recent versions of Emacs seems to have the bug (
http://xpra.org/trac/ticket/1327) when used with xpra.

If you have any insight to share it will be greatly appreciated.

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

bug#24583: Xpra compatibility

[martin rudalics]

 >   All recent versions of Emacs seems to have the bug (
 > http://xpra.org/trac/ticket/1327) when used with xpra.
 >
 > If you have any insight to share it will be greatly appreciated.

Can you try with ‘frame-resize-pixelwise’ set to t?

martin

bug#24583: Xpra compatibility

[martin rudalics]

 > Thank you very much. It helped!

Please keep the bug number cc'd!

 > Actually I tried it once before but I forgot to restart Emacs after
 > changing it :(

Doesn't the next frame you create after setting this already exhibit the
intended pixelwise behavior?  Size hints are such a pain ...

martin

bug#24583: Xpra compatibility

[martin rudalics]

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

bug#24583: Xpra compatibility

[Eugene J.]

[-- 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 --]

bug#24583: Xpra compatibility

[martin rudalics]

 >> 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

Interesting.  Maybe I'll try to do that automatically although some
platforms are known to misbehave ...

       /* Don't set hints when maximized or fullscreen.  Apparently KWin and
          Gtk3 don't get along and the frame shrinks (!).

... and one author freely admitted that ...

     XSizeHints hints;		/* Sometimes I hate X Windows... */

martin

bug#24583: Xpra compatibility

[Stefan Kangas]

"Eugene J." <w3techplayground@gmail.com> writes:

>  All recent versions of Emacs seems to have the bug
>  (http://xpra.org/trac/ticket/1327) when used with xpra.
>
> If you have any insight to share it will be greatly appreciated.

From reading the above ticket, the issue has been solved by xpra.  It
looks like the correct version to use is xpra 1.0 or later.

Are you still seeing this issue?  If I don't hear back from you within
a couple of weeks, I'll just assume that this has since been resolved
and close this bug.

Best regards,
Stefan Kangas

bug#24583: Xpra compatibility

[Stefan Kangas]

Stefan Kangas <stefan@marxist.se> writes:

> "Eugene J." <w3techplayground@gmail.com> writes:
>
>>  All recent versions of Emacs seems to have the bug
>>  (http://xpra.org/trac/ticket/1327) when used with xpra.
>>
>> If you have any insight to share it will be greatly appreciated.
>
>>From reading the above ticket, the issue has been solved by xpra.  It
> looks like the correct version to use is xpra 1.0 or later.
>
> Are you still seeing this issue?  If I don't hear back from you within
> a couple of weeks, I'll just assume that this has since been resolved
> and close this bug.

More information was requested, but none was given within 4 weeks, so
I'm going to assume this has been fixed and close this bug.

If this is still an issue, please reply to this email (use "Reply to
all" in your email client) and we can reopen the bug report.

Best regards,
Stefan Kangas