rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: non login "rc" needs customized environment
Date: Wed, 27 Feb 2002 01:26:13 -0500	[thread overview]
Message-ID: <0dd80d6ff918424807184c4f650c5424@plan9.bell-labs.com> (raw)

> Add a flag (say -S) which when used as 'rc -S file' will act as if ". file"
> had been the first command executed.  I've been thinking of hacking this
> into my copy of rc,  just so that when starting xterms I can be lasy and
> forgo typing '. .rc/interactive' into every new shell.
> 
> This could then be used with "ssh -t host 'rc -S startup_file'" from the
> originating host if a specific environment set up is required.   I quite

Even easier, just use ssh -t host 'rc -c ''. startup_file; . -i /dev/stdin'''.



             reply	other threads:[~2002-02-27  6:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27  6:26 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-27  6:29 Byron Rakitzis
2002-02-27  0:52 Byron Rakitzis
2002-02-15  4:11 Byron Rakitzis
2002-02-15 14:04 ` Tim Goodwin
2002-02-27  1:46   ` callum.gibson
2002-02-27  2:16     ` Chris Siebenmann
2002-02-27 13:32       ` Carlo Strozzi
2002-02-27 13:29   ` Carlo Strozzi
2002-02-27 22:24     ` Matt H
2002-02-27  6:13 ` Derek Fawcus
2002-02-14 17:44 Byron Rakitzis
2002-02-15  0:18 ` Dave Mason
2002-02-15  3:21 ` Scott Schwartz
2002-02-14 13:35 Smarasderagd
2002-02-15  0:37 ` Greg A. Woods
     [not found] <chet@nike.ins.cwru.edu>
2002-02-13 20:36 ` Chet Ramey
2002-02-14  2:16   ` Scott Schwartz
2002-02-14 23:35     ` Markus Friedl
2002-02-15  3:05       ` Scott Schwartz
2002-02-13 19:21 Peter Koch

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=0dd80d6ff918424807184c4f650c5424@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --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).