* bug#24583: Xpra compatibility
@ 2016-10-01 12:50 Eugene J.
2016-10-01 18:49 ` martin rudalics
2019-11-08 3:26 ` Stefan Kangas
0 siblings, 2 replies; 8+ messages in thread
From: Eugene J. @ 2016-10-01 12:50 UTC (permalink / raw
To: 24583
[-- 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 --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#24583: Xpra compatibility
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>
2019-11-08 3:26 ` Stefan Kangas
1 sibling, 1 reply; 8+ messages in thread
From: martin rudalics @ 2016-10-01 18:49 UTC (permalink / raw
To: Eugene J., 24583
> 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#24583: Xpra compatibility
[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>
0 siblings, 1 reply; 8+ messages in thread
From: martin rudalics @ 2016-10-02 8:29 UTC (permalink / raw
To: Eugene J., 24583
> 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#24583: Xpra compatibility
[not found] ` <CADZ8+p1d_edCipxPWw7ARpS2Aw0RJ9ONzS48BS+GaBaAsSNzFw@mail.gmail.com>
@ 2016-10-02 9:26 ` martin rudalics
2016-10-03 8:43 ` Eugene J.
0 siblings, 1 reply; 8+ messages in thread
From: martin rudalics @ 2016-10-02 9:26 UTC (permalink / raw
To: Eugene J.; +Cc: 24583
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#24583: Xpra compatibility
2016-10-02 9:26 ` martin rudalics
@ 2016-10-03 8:43 ` Eugene J.
2016-10-04 6:49 ` martin rudalics
0 siblings, 1 reply; 8+ messages in thread
From: Eugene J. @ 2016-10-03 8:43 UTC (permalink / raw
To: martin rudalics, 24583
[-- 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 --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#24583: Xpra compatibility
2016-10-03 8:43 ` Eugene J.
@ 2016-10-04 6:49 ` martin rudalics
0 siblings, 0 replies; 8+ messages in thread
From: martin rudalics @ 2016-10-04 6:49 UTC (permalink / raw
To: Eugene J., 24583
>> 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#24583: Xpra compatibility
2016-10-01 12:50 bug#24583: Xpra compatibility Eugene J.
2016-10-01 18:49 ` martin rudalics
@ 2019-11-08 3:26 ` Stefan Kangas
2019-12-05 11:18 ` Stefan Kangas
1 sibling, 1 reply; 8+ messages in thread
From: Stefan Kangas @ 2019-11-08 3:26 UTC (permalink / raw
To: Eugene J.; +Cc: 24583
"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
^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#24583: Xpra compatibility
2019-11-08 3:26 ` Stefan Kangas
@ 2019-12-05 11:18 ` Stefan Kangas
0 siblings, 0 replies; 8+ messages in thread
From: Stefan Kangas @ 2019-12-05 11:18 UTC (permalink / raw
To: Eugene J.; +Cc: 24583-done
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
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-12-05 11:18 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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.
2016-10-04 6:49 ` martin rudalics
2019-11-08 3:26 ` Stefan Kangas
2019-12-05 11:18 ` Stefan Kangas
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.