From: Fletch <fletch@phydeaux.org>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: 4.0.1-pre-1 on RH6.2
Date: 15 Feb 2001 14:31:13 -0500 [thread overview]
Message-ID: <m266ibvj3y.fsf@godzilla.phydeaux.org> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Thu, 15 Feb 2001 18:04:47 +0000"
>>>>> "Bart" == Bart Schaefer <schaefer@candle.brasslantern.com> writes:
[...]
Bart> Is there anything in /etc/zshenv or /etc/zshrc that's the
Bart> same on both machines? "make check" has the problem that
Bart> it's vulnerable to being messed with by the global rcfiles,
Bart> and completion is the most exposed.
Both machines have the zsh{rc,env} from the RedHat zsh-3.0.7-4
RPM. But nothing really out of the ordinary is set (at least as far
as I can see).
---->8 /etc/zshrc 8<----
#
# /etc/zshrc is sourced in interactive shells. It
# should contain commands to set up aliases, functions,
# options, key bindings, etc.
#
# Set up aliases
alias mv='nocorrect mv' # no spelling correction on mv
alias cp='nocorrect cp' # no spelling correction on cp
alias mkdir='nocorrect mkdir' # no spelling correction on mkdir
# Shell functions
setenv() { export $1=$2 } # csh compatibility
# Set prompts
PROMPT='%m%# ' # default prompt
#RPROMPT=' %~' # prompt for right side of screen
# Some environment variables
export HOSTNAME=`/bin/hostname`
export MAIL=/var/spool/mail/$USER
path=($path $HOME/bin)
# bindkey -v # vi key bindings
# bindkey -e # emacs key bindings
bindkey ' ' magic-space # also do history expansino on space
---->8 /etc/zshrc 8<----
---->8 /etc/zshenv 8<----
#
# /etc/zshenv is sourced on all invocations of the
# shell, unless the -f option is set. It should
# contain commands to set the command search path,
# plus other important environment variables.
# .zshenv should not contain commands that product
# output or assume the shell is attached to a tty.
#
export X11HOME=/usr/X11R6
if [ `id -u` -eq 0 ]; then
path=(/sbin /usr/sbin)
fi
echo $PATH | /bin/grep -q "\W$X11HOME/bin:" || path=($path $X11HOME/bin)
echo $PATH | /bin/grep -q "\W/bin:" || path=($path /bin)
echo $PATH | /bin/grep -q "\W/usr/bin:" || path=($path /usr/bin)
echo $PATH | /bin/grep -q "\W/usr/local/bin:" || path=($path /usr/local/bin)
---->8 /etc/zshenv 8<----
--
Fletch | "If you find my answers frightening, __`'/|
fletch@phydeaux.org | Vincent, you should cease askin' \ o.O'
770 933-0600 x211(w) | scary questions." -- Jules =(___)=
| U
next prev parent reply other threads:[~2001-02-15 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 17:14 Bart Schaefer
2001-02-15 17:31 ` Fletch
2001-02-15 18:04 ` Bart Schaefer
2001-02-15 19:31 ` Fletch [this message]
2001-02-17 0:51 ` Peter Stephenson
2001-02-18 1:21 ` Bart Schaefer
2001-02-19 10:25 Sven Wischnowsky
2001-02-19 10:37 ` Andrej Borsenkow
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=m266ibvj3y.fsf@godzilla.phydeaux.org \
--to=fletch@phydeaux.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).