From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15214 invoked from network); 23 Jan 2002 22:08:29 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 23 Jan 2002 22:08:29 -0000 Received: (qmail 13504 invoked by alias); 23 Jan 2002 22:08:07 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 4618 Received: (qmail 13493 invoked from network); 23 Jan 2002 22:08:05 -0000 To: zsh-users@sunsite.auc.dk Subject: Z-Shell (zsh) FAQ changes this month Date: Wed, 23 Jan 2002 22:09:20 +0000 From: Peter Stephenson Message-Id: <20020123220925.963C514287@pwstephenson.fsnet.co.uk> This file contains general information on how to find out about zsh, (the first part of the FAQ up to item 1.1), then any other items which have changed since last month's posting, then the differences in the yodl version of the FAQ. If you would like a complete individual copy, email me and I will add you to the list. Archive-Name: unix-faq/shell/zsh Last-Modified: 2002/01/23 Submitted-By: pws@pwstephenson.fsnet.co.uk (Peter Stephenson) Posting-Frequency: Monthly Copyright: (C) P.W. Stephenson, 1995--2001 (see end of document) Changes since last issue posted: 3.27 New item: commands which can be executed but are not visible. This document contains a list of frequently-asked (or otherwise significant) questions concerning the Z-shell, a command interpreter for many UNIX systems which is freely available to anyone with FTP access. Zsh is among the most powerful freely available Bourne-like shell for interactive use. If you have never heard of `sh', `csh' or `ksh', then you are probably better off to start by reading a general introduction to UNIX rather than this document. If you just want to know how to get your hands on the latest version, skip to question 1.6; if you want to know what to do with insoluble problems, go to 5.2. Notation: Quotes `like this' are ordinary textual quotation marks. Other uses of quotation marks are input to the shell. Contents: Chapter 1: Introducing zsh and how to install it 1.1. Sources of information 1.2. What is it? 1.3. What is it good at? 1.4. On what machines will it run? (Plus important compilation notes) 1.5. What's the latest version? 1.6. Where do I get it? 1.7. I don't have root access: how do I make zsh my login shell? Chapter 2: How does zsh differ from...? 2.1. sh and ksh? 2.2. csh? 2.3. Why do my csh aliases not work? (Plus other alias pitfalls.) 2.4. tcsh? 2.5. bash? 2.6. Shouldn't zsh be more/less like ksh/(t)csh? Chapter 3: How to get various things to work 3.1. Why does `$var' where `var="foo bar"' not do what I expect? 3.2. In which startup file do I put...? 3.3. What is the difference between `export' and the ALL_EXPORT option? 3.4. How do I turn off spelling correction/globbing for a single command? 3.5. How do I get the meta key to work on my xterm? 3.6. How do I automatically display the directory in my xterm title bar? 3.7. How do I make the completion list use eight bit characters? 3.8. Why do the cursor (arrow) keys not work? 3.9. Why does my terminal act funny in some way? 3.10. Why does zsh not work in an Emacs shell mode any more? 3.11. Why do my autoloaded functions not autoload [the first time]? 3.12. How does base arithmetic work? 3.13. How do I get a newline in my prompt? 3.14. Why does `bindkey ^a command-name' or 'stty intr ^-' do something funny? 3.15. Why can't I bind \C-s and \C-q any more? 3.16. How do I execute command `foo' within function `foo'? 3.17. Why do history substitutions with single bangs do something funny? 3.18. Why does zsh kill off all my background jobs when I logout? 3.19. How do I list all my history entries? 3.20. How does the alternative loop syntax, e.g. `while {...} {...}' work? 3.21. Why is my history not being saved? 3.22. How do I get a variable's value to be evaluated as another variable? 3.23. How do I prevent the prompt overwriting output when there is no newline? 3.24. What's wrong with cut and paste on my xterm? 3.25. How do I get coloured prompts on my colour xterm? 3.26. Why is my output duplicated with `foo 2>&1 >foo.out | bar'? 3.27. Why am I prompted to correct commands which are in my path? Chapter 4: The mysteries of completion 4.1. What is completion? 4.2. What sorts of things can be completed? 4.3. How does zsh deal with ambiguous completions? 4.4. How do I complete in the middle of words / just what's before the cursor? 4.5. How do I get started with programmable completion? 4.6. And if programmable completion isn't good enough? Chapter 5: The future of zsh 5.1. What bugs are currently known and unfixed? (Plus recent important changes) 5.2. Where do I report bugs, get more info / who's working on zsh? 5.3. What's on the wish-list? 5.4. Did zsh have problems in the year 2000? Acknowledgments Copyright --- End of Contents --- Chapter 1: Introducing zsh and how to install it 1.1: Sources of information Information on zsh is available via the World Wide Web. The URL is http://zsh.sunsite.dk/ . The server provides this FAQ and much else and is now maintained by Karsten Thygesen and others (mail zsh@sunsite.dk with any related messages). The FAQ is at http://zsh.sunsite.dk/FAQ/ . The site also contains some contributed zsh scripts and functions; we are delighted to add more, or simply links to your own collection. This document was originally written in YODL, allowing it to be converted easily into various other formats. The master source file lives at http://zsh.sunsite.dk/FAQ/zshfaq.yo and the plain text version can be found at http://zsh.sunsite.dk/FAQ/zshfaq.txt . Another useful source of information is the collection of FAQ articles posted frequently to the Usenet news groups comp.unix.questions, comp.unix.shells and comp.answers with answers to general questions about UNIX. The fifth of the seven articles deals with shells, including zsh, with a brief description of differences. There is also a separate FAQ on shell differences and how to change your shell. Usenet FAQs are available via FTP from rtfm.mit.edu and mirrors and also on the World Wide Web; see USA http://www.cis.ohio-state.edu/hypertext/faq/usenet/top.html UK http://www.lib.ox.ac.uk/internet/news/faq/comp.unix.shell.html Netherlands http://www.cs.uu.nl/wais/html/na-dir/unix-faq/shell/.html You can also get it via email by emailing mail-server@rtfm.mit.edu with, in the body of the message, `send faqs/unix-faq/shell/zsh'. The latest version of this FAQ is also available directly from any of the zsh archive sites listed in question 1.6. I have been putting together a user guide to complement the manual by explaining the most useful features of zsh in a more easy to read way. This is now more than half complete and includes a discussion of the new form for command line completion, not described in the FAQ. You can find it in various formats at: http://zsh.sunsite.dk/Guide/ (As a method of reading the following in Emacs, you can type \M-2 \C-x $ to make all the indented text vanish, then \M-0 \C-x $ when you are on the title you want.) For any more eclectic information, you should contact the mailing list: see question 5.2. --- End of general information, changed items follow in full --- Minor changes of phrasing, spelling, etc. are not included. 3.27: Why am I prompted to correct commands which are in my path? (Or, if you know about the command hash table, the command isn't in the table even though you know it works --- it's the same basic problem.) It occasionally happens that a directory in your path is not readable, although files in it have `execute' permission. Then the system can execute them, but the shell can't see them when it scans the path, since it does that by trying to read the directory. If this is the case, you may find `which var(cmd)' does find the command, since then the shell checks the path explicitly for that one command rather than looking for all files in the directory. --- End of changed items, diff from previous version follows --- Index: zshfaq.yo =================================================================== RCS file: /pack/anoncvs/zsh/www/FAQ/zshfaq.yo,v retrieving revision 1.72 retrieving revision 1.73 diff -u -r1.72 -r1.73 --- zshfaq.yo 2001/12/21 17:14:16 1.72 +++ zshfaq.yo 2002/01/23 22:03:09 1.73 @@ -43,11 +43,11 @@ whenman(report(ARG1)(ARG2)(ARG3))\ whenms(report(ARG1)(ARG2)(ARG3))\ whensgml(report(ARG1)(ARG2)(ARG3))) -myreport(Z-Shell Frequently-Asked Questions)(Peter Stephenson)(2001/12/21) +myreport(Z-Shell Frequently-Asked Questions)(Peter Stephenson)(2002/01/23) COMMENT(-- the following are for Usenet and must appear first)\ description(\ mydit(Archive-Name:) unix-faq/shell/zsh -mydit(Last-Modified:) 2001/12/21 +mydit(Last-Modified:) 2002/01/23 mydit(Submitted-By:) email(pws@pwstephenson.fsnet.co.uk (Peter Stephenson)) mydit(Posting-Frequency:) Monthly mydit(Copyright:) (C) P.W. Stephenson, 1995--2001 (see end of document) @@ -55,7 +55,7 @@ bf(Changes since last issue posted:) description( - mydit( ) None. + mydit(3.27) New item: commands which can be executed but are not visible. ) This document contains a list of frequently-asked (or otherwise @@ -121,6 +121,7 @@ 3.24. What's wrong with cut and paste on my xterm? 3.25. How do I get coloured prompts on my colour xterm? 3.26. Why is my output duplicated with `tt(foo 2>&1 >foo.out | bar)'? +3.27. Why am I prompted to correct commands which are in my path? Chapter 4: The mysteries of completion 4.1. What is completion? @@ -1746,6 +1747,19 @@ first example is exactly the same, however the second redirector is disguised as a pipe. So if you want to turn this effect off, you need to unset the option mytt(MULTIOS). + +sect(Why am I prompted to correct commands which are in my path?) + +(Or, if you know about the command hash table, the command isn't in the +table even though you know it works --- it's the same basic problem.) + +It occasionally happens that a directory in your path is not readable, +although files in it have `execute' permission. Then the system can +execute them, but the shell can't see them when it scans the path, since +it does that by trying to read the directory. If this is the case, you +may find `tt(which )var(cmd)' does find the command, since then the +shell checks the path explicitly for that one command rather than +looking for all files in the directory. chapter(The mysteries of completion)