From: Nala Ginrut <nalaginrut@gmail.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [Proposal] Why not add a "shell" procedure?
Date: Sun, 13 May 2012 23:04:18 +0800 [thread overview]
Message-ID: <CAPjoZodCZFczh3PHw0tOBX1tV=oPDomKtU7tOkT_aiLUCGRxTQ@mail.gmail.com> (raw)
In-Reply-To: <87wr4hscm8.fsf@gnuvola.org>
Hmm..."pwd" and "sed" are just examples I showed how convenient this
"shell" could be.
But I missed "pwd" should be implemented by "getcwd".
Anyway, my aim is not to implement "pwd" or "sed", but the "shell"
alike in Ruby.
On Sat, May 12, 2012 at 10:22 PM, Thien-Thi Nguyen <ttn@gnuvola.org> wrote:
> () Nala Ginrut <nalaginrut@gmail.com>
> () Sat, 12 May 2012 20:30:21 +0800
>
> (pwd)
> ==> "/home/nalaginrut/Project/gnulib-20100109+stable"
>
> Any comment?
>
> For this particular case, you can use instead ‘getcwd’, which
> is builtin. See also ‘shell-command->string’ and friends:
>
> http://www.gnuvola.org/software/ttn-do/ttn-do.html.gz
>
> Tangentially, Guile 1.4.x has "guile-tools gxsed", a sed
> implementation in Scheme:
>
> http://www.gnuvola.org/software/guile/doc/guile_002dtools-gxsed.html
>
> It needs some work to be compatible w/ Guile 1.8 and 2.0
> (i.e., to use 2-arg ‘eval’), but the core transform is sound.
> IIRC it PASSed around 60% of the GNU sed 4.2 "make check".
>
> For Emacsoid in-process editing, see also module (ttn-do mogrify),
> also in ttn-do. I (and my daemons) use it every day w/ Guile 1.8.
next prev parent reply other threads:[~2012-05-13 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 12:30 [Proposal] Why not add a "shell" procedure? Nala Ginrut
2012-05-12 12:35 ` Nala Ginrut
2012-05-12 14:22 ` Thien-Thi Nguyen
2012-05-13 15:04 ` Nala Ginrut [this message]
2012-05-13 18:29 ` Mark H Weaver
2012-05-14 0:17 ` Nala Ginrut
-- strict thread matches above, loose matches on Subject: below --
2012-05-12 14:37 Nelson H. F. Beebe
2012-05-13 15:08 ` Nala Ginrut
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPjoZodCZFczh3PHw0tOBX1tV=oPDomKtU7tOkT_aiLUCGRxTQ@mail.gmail.com' \
--to=nalaginrut@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ttn@gnuvola.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).