From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#32921: emacsclient obeys Xresources even when launched with -nw Date: Thu, 19 May 2022 21:09:51 +0800 Message-ID: <87h75l1xeo.fsf@yahoo.com> References: <87o7zvc8xi.fsf@gnus.org> <835ym3f0xt.fsf@gnu.org> <875ym3c7bj.fsf@gnus.org> <834k1nezs3.fsf@gnu.org> <87ee0raqy2.fsf@gnus.org> <87czgal2tt.fsf@yahoo.com> <838rqydmy8.fsf@gnu.org> <878rqyklqj.fsf@yahoo.com> <831qwqdj2w.fsf@gnu.org> <87fsl5sxse.fsf@yahoo.com> <83y1yxdffv.fsf@gnu.org> <87czg93juo.fsf@yahoo.com> <83sfp5d7ad.fsf@gnu.org> Reply-To: Po Lu Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15866"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) Cc: 32921@debbugs.gnu.org, larsi@gnus.org, jimis@gmx.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 19 15:11:15 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nrfvu-0003xg-P0 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 May 2022 15:11:14 +0200 Original-Received: from localhost ([::1]:49736 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nrfvt-0001yl-8m for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 May 2022 09:11:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60094) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nrfvi-0001yK-1p for bug-gnu-emacs@gnu.org; Thu, 19 May 2022 09:11:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40896) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nrfvh-0002Wr-Ov for bug-gnu-emacs@gnu.org; Thu, 19 May 2022 09:11:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nrfvh-0000UJ-JP for bug-gnu-emacs@gnu.org; Thu, 19 May 2022 09:11:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Po Lu Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 19 May 2022 13:11:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32921 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 32921-submit@debbugs.gnu.org id=B32921.16529658071786 (code B ref 32921); Thu, 19 May 2022 13:11:01 +0000 Original-Received: (at 32921) by debbugs.gnu.org; 19 May 2022 13:10:07 +0000 Original-Received: from localhost ([127.0.0.1]:34793 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nrfuo-0000Sk-MD for submit@debbugs.gnu.org; Thu, 19 May 2022 09:10:06 -0400 Original-Received: from sonic303-21.consmr.mail.ne1.yahoo.com ([66.163.188.147]:41582) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nrfun-0000S3-EK for 32921@debbugs.gnu.org; Thu, 19 May 2022 09:10:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1652965800; bh=qPOXLmBtaQY2nARaTqXJxZGQoQbVEw0F1hyi648Q7SU=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From:Subject:Reply-To; b=c5mXqOW+0aWqqefUgJjgVo73TWsCbZqoyPhPZ/o8Z6m2MxdWeYiB4DE6RvfLXLjKUe9S2DuN/IpTWBRVM7fpvHoQZ6PzOVC3RnHTHIdRV3+HKmSRWhFiKYm5DlQIHl+V7ohGYK1pKUKuYno3exj0mHho55YEF54K9yfAD3r6PtATl69dqPi4KsmH5SA+KXQmGCCW/6uCphAItpo51l+aIxVeJ1tZz6BjMVyBnY6T3PX5TSMuBin2UyWsoCJ/C+SJoqzwNJBZ1r/dCURPfhGkYg36GdmyMdEQaa74CW5lOb8c+9athQBEj40w9SwF7Xp1LfINMN3EdWFCqMniMCZAgQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1652965800; bh=eufE4qXCfNyJCr77VLvpPa+qmkaYwqn0ZY62e6etc+p=; h=X-Sonic-MF:From:To:Subject:Date:From:Subject; b=bN+8+2giotyueEg5pavH1RLK+SFwZPf27jgps3w6Ir/bUGQos1ijiV419VPuvDtGv/zxCg88IgwV7e+yGj5zRhyy3uoBtgS4a1iWxhmi0NRUk5WSFXdIrlRnW2F2aknfwDHcmWu2kmIxIUb+YE0ENQcN2PPM4j8Ya9r0oecxeORfn+vQVPOL9Wtdm9An6DRvro10b77UuLR148G6dVqqThgKpFO3I3gfzNszgorCDKj15FLgiXD1e76buKBlYMxdvQh3XOdDXZnPBTs3Jc3zXNY6RUvI35aOH2rpdZFOcpVZ1d31hGQxWY0epPP1Osi0n3j6a4gnKcVUn38bHZncuw== X-YMail-OSG: ElRpwKIVM1kFs8oe7DSgv2u59fCcqTC0U6mhG1th5jMDVmH7_OM.30EoF3Nk.i5 TigkAMt0rZAIL_f9u_MwYFy2ea71hij9_e6HHRmTUyYiL_wPigdgzttj6d9Yh7N2Rx8cGOB0F2bc OLldNnO9KKH2kJ9Xp6BT2GhP6wkADLbspcW_27_XdqJi973YKpmF7ekueJiQlOk9r5RCfW8LwgYZ EPj6K802Tlb8889frJTfqBpmo6bO.GhZA2Tmcy.EDpfGz5hm733_NS0DCyjIVjHoDpaCarRuZUpz 38Vd4PDDTQvdFLinTLQl9SGJd.2Qv_fFDqx5oAL64X.uTnh3VaY8pgA4F7nKzrOfm.zZi08YuAUA 72LUlwg7s2OO7fKNZRq7XZ9PrMDdOObGMmAf.moScn56pSxGAse17DomazR1VebOjQEzEn.LnLDh NPcR_IvkdzWmV.4Z99UcsV3hQTI0eb5aFKAIY.cpIEg.eGx6QnIXUgJRsfNN_TD6MMpUV6duMnCB yEkwCLm8KNZHmOoVNIrXgvm3cDwl7tzUL165hT87aDwjDcudqr8HqwRG2B4LWS0cF2W0TuGXVePM 7WyR6WoimAGg6m7OiSnva44tEO4Ge7Fy4kGOLgZ6v59sBeJ5_eyQv2gGr9drv6Dazes7kskPPRJm WcQtWhL9hI1fy.Noa7P2udh0sPAZMuzx4R65.y6oqwqrHhlRjDS8wrdLHYiLQrmcanT.KPHHVdKM V3N0FbeCijzJDOZ96idr1Cjw1BZD5e3XefwmP_RMgpjU.IT4N65vihhWDRl7l5Q3UQXMPMWPOoHf G5.JXRyLBzK.lAKmlULLxGSLHHHkgpUsL.pa5mbK1p X-Sonic-MF: Original-Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.ne1.yahoo.com with HTTP; Thu, 19 May 2022 13:10:00 +0000 Original-Received: by hermes--canary-production-sg3-7959d4d9bd-bjkcg (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 3bd6ef06ea25d9f6590ec137c6d82124; Thu, 19 May 2022 13:09:55 +0000 (UTC) In-Reply-To: <83sfp5d7ad.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 19 May 2022 15:40:58 +0300") X-Mailer: WebService/1.1.20225 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:232642 Archived-At: Eli Zaretskii writes: > We already do that, see the information and the backtrace posted by > Lars a while ago. Hmm... then why does this code still exist at all? x-create-frame-with-faces should take care of setting the `reverse' parameter entirely. Could you please explain what you meant by "startup timer" here? > 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? Though I doubt this really matters, since X resources cannot change after Emacs starts. > The code in x-win.el does something beyond that: it caters for people > who have X resources specified on their user-private files, and want > those settings to be in effect on all displays. But then why only a single resource, and not all of them? Especially an obscure one like reverseVideo? BTW, I think I found out why this situation is. Before Emacs 19.29, reverseVideo and selectionTimeout were both set up in x-win.el assuming that there would only ever be a single display, just like the other frame parameters in Fx_create_frame. When support for multiple displays was added in 19.29, the changes to make X resources affecting frame parameters specific to each display were made to the C code in Fx_create_frame, but not to the two parameters set in Lisp. Whether or not that was done intentionally is anyone's guess, but I think it was a bug, or an oversight. > (And besides, what is the chance that someone will want different > values of reverseVideo on different displays? I think the chances for > that are nil.) Many other programs accept a resource named reverseVideo (it and -rv are a very standard knobs for X programs), so I can imagine someone placing: *.reverseVideo: on in the X resources for an X server with dark window decorations, and vice versa. Emacs should create frames with the colors specified on each server it is connected to. > Because we will otherwise break a long-standing behavior. [...] > People who want Emacs to behave like you describe can simply remove > this setting from their ~/.Xdefaults. That wouldn't be useful, since Emacs doesn't even load ~/.Xdefaults if the X server it connected to already has some resources loaded. Doing that is the job of the session script(s) that started the X server. > Not necessarily, because frame-parameters applied by > gui_default_parameter could override those we took from ~/.Xdefaults. I meant the parameters applied by gui_default_parameter when the parameter is not present in `default-frame-alist' or the ALIST argument. Thanks.