GNU bug report logs - #35726
27.0.50; global-linum-mode doesn't work in emacsclient in several modes

Previous Next

Package: emacs;

Reported by: ccQ's Gmail <ccq777 <at> gmail.com>

Date: Tue, 14 May 2019 04:00:04 UTC

Severity: normal

Found in version 27.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #23 received at 35726 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Aaron Jensen <aaronjensen <at> gmail.com>
Cc: 35726 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 changqi chen <ccq777 <at> gmail.com>
Subject: Re: bug#35726: 27.0.50;
 global-linum-mode doesn't work in emacsclient in several modes
Date: Wed, 15 May 2019 18:23:56 -0400
Aaron Jensen <aaronjensen <at> gmail.com> writes:

>>  3. Remove from linum.el and display-line-numbers.el the condition
>>     that causes this:
>>
>>        (and (daemonp) (null (frame-parameter nil 'client)))
>>
>>     I don't think that bug#27210 will affect display-line-numbers, and
>>     linum is semi-deprecated.
>
> For what it's worth, I'd vote for #3 since linum is semi-deprecated
> and I rather like the change, so I'd prefer not to revert it.

I think removing the check from display-line-numbers.el would make
sense, but IMO we should leave it in linum.el because having Emacs
freeze on startup is worse than having to toggle global-linum-mode when
using emacsclient.

Or if we really want to remove it from linum.el, there is my patch at
https://debbugs.gnu.org/27210#28 which can fix that bug without the
above check.





This bug report was last modified 5 years and 344 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.