emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel Forth
Date: Tue, 28 Jan 2025 18:37:45 +0000	[thread overview]
Message-ID: <87jzaeaio6.fsf@localhost> (raw)
In-Reply-To: <87y0z112w9.fsf@tsdye.online>

"Thomas S. Dye" <tsd@tsdye.online> writes:

> I pushed Forth documentation to the Worg repo,

Thanks!
I have 2 comments:

> +Babel evaluates Forth code blocks in an inferior Forth process.
> +You can start an inferior Forth process with =M-x run-forth=.

Does it mean that users _must_ run M-x run-forth? Otherwise, I am not
sure why this paragraph is present.

> +#+begin_example
> +,#+begin_src forth :exports both
> +." Hello World!"
> +,#+end_src
> +#+end_example
> +
> +#+begin_src forth :exports both
> +." Hello World!"

This will export into 3! snippets. I feel that
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-forth.html
is confusing. Maybe we just put both the code and result into verbatim
example, as in
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-shell.html

> ...but saw a build 
> error that I don't know how to fix.

Savannah was under DDoS making our WORG build script fail when it
attempted to clone org-mode git repo. Should be OK now, AFAIK.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2025-01-28 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 20:41 Babel Forth Thomas S. Dye
2025-01-23  8:16 ` Joost Kremers
2025-01-23  8:22   ` Joost Kremers
2025-01-23 18:36   ` Thomas S. Dye
2025-01-23 19:13     ` Ihor Radchenko
2025-01-23 19:29 ` Ihor Radchenko
2025-01-23 20:05   ` Thomas S. Dye
2025-01-24  0:17   ` Thomas S. Dye
2025-01-28 18:37     ` Ihor Radchenko [this message]
2025-01-28 19:48       ` Thomas S. Dye

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87jzaeaio6.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.online \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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