GNU bug report logs - #34639
26.1; Custom themes break terminal when switching to org-mode

Previous Next

Package: emacs;

Reported by: Vika Shleina <kisik21 <at> fireburn.ru>

Date: Sun, 24 Feb 2019 17:58:01 UTC

Severity: normal

Found in version 26.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: rms <at> gnu.org
Cc: contovob <at> tcd.ie, kisik21 <at> fireburn.ru, 34639 <at> debbugs.gnu.org
Subject: bug#34639: 26.1; Custom themes break terminal when switching to org-mode
Date: Sat, 02 Mar 2019 08:59:02 +0200
> From: Richard Stallman <rms <at> gnu.org>
> Cc: contovob <at> tcd.ie, kisik21 <at> fireburn.ru, 34639 <at> debbugs.gnu.org
> Date: Fri, 01 Mar 2019 22:28:27 -0500
> 
> 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.

It makes a difference because we can tell them to drop linum if they
have problems with display margins.  And because we don't have to deal
with bug reports about such conflicts.

> What happens if two features try to use the display margins?

You have a mess in the display margin area.  Even the size of the
margin can change unpredictably, because each feature changes it
according to its own logic.

> What does the interference look like?  I suppose they can't both work
> properly, but does it cause anything worse than that?

What can be worse in a real-time editor than a messed-up display?




This bug report was last modified 3 years and 21 days ago.

Previous Next


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