Re: setopt and alias questions

[Sweth Chandramouli <sweth@xxxxxxxxxxxxxxxxxxxx>]

On Sun, Feb 07, 1999 at 05:59:31PM -0800, Bart Schaefer wrote:
> Please stop using <zsh-users@xxxxxxxxxxxxxxx>.  The mailing list address is
> now <zsh-users@xxxxxxxxxxxxxx>.  Forwarding through the old address won't
> work forever.  Your Mail-Followup-To: header should be fixed, too.
	oops.  i never noticed that i was using the old address.

> On Feb 7,  7:37pm, Sweth Chandramouli wrote:
> } 	1) is there some way to force setopt to list the status
> } of all options?
> 
> Yes:  setopt kshoptionprint
> 
> However, this produces all sorts of lovely double-negatives like
> 
> noalwayslastprompt    off
> noautolist            off
> noautomenu            off
> nolistambiguous       off
> nolistbeep            off
> nolisttypes           off
	
	here's the workaround i just came up with; it depends on the
fact that the options that already start with "no" (e.g. notify) are,
by default, on.  it probably needs a test at the beginning to see
what the current value of kshoptionprint is, but since i won't ever
be setting that option manually now that i have this function, i
didn't bother to put it in.

allopt () {
   builtin setopt kshoptionprint
   for OPT_PAIR in ${(f)$(builtin setopt)} ; do
      OPT_VALUE=$((${#${(M)OPT_PAIR% *}}%2))
      OPT_NAME=${OPT_PAIR% *}
      if [[ ${OPT_NAME#no} != ${OPT_NAME} ]] ; then
         OPT_VALUE=$(( (${OPT_VALUE}+1)%2 )) &&
            OPT_NAME=${OPT_NAME#no};
      fi;
      if [[ ${OPT_VALUE} = 1 ]] ; then
         OPT_VALUE='on'
      else OPT_VALUE='off'
      fi;
      echo ${(r:28:)OPT_NAME} ${OPT_VALUE}
   done
   builtin unsetopt kshoptionprint
}

> } 	2) does zsh not support tracking or exporting of aliases?
> 
> Zsh does not export aliases.  
	so aliases to be present in all interactive shells must be
defined in .zshrc?  aside from global aliases, is there any reason
to not put all of my aliases into equivalent functions?  (other than
memory use, of course.)

> I don't know what you mean by "tracking."
	ksh tracks aliases (it used to be an option to the alias command,
but now i believe it is mandatory) as a security/efficiency aid.  tracking
means that when an alias is first invoked, its definition is modified as
though all commands it calls were defined with their full paths.  this
speeds things up a little because all subsequent invocations of that
alias don't have to find the commands in PATH, and is a bit more secure
in that it can be used, by aliasing commands like ls, to help prevent 
problems caused by insecure paths--once a command that has been "wrapped"
by its alias has been invoked, subsequent invocations will refer back
to that original command, as opposed to, say, an evil trojan in the current
directory that would otherwise have been run by a PATH containing ".".

	-- sweth.

-- 
Sweth Chandramouli
IS Coordinator, The George Washington University
<sweth@xxxxxxx> / (202) 994 - 8521 (V) / (202) 994 - 0458 (F)
<a href="http://astaroth.nit.gwu.edu/~sweth/disc.html";>*</a>