From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Tue, 16 Dec 2008 20:25:13 +0100 From: "Rudolf Sykora" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <1295100d9db84ab0e50f470ef38221ff@quintile.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1295100d9db84ab0e50f470ef38221ff@quintile.net> Subject: Re: [9fans] sam/rc script problem Topicbox-Message-UUID: 6326e360-ead4-11e9-9d60-3106f5b1d025 > if you need VT in order to run your editor you could edit the file remotely > from plan9. To do this either run u9fs on the linux box, or pick up > sftpfs from contrib and use ssh. You can then import your linux boxes > namespace from plan9 (by convention put the magic in the 9fs script so its easy to do). I've been using this for some time. > now you can edit files and run normal command line tools on plan9, and you only > need to use your ssh session to start programs. this (in my case at least) means I > no longer need vt and just use a rio window, so all the features of rio work > in the linx windows as elsewhere. > > beware, bash can do some strange things to its output as you cut and paste long lines to it. > I usually run either a Bourne shell or Byron's rc(1) for Unix for sanity's sake. well, this doesn't work for me, even when using just 'rc' (i.e. not bash). When not using 'vt' I get CR printed at the end of each line, I can't read man pages, etc. Even though your approach allows me to use a mouse for e.g. copying, mentioned cons are just too serious. Ruda