From: Buggs <buggs-rc@splashground.de>
To: Tim Goodwin <tjg@star.le.ac.uk>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Beta release rc-1.6b3 available
Date: Wed, 17 Oct 2001 16:13:12 -0500 [thread overview]
Message-ID: <20011017222058.16189.qmail@mail.splashground.de> (raw)
In-Reply-To: <20011017133445.9850.qmail@happy.star.le.ac.uk>
On Wednesday 17 October 2001 15:34, Tim Goodwin wrote:
> > Suse Linux 7.2 with a CVS gcc-3.1 from last week does fine.
>
> Thanks for the report. (Keep 'em coming, folks!)
Your welcome. I migth be able to provide a few others next week.
> > But there are some issues, not version dependant, that I don't
> > understand. This will get out of control:
> >
> > ; fn l {ls -l $*}
> > ; fn l {l -a $*}
> > ; l
>
> Your function `l' always calls itself recursively, so it rapidly runs
> out of stack.
Thougth so.
> Remember that, unlike other shells, rc is not a macro processor. In
> particular, the `l' in the function body of your second definition is
> *not* expanded using the previous definition of `fn l'. (You can
> always use `whatis' to see the current definition of a function.)
So my old definition is lost and it constantly calls itself.
> A simple
>
> fn l { ls -la $* }
>
> is probably what you want.
Yes, probably. But I also wondered about the why of the failure and
why I did not receive a warning (could have been a bug after all).
[...]
> > And what about job control, how do I handle that?
>
> This shell does not have job control.
>
> It has been said (by Duff? Pike? Rakitzis? I forget...) that job
> control adds a deal of complexity to handle just the easy part of a
> hard problem. The suggested alternative in a windowing environment is
> to open a new window.
I see. That was exactly what I wanted to know, thanks.
> If you're not in a windowing environment, you might like the `screen'
> program, which does both the easy and hard parts of the problem.
> There's also a "tabbed" version of gnome-terminal around, called
> `multignometerm'.
Never used multignometerm but that is the way KDE's konsole takes,
which I can also recommend.
Thanks again,
Buggs
next prev parent reply other threads:[~2001-10-18 5:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 13:56 Tim Goodwin
2001-10-17 14:13 ` Buggs
2001-10-17 14:34 ` Tim Goodwin
2001-10-17 21:13 ` Buggs [this message]
[not found] ` <20011019004843.A429@gc.wirefire.com>
2001-10-19 17:14 ` Tim Goodwin
2001-10-22 6:47 ` Scott Schwartz
2001-10-24 3:25 ` Chris Siebenmann
2001-10-24 3:41 ` Scott Schwartz
2001-10-23 7:55 ` Carlo Strozzi
2001-10-23 12:44 ` Tim Goodwin
2001-10-23 21:32 ` Carlo Strozzi
2001-10-24 3:34 ` Chris Siebenmann
2001-10-24 8:04 ` Carlo Strozzi
2001-10-23 15:47 ` Markus Friedl
2001-10-23 21:09 ` Carlo Strozzi
2001-10-23 15:55 ` Sam Roberts
2001-10-23 21:14 ` Scott Schwartz
2001-10-26 23:57 Gary Carvell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011017222058.16189.qmail@mail.splashground.de \
--to=buggs-rc@splashground.de \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=tjg@star.le.ac.uk \
/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 NNTP newsgroup(s).