From: Tom Fitzhenry <tom@tom-fitzhenry.me.uk>
To: 51585@debbugs.gnu.org
Subject: [bug#51585] [PATCH] gnu: Add emacs-flymake-flycheck.
Date: Thu, 4 Nov 2021 01:02:22 +1100 [thread overview]
Message-ID: <c3e95e7f-5a29-b748-b5ae-64f9781f10cf@tom-fitzhenry.me.uk> (raw)
* gnu/packages/emacs-xyz.scm (emacs-flymake-flycheck): New variable.
---
gnu/packages/emacs-xyz.scm | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 543ce6303a..8253d7d562 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -1586,6 +1586,29 @@ (define-public emacs-flycheck
provides an optional IDE-like error list.")
(license license:gpl3+)))) ;+GFDLv1.3+ for
the manual
+(define-public emacs-flymake-flycheck
+ (package
+ (name "emacs-flymake-flycheck")
+ (version "20210404.2128")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (string-append
+ "https://melpa.org/packages/flymake-flycheck-"
+ version
+ ".el"))
+ (sha256
+ (base32 "1m59ahd5gjlfwf328labwdlpcxh8ywywkwgfrlsy5jyxfc9ss4nv"))))
+ (build-system emacs-build-system)
+ (propagated-inputs `(("emacs-flycheck" ,emacs-flycheck)))
+ (home-page "https://github.com/purcell/flymake-flycheck")
+ (synopsis "Use flycheck checkers as flymake backends")
+ (description
+ "This package provides support for running any flycheck checker as a
+flymake diagnostic backend. The effect is that flymake will
+control when the checker runs, and flymake will receive its errors.")
+ (license license:gpl3)))
+
(define-public emacs-flymake-quickdef
;; This particular commit includes bug fixes on top of 1.0.0 release.
(let ((version "1.0.0")
--
2.33.1
next reply other threads:[~2021-11-03 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 14:02 Tom Fitzhenry [this message]
2021-11-12 22:51 ` bug#51585: [PATCH] gnu: Add emacs-flymake-flycheck Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3e95e7f-5a29-b748-b5ae-64f9781f10cf@tom-fitzhenry.me.uk \
--to=tom@tom-fitzhenry.me.uk \
--cc=51585@debbugs.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/guix.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).