rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Donn Cave <donn@milton.u.washington.edu>
To: rc@archone.tamu.edu
Subject: Re: login shells
Date: Tue, 6 Aug 1991 16:17:19 -0500	[thread overview]
Message-ID: <9108062117.AA22670@milton.u.washington.edu> (raw)

| I like the 10th Edition method of putting a special variable in the
| environment of the invoked shell (REMOTE= or REMOTEHOST=otherhost or
| something like that).

That seems like a good idea, regardless.

But in order to use it, the shell has to be prepared to source some file
when it sees this variable (and then presumably delete the variable).
For rc, that would be .rcrc? so the effect would be similar to forcing
a "login" shell?

	Donn Cave, University Computing Services, University of Washington
	donn@cac.washington.edu


             reply	other threads:[~1991-08-06 21:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1991-08-06 21:17 Donn Cave [this message]
  -- strict thread matches above, loose matches on Subject: below --
1991-08-07 15:35 Donn Cave
1991-08-07  9:38 malte
1991-08-06 20:54 Chet Ramey
1991-08-06 16:10 Donn Cave
1991-08-02 15:26 Donn Cave
1991-08-06 12:16 ` Boyd Roberts

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=9108062117.AA22670@milton.u.washington.edu \
    --to=donn@milton.u.washington.edu \
    --cc=rc@archone.tamu.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).