unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Is there REPL for Bash?
Date: Sat, 28 Dec 2024 08:19:02 +0100	[thread overview]
Message-ID: <Z2+mZvbcBd7uv9LR@tuxteam.de> (raw)
In-Reply-To: <861pxsbzvq.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

On Sat, Dec 28, 2024 at 08:05:29AM +1100, Joel Reicher wrote:
> Jean Louis <bugs@gnu.support> writes:
> 
> > * Joel Reicher <joel.reicher@gmail.com> [2024-12-27 17:18]:
> > > Jean Louis <bugs@gnu.support> writes:
> > > 
> > > > I wonder if there is some REPL for Bash, so that I can write and
> > > > evaluate shell script and see it evaluated in the side window?
> > > 
> > > Bash itself is the REPL for bash.
> > 
> > Sure, I was thinking I could edit a file in one buffer and easily
> > evaluate it in a new shell related to that buffer and file, watching it
> > on the side. 💡📝💻🔍
> 
> If you're editing foo.sh You could do M-x compile and enter something like
> "bash foo.sh" for the compilation. That will achieve this effect as long as
> the script does not require interactive input.
> 
> But this is not what a REPL is, so I'm a bit confused why you say you want a
> REPL (and also don't want to use the one that already exists).

I think the OP has been using REPL in some extension of the original sense.
Strictly speaking, the bash /is/ primarily a REPL (read-evaluate-print loop).
All shells were born for that.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2024-12-28  7:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27  9:26 Is there REPL for Bash? Jean Louis
2024-12-27 14:17 ` Joel Reicher
2024-12-27 16:14   ` Jean Louis
2024-12-27 21:05     ` Joel Reicher
2024-12-28  7:19       ` tomas [this message]
2024-12-28 13:28       ` Jean Louis
2024-12-28 13:47       ` Jean Louis
2024-12-27 14:36 ` Eduardo Ochs
2024-12-27 16:16   ` Jean Louis

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/emacs/

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

  git send-email \
    --in-reply-to=Z2+mZvbcBd7uv9LR@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    /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).