From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: contovob@tcd.ie, kisik21@fireburn.ru, 34639@debbugs.gnu.org
Subject: bug#34639: 26.1; Custom themes break terminal when switching to org-mode
Date: Thu, 28 Feb 2019 19:32:14 +0200 [thread overview]
Message-ID: <83mumfkee9.fsf@gnu.org> (raw)
In-Reply-To: <E1gzCav-0000vO-DS@fencepost.gnu.org> (message from Richard Stallman on Wed, 27 Feb 2019 22:42:49 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: contovob@tcd.ie, kisik21@fireburn.ru, 34639@debbugs.gnu.org
> Date: Wed, 27 Feb 2019 22:42:49 -0500
>
> > The main (perhaps the only) one is that linum.el displays line numbers
> > in the display margin, whereas the native line numbers are displayed
> > in the text area.
>
> Would it be difficult to add (in native line numbers) the option to put
> them in the display margin?
It's not easy, but should be possible, of course. However, I don't
want to do that at this time, because we don't have any way of letting
more than one feature use the display margins without interfering with
one another. Until we have an infrastructure in place to allow such
sharing of the margins, I firmly believe that core features should not
usurp the display margins, and will object to any core feature that
tries.
next prev parent reply other threads:[~2019-02-28 17:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 17:44 bug#34639: 26.1; Custom themes break terminal when switching to org-mode Vika Shleina
2019-02-24 18:23 ` Eli Zaretskii
2019-02-24 18:37 ` Vika Shleina
2019-02-24 18:47 ` Vika Shleina
2019-02-24 19:12 ` Eli Zaretskii
[not found] ` <871s3x0zfz.fsf@sakura.i-did-not-set--mail-host-address--so-tickle-me>
2019-02-24 19:26 ` Eli Zaretskii
2019-02-24 19:32 ` Vika Shleina
2019-02-24 19:35 ` Vika Shleina
2019-02-24 19:47 ` Eli Zaretskii
2019-02-24 19:53 ` Vika Shleina
2019-02-24 19:57 ` Eli Zaretskii
2019-02-24 20:05 ` Vika Shleina
2019-02-25 3:30 ` Eli Zaretskii
2019-02-25 18:58 ` Vika Shleina
2019-02-25 20:01 ` Basil L. Contovounesios
2019-02-26 2:59 ` Richard Stallman
2019-02-26 3:36 ` Eli Zaretskii
2019-02-26 4:55 ` Glenn Morris
2019-02-26 5:38 ` Eli Zaretskii
2019-02-26 6:27 ` Colin Baxter
2019-02-26 10:50 ` Basil L. Contovounesios
2019-02-26 12:19 ` Colin Baxter
2019-02-27 4:05 ` Richard Stallman
2019-02-27 16:33 ` Eli Zaretskii
2019-02-28 3:42 ` Richard Stallman
2019-02-28 6:53 ` Colin Baxter
2019-02-28 17:32 ` Eli Zaretskii [this message]
2019-03-02 3:28 ` Richard Stallman
2019-03-02 6:59 ` Eli Zaretskii
2019-03-03 3:01 ` Richard Stallman
2022-04-28 10:38 ` Lars Ingebrigtsen
2019-02-25 18:59 ` Vika Shleina
2019-02-24 19:27 ` Vika Shleina
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=83mumfkee9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34639@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=kisik21@fireburn.ru \
--cc=rms@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).