From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: dwight_lee@fortdearborn.com, zsh-workers@sunsite.auc.dk
Subject: Re: zsh can't hold options in MOSXS
Date: Mon, 31 May 1999 06:37:27 +0000 [thread overview]
Message-ID: <990531063728.ZM1506@candle.brasslantern.com> (raw)
In-Reply-To: <199905211157.HAA09160@ocalhost>
On May 21, 7:57am, Timothy J Luoma wrote:
} Subject: (fwd) zsh can't hold options in MOSXS
}
} Begin forwarded message:
}
} Newsgroups: comp.sys.next.bugs,comp.sys.next.misc
} Subject: zsh can't hold options in MOSXS
} Date: 21 May 1999 08:14:50 GMT
} Organization: MCSNet Services
} Message-ID: <7i34lq$8et$1@Nntp1.mcs.net>
}
} As a faithful zsh user, I of course set myself up on Mac OS X Server
} with zsh, but found that my preferred options weren't sticking.
} Specifically, autolist (aka AUTO_LIST) doesn't show up in a plain
} "setopt", and it's not the default. I compiled my own copy of zsh
} 3.1.5 and the same thing happened.
Autolist -is- on by default in 3.1.5, so it won't show up in setopt
output. Try doing "setopt kshoptionprint" so that you can see the
state of every option; in 3.1.5 I see (among lots of others)
noautolist off
("no... off" is "on").
} Is this a zsh problem or a MOSXS problem?
It's a zsh 3.1.5 "problem": A whole lot of options that weren't on by
default in 3.0.x got made on-by-default in 3.1.5, and the way that
"setopt" prints them correspondingly changed.
The only other time I've something that could be described as "options
not sticking" is when using a zsh that has been patched to add or change
the list of options, and then rebuilt without all the .o files getting
recompiled.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1999-05-31 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-21 11:57 (fwd) " Timothy J Luoma
1999-05-31 6:37 ` Bart Schaefer [this message]
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=990531063728.ZM1506@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=dwight_lee@fortdearborn.com \
--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).