From: Mike Gran <spk121@yahoo.com>
To: Christine Lemmer-Webber <cwebber@dustycloud.org>,
"tomas@tuxteam.de" <tomas@tuxteam.de>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Guile outside of Emacs + Geiser
Date: Thu, 28 Sep 2023 12:01:50 +0000 (UTC) [thread overview]
Message-ID: <1343676524.4347173.1695902510641@mail.yahoo.com> (raw)
In-Reply-To: <ZRUpN7O/Dzclkfm1@tuxteam.de>
On Thursday, September 28, 2023 at 12:20:58 AM PDT, <tomas@tuxteam.de> wrote:
> On Wed, Sep 27, 2023 at 03:07:10PM -0400, Christine Lemmer-Webber wrote:
>> There's a long thread on guix-devel which is related and touches on many
>> things, but I thought I'd narrow in on this one thing.
>>
>> Has anyone had a "good" experience programming with Guile without using
>> Emacs? If so, what was your development experience like?
> For one exotic datapoint: I do use Emacs as an editor (almost exclusively)
> but never got the hang of Geiser. So I'm happy as a clam with Guile's
> REPL in a plain & simple terminal.
I also use emacs but not geiser. And I only use emacs because of the auto-indentation
and tab-to-indent.
I've often used VSCode for other things, but, I never got indent of scheme to
be identical to emacs.
I once tried to write a graphical debugger in Gtk for Guile, but, gave up.
Like often happens, a fun idea ended up being real work.
Regards,
Mike Gran
next prev parent reply other threads:[~2023-09-28 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 19:07 Guile outside of Emacs + Geiser Christine Lemmer-Webber
2023-09-27 19:47 ` Ricardo G. Herdt
2023-09-30 12:42 ` Christine Lemmer-Webber
2023-09-30 17:24 ` defn(life()) via General Guile related discussions
2023-09-27 19:48 ` Luis Felipe
2023-09-28 7:20 ` tomas
2023-09-28 12:01 ` Mike Gran [this message]
2023-09-28 12:23 ` Maxime Devos
2023-10-13 13:38 ` Simon Tournier
2023-10-16 19:41 ` Christine Lemmer-Webber
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=1343676524.4347173.1695902510641@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
--cc=tomas@tuxteam.de \
/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).