rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Tom Culliton <culliton@clark.net>
To: broman@nosc.mil
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: "rc" shell maintainer?
Date: Tue, 10 Feb 1998 18:26:40 -0500	[thread overview]
Message-ID: <199802102326.SAA10989@shell.clark.net> (raw)
In-Reply-To: Your message of "Mon, 09 Feb 1998 18:45:04 EST." <19980209234504.4267.qmail@np.nosc.mil>

On Mon, 09 Feb 1998 18:45:04 EST, Vincent Broman wrote:
> 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".

Hmmm... This sounds familiar, are you building with GNU Readline?  Now
all I have to do is remember what I did to fix it... 8-/

I probably posted a patch...  Aha...  Yes I did, but Tim never picked
it up.  Look back through the archives for a message from me which
moves print_prompt2 from lex.c to input.c amoung other things.  I sent
it before my big signal handling fix.



  reply	other threads:[~1998-02-11  0:24 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 [this message]
1998-02-11 10:45           ` Tim Goodwin
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=199802102326.SAA10989@shell.clark.net \
    --to=culliton@clark.net \
    --cc=broman@nosc.mil \
    --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).