From: Colin Baxter <m43cap@yandex.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: , rms@gnu.org, 34639@debbugs.gnu.org, contovob@tcd.ie,
kisik21@fireburn.ru
Subject: bug#34639: 26.1; Custom themes break terminal when switching to org-mode
Date: Tue, 26 Feb 2019 06:27:19 +0000 [thread overview]
Message-ID: <875zt7m5dk.fsf@yandex.com> (raw)
In-Reply-To: <4780FCD2-DC65-412B-AC86-11F9FF2C4396@gnu.org> (Eli Zaretskii's message of "Tue, 26 Feb 2019 07:38:47 +0200")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> On February 26, 2019 6:55:32 AM GMT+02:00, Glenn Morris <rgm@gnu.org> wrote:
>> Eli Zaretskii wrote:
>>
>> > I left linum-mode not obsolete because some people might decide
>> not to > switch due to those differences. We should revisit this
>> issue a few > years from now, IMO.
>>
>> We already agreed to obsolete linum (which has two replacements)
>> years ago; https://debbugs.gnu.org/27622#37
> It's not in obsolete, is it?
May I put in a selfish plea to delay obsoleting 'linum-mode'. I use it
all the time. It's customised to my liking and I much prefer it to
'display-line-numbers-mode'. Perhaps, if I use 'linum-mode' extensively
then there may well be (many?) others who do likewise.
Best wishes,
--
Colin Baxter
m43cap@yandex.com
next prev parent reply other threads:[~2019-02-26 6:27 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 [this message]
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
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=875zt7m5dk.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=34639@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--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).