zsh-users
 help / color / mirror / code / Atom feed
From: Thorsten Haude <zsh@thorstenhau.de>
To: zsh-users@sunsite.dk
Subject: Re: Options are not set
Date: Tue, 7 May 2002 19:28:40 +0200	[thread overview]
Message-ID: <20020507172840.GH2512@acp1130.ac1.dsh.de> (raw)
In-Reply-To: <20020507170005.GF50922@roman.mobil.cz>

Hi,

* Roman Neuhauser <neuhauser@mail.cz> [02-05-07 19:00]:
>    When listing options (by `setopt', `unsetopt', `set -o' or `set
>    +o'), those turned on by default appear in the list prefixed with
>    `no'. Hence (unless KSH_OPTION_PRINT is set), `setopt' shows all
>    options whose settings are changed from the default.
>
>    check the missing options in the manual, they're on by default.
Sorry, that means that my information is lacking.

However, that also means that something else is wrong, which I even
have a harder time seeing. The options are not set, at least I get not
the results I expect.
- No history is written
- If I want to start a program in subdir 'source' and enter
	sour<tab>
I get
	source _
not the
	source/_
I expect.
- auto_list seems to work, I was not thouroug enough here.

I browsed in zshoptions for anything related to directories and the
history, but couldn't find anything.

Thanks for your time!

Thorsten
-- 
Nobody will ever need more than 640 kB RAM.     -- Bill Gates, 1983
Windows XP requires 64 MB RAM.                  -- Bill Gates, 2001
Nobody will ever need Windows XP.               -- logical conclusion


  reply	other threads:[~2002-05-07 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 16:37 Thorsten Haude
2002-05-07 16:37 ` Will Yardley
2002-05-07 16:51 ` Thorsten Haude
2002-05-07 17:00 ` Roman Neuhauser
2002-05-07 17:28   ` Thorsten Haude [this message]
2002-05-07 17:28     ` Bart Schaefer
2002-05-07 18:25       ` Thorsten Haude
2002-05-07 18:27         ` Will Yardley
2002-05-07 18:28       ` Thorsten Haude

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=20020507172840.GH2512@acp1130.ac1.dsh.de \
    --to=zsh@thorstenhau.de \
    --cc=zsh-users@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).