all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 44171@debbugs.gnu.org
Subject: bug#44171: Make cwarn.el obsolete
Date: Fri, 23 Oct 2020 16:03:06 +0300	[thread overview]
Message-ID: <835z71jdrp.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmRrAscQqXQzxBe7Ndpsx-oJqvwZX0nyNQn2kOrcJaq8w@mail.gmail.com> (message from Stefan Kangas on Fri, 23 Oct 2020 12:12:49 +0000)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 23 Oct 2020 12:12:49 +0000
> Cc: 44171@debbugs.gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> This was written in 1999, but is it useful today?
> >
> > I'm still using it, and it sometimes shows mistakes I'm about to make.
> > Are there any alternatives that highlight such suspicious constructs?
> 
> I was under the impression that flymake was such a replacement?

Flymake is a much larger package which affects the workflow in many
ways.  Telling people to use Flymake when all they need is what
cwarn.el provides would be like deprecating Outline mode because we
have Org, for example.

I thought CC mode could have something similar.  Or maybe there's a
way of adding to CC mode a similar feature, then we could retire
cwarn.el.

> To be clear, I'm not on a quest to remove actually useful features.  I
> just stumbled across cwarn.el while looking for stuff that need tests
> and/or should be converted to lexical-binding.

I'm very happy with its functionality, FWIW.  Thank you for taking
care of it.





  reply	other threads:[~2020-10-23 13:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 10:53 bug#44171: Make cwarn.el obsolete Stefan Kangas
2020-10-23 11:14 ` Eli Zaretskii
2020-10-23 12:12   ` Stefan Kangas
2020-10-23 13:03     ` Eli Zaretskii [this message]
2020-10-23 13:20       ` Stefan Kangas

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=835z71jdrp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44171@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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.