public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Damon M. Conway" <damon@3jane.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] grace not working
Date: Thu, 13 Dec 2001 13:44:14 -0600	[thread overview]
Message-ID: <20011213194414.DD1D3EC37@chiba.3jane.net> (raw)
In-Reply-To: <1008271185.3209.12.camel@nosferatu.lan>

 Martin Schlemmer wrote:
>This issue has come up before ...
>
>I do not use csh myself, and due to time considerations,
>would appreciate it if you could give me a short howto on
>how csh and tcsh (if you know ..) does things.  Meaning
>what it use in the place of /etc/profile, the synstax=20
>defferences, etc.

I'm a big tcsh user so I can help.

/etc/csh.cshrc  ==  /etc/profile
/etc/csh.login  ==  /etc/bashrc (if such a thing exists for bash)
/etc/csh.logout

Like profile, you should keep the csh.cshrc, csh.login, and csh.logout files
free of tcsh specific commands lest someone uses standard csh.  This is
generally not a problem since most of what you set in these files are env
vars and paths.

I generally put stuff like keychain and my mh setup in ~/.login so that it
only executes when I get an actual login.  Otherwise, it tries to start
keychain when I scp to that host.  Paths and umask are pretty much the only
thing I put in cshrc

Instead of export you have setenv.

setenv VAR 'value'  ie.  setenv CVSROOT 'kabau@cvs.gentoo.org:/home/cvs'

Paths are generally set like so:

set path = (/bin /usr/bin /usr/local/bin /usr/X11R6/bin)

My paths look like so:

set binpath = (/bin /usr/bin /usr/local/bin)
set ccspath = (/usr/ccs/bin)
set sbinpath = (/sbin /usr/sbin /usr/local/sbin)
set userpath = ($HOME/bin)
set xpath = (/usr/X11R6/bin)
set path = ($binpath $sbinpath $xpath)

if ($OSTYPE == "solaris") then
    set path = ($path $ccspath)
endif

foreach HOSTNAME ("case" "thedrag" "ashpool")
    if ($HOST == $HOSTNAME) then
        set path = ($path $gnomepath $kdepath)
    endif
end

set path = ($path $userpath)

>I can then, if Daniel agree, add the funtionality to env-update to also
>update things for csh, etc.

I didn't realize that I was missing /etc/env.d functionality until Tibor
sent an email about it.  I'll be happy to help with or do the tcsh
functionality in env-update.  I didn't even realize that we don't install
system-wide startup files for (t)csh users.

kabau

--
"UNIX was not designed to stop you from doing stupid things, because that
 would also stop you from doing clever things."  --Doug Gwyn


  reply	other threads:[~2001-12-13 19:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 11:17 [gentoo-dev] grace not working Tibor Rudas
2001-12-12 17:17 ` Martin Schlemmer
2001-12-13 16:18   ` Tibor Rudas
2001-12-13 19:19     ` Martin Schlemmer
2001-12-13 19:44       ` Damon M. Conway [this message]
2001-12-13 21:01         ` Tibor Rudas
2001-12-13 22:36           ` Damon M. Conway
2001-12-13 23:42             ` Damon M. Conway

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=20011213194414.DD1D3EC37@chiba.3jane.net \
    --to=damon@3jane.net \
    --cc=gentoo-dev@gentoo.org \
    /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