Re: Contributions to “Guile Studio”

Guile Studio is a great idea but If I had to make a wish it would be Mike Gran will continue to develop The Gano Project http://gano.sourceforge.net/ and from there someone would make some kind of https://en.wikipedia.org/wiki/Borland_Turbo_C

Re: Contributions to “Guile Studio”

I just want to say thank you to all the contributors! I'm trying to do some efforts to make Guile more friendly to newbies, guile-studio seems a good thing to help them to get a start. Best regards. On Tue, Oct 29, 2019 at 2:40 AM Ricardo Wurmus wrote: > > Hi Mark, > > I’m glad you consider th

Re: Contributions to “Guile Studio”

Hi Mark, I’m glad you consider this to be useful! >> Guile Studio is not supposed to be yet another pre-configured Emacs; its >> goal is just to provide a comfortable environment that works best for >> playing with Guile. I’d like to have less surprising window management, >> but I don’t know

Re: Contributions to “Guile Studio”

Hi Ricardo, Ricardo Wurmus writes: > some months ago I thought it would be neat if we had a simpler > environment for newcomers to play with Guile than to ask them to first > learn how to use Emacs. > > This is what made me play around with Emacs to build something called > “Guile Studio”. It a

Re: Contributions to Guile

Thanks everyone for your feedback. It gives a sense of what contributions would be welcome. There seems no clear consensus that there is anything on my list that is drop-dead important. There doesn't seem much desire to move beyond the current build system; while interesting, I'm not getting a s

Re: Contributions to Guile

Ricardo Wurmus skribis: > I couldn’t derive anything constructive from the reply. Indeed. :-) > Or are we talking about just changing the style for the Guile manual? No, all of the gendocs-using things. Well, at least we’ll try, if you can put up an example on-line. Ludo’.

Re: Contributions to Guile

Ludovic Courtès writes: > Could you look again at the feedback at > > and put up an example manual somewhere (thus not requiring Stylish)? We > can then lobby for the new CSS again. :-) The full relevant criticism/feedback

Re: Contributions to Guile

On Mon, Feb 8, 2016 at 4:28 PM, Chad Albers wrote: > On Mon, Feb 8, 2016 at 2:05 PM, Christopher Allan Webber > wrote: >> Ludovic Courtès writes: >> >>> Christopher Allan Webber skribis: >>> Chad Albers writes: >>> >>> [...] >>> > b. More robust documentation system - texinfo is not the

Re: Contributions to Guile

On Mon, Feb 8, 2016 at 2:05 PM, Christopher Allan Webber wrote: > Ludovic Courtès writes: > >> Christopher Allan Webber skribis: >> >>> Chad Albers writes: >> >> [...] >> b. More robust documentation system - texinfo is not the greatest. And it's non-trivial to generate any documentatio

Re: Contributions to Guile

Christopher Allan Webber skribis: > Ludovic Courtès writes: > >> Christopher Allan Webber skribis: >> >>> Chad Albers writes: >> >> [...] >> b. More robust documentation system - texinfo is not the greatest. And it's non-trivial to generate any documentation (including texinfo) for >>>

Re: Contributions to Guile

Ricardo Wurmus skribis: > Christopher Allan Webber writes: > If the html export was nicely themed >>> >>> It can be nicely themed. FWIW, Gnulib’s gendocs.sh, which is what most >>> projects use to export their HTML to gnu.org, now includes a CSS by >>> default (see

Re: Contributions to Guile

Christopher Allan Webber writes: >>> If the html export was nicely themed >> >> It can be nicely themed. FWIW, Gnulib’s gendocs.sh, which is what most >> projects use to export their HTML to gnu.org, now includes a CSS by >> default (see as an example.) We can >

Re: Contributions to Guile

Ludovic Courtès writes: > Christopher Allan Webber skribis: > >> Chad Albers writes: > > [...] > >>> b. More robust documentation system - texinfo is not the greatest. And >>> it's non-trivial to generate any documentation (including texinfo) for >>> modules. >> >> Texinfo is pretty nice to use i

Re: Contributions to Guile

Ludovic Courtès writes: > Christopher Allan Webber skribis: > >> Chad Albers writes: > > [...] > >>> b. More robust documentation system - texinfo is not the greatest. And >>> it's non-trivial to generate any documentation (including texinfo) for >>> modules. >> >> Texinfo is pretty nice to use i

Re: Contributions to Guile

Alex Sassmannshausen writes: > Mike Gerwitz writes: > >> On Sun, Feb 07, 2016 at 14:23:29 -0800, Christopher Allan Webber wrote: > > [...] > >>> In the meanwhile we've had some conversations about this, see David >>> Thompson's RFC on a Guile project generator: >>> >>> https://lists.gnu.org/arch

Re: Contributions to Guile

Mike Gerwitz writes: > On Sun, Feb 07, 2016 at 14:23:29 -0800, Christopher Allan Webber wrote: [...] >> In the meanwhile we've had some conversations about this, see David >> Thompson's RFC on a Guile project generator: >> >> https://lists.gnu.org/archive/html/guile-user/2015-09/msg00042.html

Re: Contributions to Guile

Christopher Allan Webber skribis: > Chad Albers writes: [...] >> b. More robust documentation system - texinfo is not the greatest. And >> it's non-trivial to generate any documentation (including texinfo) for >> modules. > > Texinfo is pretty nice to use if you're an emacs user... in fact, if

Re: Contributions to Guile

On Sun, Feb 07, 2016 at 14:23:29 -0800, Christopher Allan Webber wrote: > Texinfo is pretty nice to use if you're an emacs user... in fact, if > you're an emacs user, it's the best documentation reading system in the > world. But not everyone's an emacs user. It's also the required documentation

Re: Contributions to Guile

Chad Albers writes: > Hi Ludo, > > Thanks for getting back to me. I am most interested in remedying the > pain points that I have encountered while developing guile code. > > The pain points I experienced are the following: > > a. Simple reference guide. The guile manual is more of a guide than

Re: Contributions to Guile

Hi Ludo, Thanks for getting back to me. I am most interested in remedying the pain points that I have encountered while developing guile code. The pain points I experienced are the following: a. Simple reference guide. The guile manual is more of a guide than a reference...the best way to find

Re: Contributions to Guile

It is good to hear such announcements encouraged. I have often missed some ideas from Clojure and Racket in guile and recently had an idea to create a library that would bring those ideas in one place. I have defined macros that bring Clojure or Racket forms into the several projects I've used gui

Re: Contributions to Guile

Hi! Chad Albers skribis: > I have experience with several schemes: Racket, Chibli, Gauche, and Guile. > I've started to enjoy Guile the most. I've written one Guile module ( > https://github.com/neomantic/guile-beaglebone-io) and I'm about to release > another one (mailboxes queues for cross th