guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guile Studio's goals (and home)


From: Eli Zaretskii
Subject: Re: Guile Studio's goals (and home)
Date: Tue, 25 Feb 2020 12:30:26 +0200

> From: Ricardo Wurmus <address@hidden>
> Date: Tue, 25 Feb 2020 10:12:31 +0100
> Cc: address@hidden
> 
> The pretentiously named “Guile Studio” arose from the observation that
> we often tell new Guile users to learn how to use Emacs first in order
> to get a comfortable Guile development experience.  Since Emacs has
> really quirky defaults that don’t mesh with the expectations of people
> who learn a new programming language, this can be so discouraging
> that the person abandons the initial goal of learning Guile.
> 
> Many people in the past had the idea to “fix” Emacs.  “Guile Studio” is
> not intended to be yet another Emacs starter kit like Prelude, Doom, or
> Spacemacs.  Instead it tries to focus on just Guile, going as far as to
> remove “Emacs” from the window title and the menus.
> 
> My goal was to provide a friendly editor that does not require any
> configuration to use and play with Guile.  You install Guile Studio and
> get started right away.  It tries to be what Dr Racket is for Racket and
> what RStudio is for R.
> 
> This is why Guile Studio comes with the picture language and immediately
> spawns a Geiser session where it can be used.  It hides Emacs clutter
> from the menus and adds menu items that are relevant to new Guile users,
> such as a link to the Guile manual.  It aims to handle documentation
> buffers specially to avoid the confusion that comes with Emacs-typical
> “buffer clutter”.  It uses CUA key bindings to avoid annoying surprises.

As an Emacs co-maintainer, I was quite surprised to read the above,
since AFAIK none of these issues were ever communicated to the Emacs
developers.  If they were reported (using the Emacs built-in
bug-reporting command), I'm quite sure we would be very attentive to
such reports and amenable to adding/tweaking features so as to make
Emacs a better basis for Guile use and development.  After all, GNU
projects should help each other.

So I urge you to report the problems on which you hint above, and
suggest changes or improvements that would remove at least some of the
need to tweak Emacs for being a "Guile Studio".

TIA



reply via email to

[Prev in Thread] Current Thread [Next in Thread]