From: "Роман Зайруллин" <krosenmann@gmail.com>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Automatic refactoring of Guile code
Date: Sat, 20 Apr 2019 13:21:42 +0300 [thread overview]
Message-ID: <CA+GxJ_FTM9Zqpo-eq8groaVwwnpJvwRCcxz7iqgk7swEOU+dmA@mail.gmail.com> (raw)
In-Reply-To: <D18CFF23-6EE3-4028-8FBD-09EAF47BDD77@korwin-zmijowski.fr>
Hello!
Wilfred made the refactor browser some time ago. It can only extract
variable and function now, but this browser is easily extensible. I will
add some extra tasks in a few months to it when will be working for
refactoring part of my current research of legacy software support technics.
https://github.com/Wilfred/emacs-refactor#user-content-scheme
пн, 8 апр. 2019 г. в 21:58, Jérémy Korwin-Zmijowski <
jeremy@korwin-zmijowski.fr>:
> Hello !
>
> I am curious about answers too!
> I use Paredit for small actions. I am trying Parinfer in combination.
> I looked for refactoring packages for Emacs which provide extracting
> facilities like extract let context or extract function, ... Maybe it is
> something we can work on for Guile ?
> With people interested in the challenge ?
>
> Jeko
>
> Le 8 avril 2019 18:54:07 GMT+02:00, sirgazil <sirgazil@zoho.com> a écrit :
> >Hello,
> >
> >I'm looking for tools to do common automatic refactoring in Emacs.
> >Would
> >you mind sharing what you currently use?
> >
> >
> >--
> >Luis Felipe López Acevedo
> >http://sirgazil.bitbucket.io/
>
> --
> Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma
> brièveté.
>
next prev parent reply other threads:[~2019-04-20 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 16:54 Automatic refactoring of Guile code sirgazil
2019-04-08 18:57 ` Jérémy Korwin-Zmijowski
2019-04-20 10:21 ` Роман Зайруллин [this message]
2019-04-20 16:05 ` sirgazil
2019-04-20 16:41 ` Роман Зайруллин
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=CA+GxJ_FTM9Zqpo-eq8groaVwwnpJvwRCcxz7iqgk7swEOU+dmA@mail.gmail.com \
--to=krosenmann@gmail.com \
--cc=guile-user@gnu.org \
--cc=jeremy@korwin-zmijowski.fr \
/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).