[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Another Emacs incompatibilty
From: |
Emanuel Berg |
Subject: |
Re: Another Emacs incompatibilty |
Date: |
Mon, 17 Aug 2020 23:22:42 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Stefan Monnier wrote:
> So the only really safe way to avoid introducing
> new problems is to leave the code 100% unchanged.
Fixing one bug can introduce another bug. But to be
fair, I think everyone understands that, and no one
suggests the code should never change one ... bit.
I'm an "under the hood maximalist" myself. As long as
I can configure the interface [see dump 1] to be
minimalist and clutter free I don't mind having all
kinds of huge software libraries below, invisible.
They might come handy one day and until then they
don't bother anyone.
[1] https://dataswamp.org/~incal/pimgs/comp/mail.png
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
- Re: Another Emacs incompatibilty, (continued)
- Re: Another Emacs incompatibilty, Torbjörn Granlund, 2020/08/17
- Re: Another Emacs incompatibilty, Robert Pluim, 2020/08/17
- Re: Another Emacs incompatibilty, Eli Zaretskii, 2020/08/17
- Re: Another Emacs incompatibilty, Torbjörn Granlund, 2020/08/17
- Re: Another Emacs incompatibilty, Stefan Monnier, 2020/08/17
- Re: Another Emacs incompatibilty,
Emanuel Berg <=
- Re: Another Emacs incompatibilty, Gregory Heytings, 2020/08/17
- Re: Another Emacs incompatibilty, Eric Abrahamsen, 2020/08/17
- Re: Another Emacs incompatibilty, Emanuel Berg, 2020/08/17
- Re: Another Emacs incompatibilty, Eric Abrahamsen, 2020/08/17
- Re: Another Emacs incompatibilty, Stefan Monnier, 2020/08/18
- Re: Another Emacs incompatibilty, Eli Zaretskii, 2020/08/18
- Re: Another Emacs incompatibilty, Emanuel Berg, 2020/08/18
- Re: Another Emacs incompatibilty, Eli Zaretskii, 2020/08/18
- Re: Another Emacs incompatibilty, Emanuel Berg, 2020/08/23
- Re: Another Emacs incompatibilty, Alan Davis, 2020/08/24