unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Zhiwei Chen <condy0919@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50331@debbugs.gnu.org, andlind@gmail.com
Subject: bug#50331: 28.0.50; Propose to obsolete cwarn.el
Date: Thu, 02 Sep 2021 16:51:52 +0800	[thread overview]
Message-ID: <871r67gy1j.fsf@gmail.com> (raw)
In-Reply-To: <83tuj3nzxy.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 02 Sep 2021 11:28:57 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Zhiwei Chen <condy0919@gmail.com>
>> Cc: 50331@debbugs.gnu.org,  andlind@gmail.com
>> Date: Thu, 02 Sep 2021 16:12:03 +0800
>> 
>> Why would I like to obsolete cwarn?
>> 
>> Actually, I'm making an introduction to Emacs builtin modes (in Chinese)
>> to see how powerful the vanilla Emacs is. But I found, Emacs is not so
>> orthogonal in functionality. e.g., `whitespace-mode' provides
>> `whitespace-cleanup' while simple.el has `delete-trailing-whitespace'.
>> Is it time to do subtraction for Emacs? There are too many packages
>> merged into Emacs, but a few are removed from Emacs (to elpa maybe).
>
> That's true, and one way we have for doing that is moving some stuff
> to GNU ELPA.  But that is WIP, and we didn't yet figure out how to
> move stuff to ELPA from core without punishing our users.  So we need
> to wait for that work to be completed before we can talk about making
> Emacs core thinner.
>
> In any case, obsoleting packages is not the right way of doing that,
> IMO: there's nothing obsolete in a package that offers some
> functionality which doesn't have a 1:1 replacement.

Thanks for the effort in Emacs.

> In a recent discussion on Reddit, it turned out many don't know about
> dabbrev.el as well, but I hope no one will propose to obsolete or
> remove it on those grounds.
>
> So I think we should not obsolete cwarn for now.

Got it, Emacs developers have already been working on that.

-- 
Zhiwei Chen





  reply	other threads:[~2021-09-02  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02  6:30 bug#50331: 28.0.50; Propose to obsolete cwarn.el Zhiwei Chen
2021-09-02  7:27 ` Eli Zaretskii
2021-09-02  8:12   ` Zhiwei Chen
2021-09-02  8:28     ` Eli Zaretskii
2021-09-02  8:51       ` Zhiwei Chen [this message]
2021-09-02 11:10 ` Anders Lindgren
2021-09-02 16:12   ` Lars Ingebrigtsen
2021-09-03  6:18 ` bug#50331: [Anders Lindgren] " Zhiwei Chen

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=871r67gy1j.fsf@gmail.com \
    --to=condy0919@gmail.com \
    --cc=50331@debbugs.gnu.org \
    --cc=andlind@gmail.com \
    --cc=eliz@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).