From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: formido <formido@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Bash Script Editing Mode?
Date: Thu, 07 Aug 2008 22:53:58 +0200 [thread overview]
Message-ID: <489B60E6.8020402@gmail.com> (raw)
In-Reply-To: <361d08d2-b456-49c9-a578-53d1aaaf0b0f@a8g2000prf.googlegroups.com>
formido wrote:
> There's a shell mode, but it has a prompt and doesn't help you
> incrementally create a shell script as efficiently as it could, unless
> I'm missing something. Is there any shell script mode that works more
> like the elisp, python, or erlang repls, where you can execute your
> choice of several lines at once and you can go back and edit and
> execute the lines in situ? If I write a bash function, editing and
> reloading the function is a painful process. I'm looking for something
> a little bit like the Mac's BBEdit shell worksheets (only better).
>
> I considered altering the usual shell mode, but it would take more
> than slight edits, so I'm hoping something's already out there. For
> example, one should be able to go back to a function, tweak it, and
> reload with a minimum of keyboard fuss.
You can search for available commands from the help menu. Major modes
are commands so you can use the menu entry
Help
Search Documentation
Find Commands by Name
I guessed that such a major mode would match
^sh.*-mode$
and found some that might help you (I am not sure).
next prev parent reply other threads:[~2008-08-07 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 20:21 Bash Script Editing Mode? formido
2008-08-07 20:49 ` Mike Treseler
2008-08-07 22:10 ` formido
2008-08-07 20:53 ` Lennart Borgman (gmail) [this message]
2008-08-07 21:06 ` Thierry Volpiatto
2008-08-07 21:20 ` Pascal J. Bourguignon
2008-08-07 21:59 ` formido
[not found] ` <mailman.16033.1218143342.18990.help-gnu-emacs@gnu.org>
2008-08-07 22:01 ` formido
[not found] ` <mailman.16028.1218142452.18990.help-gnu-emacs@gnu.org>
2008-08-07 22:03 ` formido
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=489B60E6.8020402@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=formido@gmail.com \
--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).