From: Derek Fawcus <firstname.lastname@example.org> To: Byron Rakitzis <email@example.com> Cc: firstname.lastname@example.org, pk@TechFak.Uni-Bielefeld.DE, email@example.com Subject: Re: non login "rc" needs customized environment Date: Wed, 27 Feb 2002 01:13:02 -0500 [thread overview] Message-ID: <20020227061302.B5979@edinburgh.cisco.com> (raw) In-Reply-To: <200202150411.g1F4BTn06392@rakitzis.com>; from firstname.lastname@example.org on Thu, Feb 14, 2002 at 11:11:29PM -0500 On Thu, Feb 14, 2002 at 11:11:29PM -0500, Byron Rakitzis wrote: > > All I'm saying is that you don't necessarily want .rcrc to run via rsh -- > there might be stuff in there that depends on an interactive shell. Hence > the suggestion that a different mechanism be used. > > That being said, I like to use stricter rules for my personal .rcrc: > it is idempotent, so I can always issue ". .rcrc" and be sure there > won't be any nonsense in my environment. 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 _like_ the fact that I can get an virgin environment when logging in remotely. In fact the above could be hidden by having a _local_ wrapper for ssh which played the above games when logging into the remote system. Alternately since ssh can pass environment strings across to the remote process, simply set the environment you need for rc at your local end and allow this to inititialise the remote rc. DF
next prev parent reply other threads:[~2002-02-27 6:18 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 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 [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-27 6:29 Byron Rakitzis 2002-02-27 6:26 Russ Cox 2002-02-27 0:52 Byron Rakitzis 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] <email@example.com> 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=20020227061302.B5979@edinburgh.cisco.com \ --firstname.lastname@example.org \ --email@example.com \ --cc=pk@TechFak.Uni-Bielefeld.DE \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: non login "rc" needs customized environment' \ /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
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).