From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35726@debbugs.gnu.org, changqi chen <ccq777@gmail.com>
Subject: bug#35726: Further information of line number bug.
Date: Wed, 15 May 2019 12:21:42 -0700 [thread overview]
Message-ID: <CAHyO48zg15vHEY+tYDmes+hNhz3NTQNtu5rLDap3Lhgo14KXXQ@mail.gmail.com> (raw)
In-Reply-To: <83sgtf91ip.fsf@gnu.org>
On Wed, May 15, 2019 at 8:32 AM Eli Zaretskii <eliz@gnu.org> wrote:
> Thinking about this, I see several possible solutions:
>
> 1. Revert the fix for bug#24218 (since it's just an aesthetic issue).
> Or maybe someone sees how to fix that bug in a way that doesn't
> change the order of visiting the file and creating the client
> frame.
>
> 2. Modify define-globalized-minor-mode to also use some other hook,
> like maybe server-after-make-frame-hook. This has a downside that
> we will need to scan all the buffers on the frame, which might
> slow down client frame creation.
>
> 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.
Aaron
next prev parent reply other threads:[~2019-05-15 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 2:07 bug#35726: 27.0.50; global-linum-mode doesn't work in emacsclient in several modes ccQ's Gmail
2019-05-14 4:21 ` bug#35726: Further information of line number bug changqi chen
2019-05-15 15:32 ` Eli Zaretskii
2019-05-15 17:35 ` npostavs
2019-05-15 18:05 ` Eli Zaretskii
2019-05-15 19:21 ` Aaron Jensen [this message]
2019-05-15 22:23 ` bug#35726: 27.0.50; global-linum-mode doesn't work in emacsclient in several modes Noam Postavsky
2019-06-07 14:33 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHyO48zg15vHEY+tYDmes+hNhz3NTQNtu5rLDap3Lhgo14KXXQ@mail.gmail.com \
--to=aaronjensen@gmail.com \
--cc=35726@debbugs.gnu.org \
--cc=ccq777@gmail.com \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).