[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#32921: emacsclient obeys Xresources even when launched with -nw
From: |
Eli Zaretskii |
Subject: |
bug#32921: emacsclient obeys Xresources even when launched with -nw |
Date: |
Wed, 18 May 2022 17:00:52 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: jimis@gmx.net, 32921@debbugs.gnu.org
> Date: Wed, 18 May 2022 15:52:21 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So the difference is between (a) taking notice of the reverseVideo
> > resource at startup timer as opposed to (b) at frame creation time, is
> > that right? If so, I think this might affect the use case whereby
> > someone changes the X resources after Emacs has already started, or
> > something?
>
> Yes, it would change that behaviour... but I think we'd want that? If
> the user changes reverseVideo, then I think it's natural to expect
> subsequent frames to heed that. (Not that I think that's very
> important -- people generally don't do that.)
It's a change in long-standing behavior, and someone out there is
bound to want it.
> > Maybe it would be safer to add a special frame-parameter which will
> > record the fact that some parameters came from X resources, and will
> > then refrain from applying those parameters to TTY frames? Or maybe
> > we should have some other special construct in default-frame-alist
> > that prevents some parameters from being applied to TTY frames?
> > Because I think reverseVideo is just one example of such parameters.
>
> Yes, a default-frame-parameters-for-window-system (or something like
> that) variable might make sense in general. Then users could specify
> these things separately for TTY and GUI.
>
> But are there many parameters like this? Most of the frame parameters
> are ignored on TTY...
Many are ignored, but some are relevant:
. foreground and background colors
. cursor blinking
. menuBar
. tabBar
> > Yes, we emulate X resources using the Registry on MS-Windows (although
> > I think this is largely unknown and unused).
>
> I see. I wondered whether this was for using X servers under Windows,
> somehow... (I think that existed a long time ago, at least?)
It did? I only know about X servers used to run X programs from
remote Unix hosts. And there's a Cygwin build of Emacs, of course,
but that runs as if on a Unix host.
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Lars Ingebrigtsen, 2022/05/18
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Eli Zaretskii, 2022/05/18
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Lars Ingebrigtsen, 2022/05/18
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Po Lu, 2022/05/18
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Eli Zaretskii, 2022/05/19
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Po Lu, 2022/05/19
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Eli Zaretskii, 2022/05/19
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Po Lu, 2022/05/19
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Eli Zaretskii, 2022/05/19
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Po Lu, 2022/05/19
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Eli Zaretskii, 2022/05/19
- bug#32921: emacsclient obeys Xresources even when launched with -nw, Po Lu, 2022/05/19