From: sirgazil <sirgazil@zoho.com>
To: "Ricardo Wurmus" <rekado@elephly.net>
Cc: "Matt Wette" <matt.wette@gmail.com>, "guile-user" <guile-user@gnu.org>
Subject: Re: Geiser vs. guile-mode?
Date: Thu, 20 Feb 2020 09:24:16 -0500 [thread overview]
Message-ID: <17062fc23de.1018aff9f2171.7728684452987111137@zoho.com> (raw)
In-Reply-To: <87pneall19.fsf@elephly.net>
---- On Wed, 19 Feb 2020 09:16:34 -0500 Ricardo Wurmus <rekado@elephly.net> wrote ----
>
> sirgazil <sirgazil@zoho.com> writes:
>
> > I also find some fundamental things missing when programming in Guile Scheme (with Emacs+Geiser):
> >
> > 1. On-the-fly syntax checking (see flycheck)
>
> This is available by default in “Guile Studio”[1]. It works by compiling
> the buffer:
>
> --8<---------------cut here---------------start------------->8---
> (require 'flycheck)
> (flycheck-define-checker guile
> "A Guile syntax checker with `guild compile'."
> :command ("guild" "compile" "--to=cps"
> "--warn=unused-variable"
> "--warn=unused-toplevel"
> "--warn=unbound-variable"
> "--warn=macro-use-before-definition"
> "--warn=arity-mismatch"
> "--warn=duplicate-case-datum"
> "--warn=bad-case-datum"
> "--warn=format"
> source)
> :predicate
> (lambda ()
> (and (boundp 'geiser-impl--implementation)
> (eq geiser-impl--implementation 'guile)))
> :verify
> (lambda (checker)
> (let ((geiser-impl (bound-and-true-p geiser-impl--implementation)))
> (list
> (flycheck-verification-result-new
> :label "Geiser Implementation"
> :message (cond
> ((eq geiser-impl 'guile) "Guile")
> (geiser-impl (format "Other: %s" geiser-impl))
> (t "Geiser not active"))
> :face (cond
> ((or (eq geiser-impl 'guile)) 'success)
> (t '(bold error)))))))
> :error-patterns
> ((warning
> line-start (file-name) ":" line ":" column ": warning:" (message) line-end)
> (error
> line-start (file-name) ":" line ":" column ":" (message) line-end))
> :modes (scheme-mode geiser-mode))
> (add-to-list 'flycheck-checkers 'guile)
> (global-flycheck-mode 1)
> --8<---------------cut here---------------end--------------->8---
Thanks, Ricardo :)
Any reason why this checker is not integrated into Flycheck? Currently, the only supported Scheme in Flycheck is Chikken...
next prev parent reply other threads:[~2020-02-20 14:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:18 Geiser vs. guile-mode? Pierre Neidhardt
2020-02-04 16:16 ` Jérémy Korwin-Zmijowski
2020-02-04 16:40 ` Pierre Neidhardt
2020-02-07 13:50 ` Pierre Neidhardt
2020-02-07 16:19 ` Jérémy Korwin-Zmijowski
2020-02-07 16:30 ` Matt Wette
2020-02-07 17:50 ` sirgazil
2020-02-07 22:24 ` Matt Wette
2020-02-08 18:14 ` Ricardo Wurmus
2020-02-08 18:59 ` Matt Wette
[not found] ` <F5513F8F-F6A8-4AAC-8AF3-C91991CE8E40@korwin-zmijowski.fr>
2020-02-13 9:38 ` Jérémy Korwin-Zmijowski
2020-02-18 23:53 ` sirgazil
2020-02-19 14:16 ` Ricardo Wurmus
2020-02-20 14:24 ` sirgazil [this message]
2020-02-20 22:50 ` Jose A. Ortega Ruiz
2020-02-21 0:01 ` sirgazil
2020-02-21 1:44 ` Jose A. Ortega Ruiz
2020-02-21 8:41 ` Arne Babenhauserheide
2020-02-21 22:57 ` Jose A. Ortega Ruiz
2020-02-08 16:30 ` Pierre Neidhardt
2020-02-07 23:44 ` Jose A. Ortega Ruiz
2020-02-14 8:38 ` Pierre Neidhardt
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17062fc23de.1018aff9f2171.7728684452987111137@zoho.com \
--to=sirgazil@zoho.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
--cc=rekado@elephly.net \
/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.
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).