From: sirgazil <sirgazil@zoho.com>
To: "Matt Wette" <matt.wette@gmail.com>
Cc: "guile-user" <guile-user@gnu.org>
Subject: Re: Geiser vs. guile-mode?
Date: Tue, 18 Feb 2020 18:53:21 -0500 [thread overview]
Message-ID: <1705ab86de0.124b9a35210423.8624681576554917312@zoho.com> (raw)
In-Reply-To: <17020c6ae18.bf06ef5b71547.6717873688020963681@zoho.com>
I also find some fundamental things missing when programming in Guile Scheme (with Emacs+Geiser):
1. On-the-fly syntax checking (see flycheck)
2. Immediate availability of new symbols after importing a module.
Without (1) I don't get alerted about modules imported but not used, symbols used but not defined, ... These would have helped me when writing my first Guix packages, where I copy/pasted inputs from other package definitions without importing the modules they were defined in, or when I deleted inputs I didn't need but left their corresponding modules around.
Without (2) I have to evaluate the buffer manually so that I have autocomplete, autodoc, go to definition, etc., for the symbols defined in the imported modules.
I get these two features when I install emacs-elpy, an "Emacs Python Development Environment". I expected to have them too when I installed Geiser, the "Emacs environment to hack in Scheme".
---
https://sirgazil.bitbucket.io/
next prev parent reply other threads:[~2020-02-18 23:53 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 [this message]
2020-02-19 14:16 ` Ricardo Wurmus
2020-02-20 14:24 ` sirgazil
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=1705ab86de0.124b9a35210423.8624681576554917312@zoho.com \
--to=sirgazil@zoho.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).