emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Felipe Lema <felipelema@mortemale.org>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Report error in scheme evaluation
Date: Wed, 22 Dec 2021 02:27:57 -0300	[thread overview]
Message-ID: <10672089.j3G5Rs59A6@felipe-thinkpad-x200> (raw)
In-Reply-To: <m27dbxy2ui.fsf@me.com>

On Tuesday, 21 December 2021 20.07.01 -03 Rudolf Adamkovič wrote:
> Felipe Lema <felipelema@mortemale.org> writes:
> > Sup, y'all
> >
> > I started using guile with Org Babel […]
> Sup! I plan to write some literate Scheme soon as well.  How do you find
> the experience so far?  As of today, I use 'scheme-mode' with a set of
> TAGS files for completion and help, all based on my (incomplete) notes
> about R7RS.  Org requires Geiser to run Scheme, from what I gather.
> Also, do Org bugs cause any issues when writing literate Scheme?  Thanks
> in advance for any insights.  Cheers!
> Rudy
Hey, Rudy

I think this was not clear, but just in case: this patch is not a bugfix. I just thought having an error buffer just like with Python is a good idea (specially since I'm relatively new to Guile). I also believe that fine-tuning a workflow with libre softweare through can be considered an improvement and, thus, should be shared for others to use.

For anyone interested about my Org + Babel + GNU Guile flow, read below.

I think the experience is good if you're not picky. This is my opinion for Emacs workflows in general. At the same time, I'd say it takes some resources (mainly time) to get things running comfortably.

Some context ahead. I'm using Org for Get Things Done workflows in which I basically log a shell session (you may think of it as data processing on text files too: grep, awk sed... but logged and reproducible). Because of my everyday job, I need to switch context several times within a week and I find it helpful to use Org for two reasons: 1) When I write stuff myself (describing stuff in Org file) I find it easier to remember 2) If I cannot remember, I can grep for similar text / tags.

I'm trying GNU Guile as scripting language because... well, for one, that is its purpose. And two, because I've mostly discarded other languages as being too costly (too slow, too much needs to be done...).

I'd say that geiser transforms Emacs into a full blown IDE: code completion, documentation, symbol/tag search... you name it. This also applies to Org when you edit the source code using C-c C-c, so that helps a ton with learning the language.

Hope this helps. You can contact me privately if you want to follow up.


  reply	other threads:[~2021-12-22  5:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 19:58 Report error in scheme evaluation Felipe Lema
2021-12-21 23:07 ` Rudolf Adamkovič
2021-12-22  5:27   ` Felipe Lema [this message]
2021-12-23 21:01     ` Rudolf Adamkovič
2021-12-22 14:54 ` Ihor Radchenko
2021-12-22 16:56   ` Felipe Lema
2021-12-22 14:58 ` Ihor Radchenko
2021-12-22 16:34 ` Max Nikulin
2021-12-22 17:04   ` Ihor Radchenko
2022-09-12 11:27 ` Ihor Radchenko
2021-12-28  1:03 Felipe Lema
2022-04-30  8:11 ` Ihor Radchenko
2022-04-30 10:35   ` Neil Jerram
2022-05-04  2:52     ` Felipe Lema

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10672089.j3G5Rs59A6@felipe-thinkpad-x200 \
    --to=felipelema@mortemale.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=salutis@me.com \


* 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 public inbox


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).