all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@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: Fri, 01 Mar 2019 22:28:27 -0500	[thread overview]
Message-ID: <E1gzvK7-00024r-3h@fencepost.gnu.org> (raw)
In-Reply-To: <83mumfkee9.fsf@gnu.org> (message from Eli Zaretskii on Thu, 28 Feb 2019 19:32:14 +0200)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > 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.

Why is it better if people use the display margins via
linum (not core) rather than by an option in native line numbers?
I don't see that it makes much difference to the issues of
future maintenance.

What happens if two features try to use the display margins?
What does the interference look like?  I suppose they can't both work
properly, but does it cause anything worse than that?


-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  reply	other threads:[~2019-03-02  3:28 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
2019-03-02  3:28                                       ` Richard Stallman [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1gzvK7-00024r-3h@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=34639@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=eliz@gnu.org \
    --cc=kisik21@fireburn.ru \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.