all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
To: 48530@debbugs.gnu.org
Subject: bug#48530: Guile Mode
Date: Thu, 20 May 2021 10:57:11 +0200	[thread overview]
Message-ID: <e1dddaccec04213a685bd5f3a701bdabda0903d0.camel@korwin-zmijowski.fr> (raw)


Dear Emacs team,

I am Jérémy, an Emacs and Guile user. I came to discover both in the
same time about three years ago.
I am not a member of the GNU project, nor FSF. I'm just a GNU
enthousiast.

When I edit Guile code in Emacs, I rely mostly on :
Scheme mode + Geiser + Paredit + Autocomplete/Company + Projectile +
Magit

Then come other extensions.

I am writing to you today to start a conversation (hopefully a work)
around a kind of "Guile mode" (why not something with IDE
capabilities). I remember Eli incentivizing people to do so on Guile
user mailing list.

I don't know the spirit and the boundaries of the Emacs project.
Here is a list of things that I would like to be able to do in Emacs
while writing Guile code.
(I would like to know if there are things that fit to the scope of your
project ? For the ones that do not, I will contact the relevant
stakeholders.)

- take in charge the support of Geiser for Guile ?
- provide features to "refactor" Guile code (i.e extract a
value/procedure into a local/top-level define or let expression, toogle
a variable to be private or public, change procedure signature and
propagate change, move to another file/module and auto-import it) ?
- auto import Guile modules according to unbound variables ?
- instrument the code (set and stepover breakpoints)

Thank you,
Jérémy






             reply	other threads:[~2021-05-20  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  8:57 Jérémy Korwin-Zmijowski [this message]
2021-05-20 15:07 ` bug#48530: Guile Mode Jose A. Ortega Ruiz
2021-05-21  6:59 ` Eli Zaretskii
2022-07-13 12:05 ` Lars Ingebrigtsen

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=e1dddaccec04213a685bd5f3a701bdabda0903d0.camel@korwin-zmijowski.fr \
    --to=jeremy@korwin-zmijowski.fr \
    --cc=48530@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 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.