zsh-workers
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: adding a toplevel zsh.spec.in file
Date: Mon, 17 Jul 2000 16:09:33 +0100	[thread overview]
Message-ID: <20000717160933.B6739@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <1000707181834.ZM1473@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Fri, Jul 07, 2000 at 06:18:33PM +0000

Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> On Jul 7,  6:44pm, Zefram wrote:
> } Subject: Re: adding a toplevel zsh.spec.in file
> }
> } Is there anything that ought to go in /etc/z* on more machines than,
> } say, those in a single company?
> 
> I've always asserted that there is not, with the possible exception of
> default path settings in /etc/zshenv.

In /etc/zshenv:

What about setting of umask?  In the last discussion about this kind
of stuff you suggested that umask setting was better done in zshrc.
But shouldn't it be set correctly for non-interactive processes too?

These don't do much harm either (quoted mostly straight from Bart
anyway ;-)

  export USER=`id -un`
  export LOGNAME=$USER
  export HOSTNAME=$HOST
  
  # this only on appropriate boxes of course
  export MAIL=/var/spool/mail/$USER
  
  HISTSIZE=1000
  HISTFILE=~/.zshhistory
  SAVEHIST=1000
  
  export INPUTRC=/etc/inputrc
  
Is there any good reason why /sbin and /usr/sbin should not be on
every user's path by default?  They're not under RedHat, which is
infuriating when it comes to using traceroute, lsof etc.

Now here's a candidate for StartupFiles/RedHat/zshrc.  Anything badly
wrong?

--------- 8< --------- 8< --------- 8< --------- 8< --------- 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

# Where to look for autoloaded function definitions
fpath=(
       ~/{lib/zsh,.zsh}/{functions,scripts}(N)
       ~/.z{sh,}func*(N)
       $fpath
       /usr/doc/zsh*/Functions(N)
      )

typeset -U fpath

# Autoload all shell functions from all directories
# in $fpath that have the executable bit on
# (the executable bit is not necessary, but gives
# you an easy way to stop the autoloading of a
# particular shell function).
for dirname in $fpath
do
  fns=( $dirname/*(N.x:t) )
  (( $#fns )) && autoload $fns
done

# Set prompts
PS1='%n@%m %B%3~%b %# '        # default prompt
#RPS1=' %~'                     # prompt for right side of screen

#bindkey -v               # vi key bindings
#bindkey -e               # emacs key bindings
#bindkey ' ' magic-space  # also do history expansion on space

--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------


  reply	other threads:[~2000-07-17 15:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07 11:53 Adam Spiers
2000-07-07 12:45 ` Peter Stephenson
2000-07-07 16:15 ` Chmouel Boudjnah
2000-07-17 14:56   ` Adam Spiers
2000-07-07 17:18 ` Bart Schaefer
2000-07-07 17:44   ` Zefram
2000-07-07 18:18     ` Bart Schaefer
2000-07-17 15:09       ` Adam Spiers [this message]
2000-07-17 17:48         ` Bart Schaefer
2000-07-17 18:07           ` Adam Spiers
2000-07-17 21:05             ` Oliver Kiddle
2000-07-17 23:35               ` Adam Spiers
2000-07-18  2:32                 ` Trond Eivind Glomsrød
2000-07-18  6:01                 ` Bart Schaefer
2000-07-18  1:56         ` PATCH: " Zefram
2000-07-18  5:22           ` Bart Schaefer
2000-07-18  6:15             ` Wayne Davison
2000-07-18  8:31               ` How to distribute skeleton zshrc etc. (Re: PATCH: Re: adding a toplevel zsh.spec.in file) Bart Schaefer
2000-07-18 16:54             ` PATCH: Re: adding a toplevel zsh.spec.in file Trond Eivind Glomsrød
2000-07-18  6:25           ` Andrej Borsenkow
2000-07-18  9:42           ` Peter Stephenson
2000-07-18 18:22           ` Trond Eivind Glomsrød
2000-07-18 19:57             ` Zefram
2000-07-18 20:07               ` Trond Eivind Glomsrød
2000-07-18 20:37                 ` Zefram

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=20000717160933.B6739@thelonious.new.ox.ac.uk \
    --to=adam@spiers.net \
    --cc=zsh-workers@sunsite.auc.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).