From: Tim Goodwin <tgoodwin@cygnus.co.uk>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: "rc" shell maintainer?
Date: Wed, 11 Feb 1998 05:45:36 -0500 [thread overview]
Message-ID: <I0wAAGWB4TSy1A4A@nan.cygnus.co.uk> (raw)
In-Reply-To: <199802102326.SAA10989@shell.clark.net>
> > My rc-1.5b2 fails to trip because of the line testing
> >
> > prompt=';' if (!~ `` '' {. -i /tmp/dot.$pid>[2=1]} ';hi'^$nl';')
> >
> > It seems that '. -i' used to output prompts, but in 1.5b2 it does not.
> > Was this change unintentional? I'd be uneasy about changing
> > trip.rc to match spec "improvements".
This hasn't changed since 1.4: `-i' only works as documented if you
don't use readline or editline. I guess this is a bug, although I
haven't thought about it much.
(The trip failure is documented in the README file, for what it's
worth.)
> I probably posted a patch... Aha... Yes I did, but Tim never picked
> it up.
rc-1.5b2 was purely an autoconfiscation of rc-1.5betadev-1; I didn't
include any patches that had gone to the list. This was the quickest
way for me to get on top of the project.
> Look back through the archives for a message from me which
> moves print_prompt2 from lex.c to input.c amoung other things.
OK, I've got that, and will have a look at it.
Thanks,
Tim.
next prev parent reply other threads:[~1998-02-11 21:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-04 21:23 Vincent Broman
1998-02-05 1:17 ` Tom Culliton
1998-02-05 11:46 ` Tim Goodwin
1998-02-05 21:48 ` Vincent Broman
1998-02-06 18:00 ` Tim Goodwin
1998-02-06 22:54 ` Vincent Broman
1998-02-09 20:31 ` Vincent Broman
1998-02-09 23:45 ` Vincent Broman
1998-02-10 23:26 ` Tom Culliton
1998-02-11 10:45 ` Tim Goodwin [this message]
1998-02-11 22:23 ` Tom Culliton
1998-02-12 10:23 ` Tim Goodwin
1998-02-11 21:55 ` Vincent Broman
1998-02-05 5:01 smarry
1998-02-05 15:25 ` Tom Culliton
1998-02-06 17:45 ` Tim Goodwin
1998-02-05 19:59 smarry
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=I0wAAGWB4TSy1A4A@nan.cygnus.co.uk \
--to=tgoodwin@cygnus.co.uk \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).