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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 35726-done <at> debbugs.gnu.org, ccq777 <at> gmail.com, aaronjensen <at> gmail.com
Subject: Re: bug#35726: 27.0.50;
 global-linum-mode doesn't work in emacsclient in several modes
Date: Fri, 07 Jun 2019 17:33:53 +0300

> From: Noam Postavsky <npostavs <at> gmail.com>
> Date: Wed, 15 May 2019 18:23:56 -0400
> Cc: 35726 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
>  changqi chen <ccq777 <at> gmail.com>
> 
> 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.

OK, done on the emacs-26 branch; closing.

Previous Next

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