From: Timothy J Luoma <tjlists@bigfoot.com>
To: zsh-workers@sunsite.auc.dk
Cc: dwight_lee@fortdearborn.com
Subject: (fwd) zsh can't hold options in MOSXS
Date: Fri, 21 May 1999 07:57:13 -0400 [thread overview]
Message-ID: <199905211157.HAA09160@ocalhost> (raw)
Dwight Lee posted this to comp.sys.next.* newsgroups (incorrectly
crossposting to csn.misc, but that's another story ;-)
I thought it likely that few folks on this list would see it so I repost it
here with followups to 'dwight_lee@fortdearborn.com'
NOTE: "MOSXS" stands for "Mac OS X Server"
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.
Oddly, if I pick another option, like autocd, it's fine.
Is this a zsh problem or a MOSXS problem?
Sample:
versace ~ $ ps auxw | grep $$
font 20893 0.0 0.4 2.78M 1.05M p4 S 0:00 /bin/zsh
font 20930 0.0 0.2 2.39M 496K p4 S 0:00 grep 20893
versace ~ $ setopt
interactive
monitor
shinstdin
zle
versace ~ $ setopt autolist
versace ~ $ setopt
interactive
monitor
shinstdin
zle
versace ~ $ setopt autocd
versace ~ $ setopt
autocd
interactive
monitor
shinstdin
zle
versace ~ $
--
Dwight Lee / dwight_lee@fortdearborn.com 1530 Morse Avenue
Information Technology Elk Grove Village, IL 60007 USA
Virtualcolor Division +1 847 357 9500 voice
Fort Dearborn Company +1 847 357 8726 fax
next reply other threads:[~1999-05-21 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-21 11:57 Timothy J Luoma [this message]
1999-05-31 6:37 ` Bart Schaefer
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=199905211157.HAA09160@ocalhost \
--to=tjlists@bigfoot.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).