* Re: zsh-2.6-beta21 released [not found] <199606192106.XAA09696@bolyai.cs.elte.hu> @ 1996-06-19 23:42 ` Clive Messer 1996-06-20 21:03 ` Mark Borges 0 siblings, 1 reply; 13+ messages in thread From: Clive Messer @ 1996-06-19 23:42 UTC (permalink / raw) To: Zoltan Hidvegi; +Cc: zsh-workers [-- Attachment #1: Type: TEXT/PLAIN, Size: 506 bytes --] On Wed, 19 Jun 1996, Zoltan Hidvegi wrote: > The texinfo documentation is updated but it does not contains the changes > in the manual between beta20 and beta21. Patch includes the changes. Zoltan: Are you going to update the Info files (makeinfo) before the next release as they are not built from the Makefile ? Clive. -- C Messer. Epos Systems. UK. | <clive@epos.demon.co.uk> | "I pressed her thigh and death smiled." <clive@epos.easynet.co.uk> | Jim Morrison. [-- Attachment #2: Type: TEXT/PLAIN, Size: 4809 bytes --] --- zsh.texi-2.0.2 Thu Jun 20 00:25:59 1996 +++ zsh.texi Thu Jun 20 00:25:59 1996 @@ -10,9 +10,9 @@ @afourpaper @end iftex -@set EDITION 2.0.2 -@set VERSION 2.6.20 -@set UPDATED 13 June 1996 +@set EDITION 2.0.3 +@set VERSION 2.6.21 +@set UPDATED 20 June 1996 @ifinfo @noindent @@ -1199,11 +1199,14 @@ Matches any character. @item [@dots{}] -Matches any of the enclosed characters. +Matches any of the enclosed characters. Ranges of characters can be specified +by separating two characters by a @code{-}. A @code{-} or @code{]} may be +matched by including it as the first character in the list. @item [^@dots{}] -Matches any character except the enclosed characters. @code{!@dots{}} -is the same as the above. +@itemx [!@dots{}] +Like @code{[@dots{}]}, except that it matches any character which is not in +the given set. @item <x-y> Matches any number in the range @code{x} to @code{y}, inclusive. If @@ -1690,15 +1693,19 @@ @cindex file descriptors @cindex descriptors, file The following may appear anywhere in a simple command or may precede or -follow a complex command. Substitution occurs before @var{word} is used -except as noted below. If the result of substitution on @var{word} -produces more than one filename, redirection occurs for each separate -filename in turn. +follow a complex command. Substitution occurs before @var{word} or +@var{digit} is used except as noted below. If the result of substitution on +@var{word} produces more than one filename, redirection occurs for each +separate filename in turn. @table @code @item <@var{word} Open file @var{word} as standard input. +@item <>@var{word} +Open file @var{word} for reading and writing as standard input. If the file +does not exist then it is created. + @item >@var{word} Open file @var{word} as standard output. If the file does not exist then it is created. If the file exists, and the @code{NO_CLOBBER} @@ -4002,9 +4009,14 @@ @item IFS @vindex IFS -Internal field separators, normally space, tab, and newline, that are -used to separate words which result from command or parameter -substitution and words read by the @code{read} builtin. +Internal field separators, normally space, tab, and newline, that are used to +separate words which result from command or parameter substitution and words +read by the @code{read} builtin. Any characters from the set space, tab and +newline that appear in the @code{IFS} are called @dfn{IFS white space}. One +or more IFS white space characters or one non-IFS white space character +together with any adjacent IFS white space character delimit a field. If an +IFS white space character appears twice consecutively in the @code{IFS}, this +character is treated as if it were not an IFS white space character. @item KEYTIMEOUT @vindex KEYTIMEOUT @@ -4901,7 +4913,7 @@ @pindex NO_BEEP Do not beep. -@item NO_CLOBBER (-1, ksh: -C) +@item NO_CLOBBER (-C, ksh: -C) @cindex file clobbering, preventing @cindex clobbering, of files @pindex NO_CLOBBER @@ -5029,7 +5041,7 @@ Commands explicitly beginning with @samp{./} or @samp{../} are not subject to path search. -@item PRINT_EXIT_VALUE (-C) +@item PRINT_EXIT_VALUE (-1) @cindex exit status, printing @pindex PRINT_EXIT_VALUE Print the exit value of programs with non-zero exit status. @@ -5110,8 +5122,8 @@ @pindex SH_GLOB @cindex globbing, sh style @cindex sh, globbing style -Disables the special meaning of @code{(}, @code{|} and @code{)} for globbing -the result of parameter and command substitutions, and in some other +Disables the special meaning of @code{(}, @code{|}, @code{)} and @code{<} for +globbing the result of parameter and command substitutions, and in some other places where the shell accepts patterns. This option is set if @code{zsh} is invoked as @code{sh} or @code{ksh}. @@ -6382,7 +6394,7 @@ supplies completion flags to be used before any other processing is done, even those given to specific commands with other @code{compctl} definitions. This is only useful when combined with extended completion -(the @samp{-x} flag. @xref{Extended Completion}. +(the @samp{-x} flag. @xref{Extended Completion}). Using this flag you can define default behaviour which will apply to all commands without exception, or you can alter the standard behaviour for all commands. For example, if your access to the user database is too @@ -6868,3 +6880,4 @@ v2.0.1. June 11th 1996. Spelling corrections. Changed single shell flags eg. "-f" to @samp, rather than @code. v2.0.2. June 13th 1996. Several fixes to Programmable Completion. +v2.0.3. June 20th 1996. Updated to include changes from 2.6.20 to 2.6.21. ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh-2.6-beta21 released 1996-06-19 23:42 ` zsh-2.6-beta21 released Clive Messer @ 1996-06-20 21:03 ` Mark Borges 1996-06-20 21:05 ` Zoltan Hidvegi 1996-06-21 7:30 ` zsh.texi commentary (actually, HTML pages commentary) Bart Schaefer 0 siblings, 2 replies; 13+ messages in thread From: Mark Borges @ 1996-06-20 21:03 UTC (permalink / raw) To: Clive Messer; +Cc: Zoltan Hidvegi, zsh-workers >> On Thu, 20 Jun 1996 00:42:20 +0100 (BST), >> Clive Messer(CM) wrote: CM> On Wed, 19 Jun 1996, Zoltan Hidvegi wrote: >> The texinfo documentation is updated but it does not contains the changes >> in the manual between beta20 and beta21. CM> Patch includes the changes. I've applied this patch and re-generated the html files via texi2html-1.50. The URL is still http://www.mal.com/zsh/Doc/test/ where zsh.texi.gz is version 2.03. BTW, with the recent change to the meaning of `<>', shouldn't the following patch be applied? Or is that change not considered permanent? $ diff -c zshexpn.1.orig zshexpn.1 *** zshexpn.1.orig Thu Jun 20 14:57:32 1996 --- zshexpn.1 Thu Jun 20 14:57:50 1996 *************** *** 489,496 **** matches any number in the range x to y, inclusive. If x is omitted, the number must be less than or equal to y. If y is omitted, the number must be greater than or equal to x. ! A pattern of the form \fB<\->\fP or ! simply \fB<>\fP matches any number. .TP \fB^x\fP matches anything except the pattern x. --- 489,495 ---- matches any number in the range x to y, inclusive. If x is omitted, the number must be less than or equal to y. If y is omitted, the number must be greater than or equal to x. ! A pattern of the form \fB<\->\fP matches any number. .TP \fB^x\fP matches anything except the pattern x. -- -mb- ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh-2.6-beta21 released 1996-06-20 21:03 ` Mark Borges @ 1996-06-20 21:05 ` Zoltan Hidvegi 1996-06-21 7:30 ` zsh.texi commentary (actually, HTML pages commentary) Bart Schaefer 1 sibling, 0 replies; 13+ messages in thread From: Zoltan Hidvegi @ 1996-06-20 21:05 UTC (permalink / raw) To: Mark Borges; +Cc: clive, zsh-workers > BTW, with the recent change to the meaning of `<>', shouldn't the > following patch be applied? Or is that change not considered > permanent? It is permanent. I just forgot it. Thanks. Zoltan ^ permalink raw reply [flat|nested] 13+ messages in thread
* zsh.texi commentary (actually, HTML pages commentary) 1996-06-20 21:03 ` Mark Borges 1996-06-20 21:05 ` Zoltan Hidvegi @ 1996-06-21 7:30 ` Bart Schaefer 1996-06-21 8:06 ` Zefram ` (2 more replies) 1 sibling, 3 replies; 13+ messages in thread From: Bart Schaefer @ 1996-06-21 7:30 UTC (permalink / raw) To: Clive Messer, Mark Borges, zsh-workers On Jun 20, 3:03pm, Mark Borges wrote: } Subject: Re: zsh-2.6-beta21 released } } I've applied this patch and re-generated the html files via } texi2html-1.50. The URL is still } } http://www.mal.com/zsh/Doc/test/ } } where zsh.texi.gz is version 2.03. I think maybe it should be clearer in the documents that 2.03 is the version number of the document and not the version of zsh to which it refers. `Edition 2.0.3' on the TOC page is confusing. For the rest of these comments, I don't know which need to change the man pages, the FAQ, zsh.texi, and/or all of them; but they're all from reading the HTML at the above URL. I've scattered semi-related thoughts and commentary throughout, usually prefixed with "Aside:". Intro section: <pf@z-code.com> hasn't been a usable address for Paul since almost two years ago. He's now <pf@software.com>. Aside: Question about NO_RCS: Commands are first read from `/etc/zshenv'. If the -f flag is given or if the NO_RCS option is set within `/etc/zshenv', all other initialization files are skipped. Why doesn't NO_RCS in any init file stop reading of any files that would normally follow the one where it is set? Or does it, and the doc just doesn't explicitly say so? Spell checking still hasn't happened ... "defauly"? Shell Grammar section: A simple command is a sequence of optional parameter assignments followed by blank-separated words, ^^^^^ Should this read "whitespace" or some such? (Too early to mention $IFS.) Aside: What's the value of a command executed in the background? E.g. if false & then echo Hmmm & fi Is it always consistent? Precommand modifiers, `exec', should explain that the "parent" zsh is replaced by the exec'd command, as if zsh had exited and the command was run in its place. Spell checking again ... "anexternal" --> "an external". Almost all the complex command descriptions could be clarified. Example: (Existing text) if list then list [ elif list ; then list ] ... [ else list ] fi The if list is executed, and, if it returns a zero exit status, the then list is executed. Otherwise, the elif list is executed and, if its value is zero, the then list is executed. If each elif list returns nonzero, the else list is executed. (Better, I think) if list1 then list2 [ elif list3 then list4 ] ... [ else list5 ] fi First list1 is executed, and, if its value is zero (it returns a zero exit status), then list2 is executed. Otherwise, if any elif is present, list3 is executed, and, if its value is zero, then list4 is executed. There may be more than one elif, each of which is tried in turn. Finally, if an else is present, and if all the if or elif lists returned nonzero values, then list5 is executed. The others aren't quite as bad because they don't need to repeat any one term in so many different places, but "while" and "until" are similar. Further, the whole section could benefit from some vertical white space between defined terms. Looks like it's there in the source but gets squashed out when displayed. I suppose its a texi2html problem (some strategic <br> need to be output). Aside: "select" is pretty much useless for more than 200 words or so. I've got some scripts that examine the file system that sometimes come up with 1000+ possible choices. Anybody have any solutions? Aside: Why doesn't `foreach name ( word ... )' need CSH_JUNKIE_PARENS? Aside: That it is possible to `disable -r fi' without first disabling `if', scares the willies out of me. Simliarly for `done' and `esac'. Aside: Given the above behavior of `disable -r', it'd be nice to be able to get at the internal tokens for the disabled reserved words. E.g.: foo() { if true ; then echo This function keeps working ; fi } alias endif=fi disable -r fi bar() { if true ; then echo I wish this still worked ; endif } Maybe an option to the alias builtin? The paragraph on Comments still refers to HISTCHARS; it's now histchars. texi2html is still having problems with pairs of single quotes (''), rendering that as a double quote ("). Expansion section: Why doesn't this section order the explanations of the kinds of expansion in the same order in which they are listed as taking place? Or at least in some sensible order, such as alphabetical? I'd love it if there were more hrefs, e.g. from every reference to an option name to the description of that option, or from a builtin's name to its description. E.g., in the sentence: The PUSHD_MINUS option exchanges the effects of ~+ and ~- where they are followed by a number. It'd be great to be able to click on PUSHD_MINUS. Only the "expression" part of identifier=expression is expanded, right? If the option MAGIC_EQUAL_SUBST is set, any unquoted shell argument in the form identifier=expression becomes eligible for file expansion as described in the previous paragraph. Say so? Parameter expansion: Italics on usages of `name[@]' are not consistent. Typo in ${name:#pattern}, "the } flag" should probably be "the @ flag". ${^spec}, ${=spec}, and ${~spec} still say "Toggle ..."; they should say "Turn on ...", right? Also, more details of what `spec' may be would be nice; e.g., is there a difference between ${#${foo}} and ${#foo} ?? The following statement is false for ${name:#pattern}, is it not? If the colon is omitted from one of the above expressions containing a colon, then the shell only checks whether name is set or not, not whether it is null. There's something odd here: Arithmetic Expansion A string of the form $[exp] is substituted with the value of the arithmetic expression exp. exp is subjected to parameter expansion, command substitution and arithmetic expansion before ^^^^^^^^^^^^^^^^^^^^^^^^ it is evaluated. See section Arithmetic Evaluation. Is this wrong, or is it just a goofy way of saying that $[exp] can be nested? (Which doesn't seem to be true, so that's not it.) Aside: Filename generation: If you set both NULL_GLOB and NO_NOMATCH, which one wins? What the heck happened to NO_NOMATCH when the change was made to make the prefix "no" into a magic equivalent of "unsetopt"? `setopt nonomatch' should be the same as `unsetopt nomatch', but what about `setopt nomatch'?? Why isn't it `unsetopt match'? Gaahhh. Or did I completely misunderstand what that was all about? Why isn't ***/ mentioned anywhere? That's like **/ except it follows symlinks, correct? Modifiers: One of either the doc or the behavior of the `g' prefix is wrong. The doc says: g Apply the change to the first occurrence of a match in each word, by prefixing the above (for example, g&). In fact, the behavior is that the change is applied to EVERY occurrence of a match in every word; the `w' modifier does only the first in each. (The description above, and not the actual behavior, is what I'd expect from the `g' modifier based on csh, but ....) That's as far as I'm going to get tonight; tomorrow night I might get to read the rest. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.nbn.com/people/lantern New male in /home/schaefer: >N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday" ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 7:30 ` zsh.texi commentary (actually, HTML pages commentary) Bart Schaefer @ 1996-06-21 8:06 ` Zefram 1996-06-21 12:15 ` Zoltan Hidvegi 1996-06-21 12:30 ` Clive Messer 2 siblings, 0 replies; 13+ messages in thread From: Zefram @ 1996-06-21 8:06 UTC (permalink / raw) To: schaefer; +Cc: Z Shell workers mailing list >Aside: Filename generation: If you set both NULL_GLOB and NO_NOMATCH, >which one wins? NULL_GLOB. It actually beats any related option. Just as well too, as this is relied upon in a number of places where NULL_GLOB is temporarily set. > What the heck happened to NO_NOMATCH when the change >was made to make the prefix "no" into a magic equivalent of "unsetopt"? >`setopt nonomatch' should be the same as `unsetopt nomatch', but what >about `setopt nomatch'?? Why isn't it `unsetopt match'? Gaahhh. Or >did I completely misunderstand what that was all about? That patch isn't in the baseline yet. It made the canonical form of that option NOMATCH, so that "setopt NOMATCH", "unsetopt NOMATCH", "setopt NO_NOMATCH" and "unsetopt NO_NOMATCH" are valid. MATCH was not made a legal option. I actually added quite a bit of text explaining this to the zshoptions man page in the patch. -zefram ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 7:30 ` zsh.texi commentary (actually, HTML pages commentary) Bart Schaefer 1996-06-21 8:06 ` Zefram @ 1996-06-21 12:15 ` Zoltan Hidvegi 1996-06-21 12:30 ` Clive Messer 2 siblings, 0 replies; 13+ messages in thread From: Zoltan Hidvegi @ 1996-06-21 12:15 UTC (permalink / raw) To: schaefer; +Cc: clive, mdb, zsh-workers > For the rest of these comments, I don't know which need to change the > man pages, the FAQ, zsh.texi, and/or all of them; but they're all from > reading the HTML at the above URL. Undoubtadly there are things in the manual which is not very clear. Any patches are welcome. > Aside: Question about NO_RCS: > Commands are first read from `/etc/zshenv'. If the -f flag is > given or if the NO_RCS option is set within `/etc/zshenv', all > other initialization files are skipped. > Why doesn't NO_RCS in any init file stop reading of any files that would > normally follow the one where it is set? Or does it, and the doc just > doesn't explicitly say so? No, the documentation is correct. > Shell Grammar section: > > A simple command is a sequence of optional parameter assignments > followed by blank-separated words, > ^^^^^ > Should this read "whitespace" or some such? (Too early to mention $IFS.) IFS is not used for that. I think that blank and whitespace are synonyms. whitespace may also include newline which cannot be used here. > Aside: What's the value of a command executed in the background? E.g. > if false & then echo Hmmm & fi > Is it always consistent? Backgrounded commands always have 0 exit status (that is explicitely mentioned in POSIX 1003.2). > Precommand modifiers, `exec', should explain that the "parent" zsh is > replaced by the exec'd command, as if zsh had exited and the command > was run in its place. Also these are builins now, which is not yet documented. > Aside: Why doesn't `foreach name ( word ... )' need CSH_JUNKIE_PARENS? foreach is a csh command and in csh that is the only way it works as I know. When someone uses foreach he is a already a csh junkie and the shell knows that. > Aside: That it is possible to `disable -r fi' without first disabling > `if', scares the willies out of me. Simliarly for `done' and `esac'. Yes, disable -r should be use very carefully. But I do not think that any change is necessary here. > Aside: Given the above behavior of `disable -r', it'd be nice to be able > to get at the internal tokens for the disabled reserved words. E.g.: > foo() { if true ; then echo This function keeps working ; fi } > alias endif=fi > disable -r fi > bar() { if true ; then echo I wish this still worked ; endif } > Maybe an option to the alias builtin? Aliases realy modify the input to the lexer. I do not think that such a feature is necessary. > The paragraph on Comments still refers to HISTCHARS; it's now histchars. Perhaps I should have mentioned it: I put back HISTCHARS and now both histchars and HISTCHARS can be used. But HISTCHARS is disabled in sh/ksh mode. > Only the "expression" part of identifier=expression is expanded, right? Identifier is also expanded but it contains only letters, numbers and underscore so there is nothing to expand. I think that's clear. > The following statement is false for ${name:#pattern}, is it not? > If the colon is omitted from one of the above expressions > containing a colon, then the shell only checks whether name > is set or not, not whether it is null. Yes, but there the form without a colon is also documented. > There's something odd here: > Arithmetic Expansion > > A string of the form $[exp] is substituted with the value of > the arithmetic expression exp. exp is subjected to parameter > expansion, command substitution and arithmetic expansion before > ^^^^^^^^^^^^^^^^^^^^^^^^ > it is evaluated. See section Arithmetic Evaluation. > Is this wrong, or is it just a goofy way of saying that $[exp] can be > nested? (Which doesn't seem to be true, so that's not it.) It should be possible to nest arithmentic exansions. Unfortunately $[$[...]] does not work, that's a bug, I'll fix it. But $[$((...))] works. > Why isn't ***/ mentioned anywhere? That's like **/ except it follows > symlinks, correct? It is documented in the manual. Zoltan ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 7:30 ` zsh.texi commentary (actually, HTML pages commentary) Bart Schaefer 1996-06-21 8:06 ` Zefram 1996-06-21 12:15 ` Zoltan Hidvegi @ 1996-06-21 12:30 ` Clive Messer 1996-06-21 12:52 ` Zoltan Hidvegi 1996-06-21 17:32 ` Mark Borges 2 siblings, 2 replies; 13+ messages in thread From: Clive Messer @ 1996-06-21 12:30 UTC (permalink / raw) To: schaefer; +Cc: Mark Borges, zsh-workers [-- Attachment #1: Type: TEXT/PLAIN, Size: 2675 bytes --] On Fri, 21 Jun 1996, Bart Schaefer wrote: > On Jun 20, 3:03pm, Mark Borges wrote: > } Subject: Re: zsh-2.6-beta21 released > } > } I've applied this patch and re-generated the html files via > } texi2html-1.50. The URL is still > } > } http://www.mal.com/zsh/Doc/test/ > } > } where zsh.texi.gz is version 2.03. > > I think maybe it should be clearer in the documents that 2.03 is the > version number of the document and not the version of zsh to which it > refers. `Edition 2.0.3' on the TOC page is confusing. OK. 'Edition 2.0.3' -> 'Document Edition 2.0.3'. > For the rest of these comments, I don't know which need to change the > man pages, the FAQ, zsh.texi, and/or all of them; but they're all from > reading the HTML at the above URL. > > I've scattered semi-related thoughts and commentary throughout, usually > prefixed with "Aside:". > > > Intro section: > > <pf@z-code.com> hasn't been a usable address for Paul since almost two > years ago. He's now <pf@software.com>. OK. This is updated. > Spell checking still hasn't happened ... "defauly"? That particular mistake was corrected in 2.0.1, is not in 2.0.2 (in the beta21 dist), so I've no idea why that should still be there if Mark has updated his HTML from 2.0.3. Mark ? > Shell Grammar section: > Spell checking again ... "anexternal" --> "an external". Again, Mark needs to update/fix HTML ???? > Further, the whole section could benefit from some vertical white space > between defined terms. Looks like it's there in the source but gets > squashed out when displayed. I suppose its a texi2html problem (some > strategic <br> need to be output). Yes, the info and printed tex are formatted correctly, so I guess the problem is with texi2html. > The paragraph on Comments still refers to HISTCHARS; it's now histchars. Fixed. > texi2html is still having problems with pairs of single quotes (''), > rendering that as a double quote ("). Having just d/l'd texi2html, the solution to this one would seem to be to run it with the '-expandinfo' option. > Expansion section: > I'd love it if there were more hrefs, e.g. from every reference to an > option name to the description of that option, or from a builtin's name > to its description. E.g., in the sentence: > The PUSHD_MINUS option exchanges the effects of ~+ and ~- > where they are followed by a number. > It'd be great to be able to click on PUSHD_MINUS. I'll give this some thought when I get home this evening. Clive. -- C Messer. Epos Systems. UK. | <clive@epos.demon.co.uk> | "I pressed her thigh and death smiled." <clive@epos.easynet.co.uk> | Jim Morrison. [-- Attachment #2: zsh.texi.diff.2.0.3-4 --] [-- Type: TEXT/PLAIN, Size: 2962 bytes --] --- zsh.texi-2.0.3 Thu Jun 20 00:30:35 1996 +++ zsh.texi Fri Jun 21 13:26:20 1996 @@ -10,13 +10,13 @@ @afourpaper @end iftex -@set EDITION 2.0.3 +@set EDITION 2.0.4 @set VERSION 2.6.21 -@set UPDATED 20 June 1996 +@set UPDATED 21 June 1996 @ifinfo @noindent -Edition @value{EDITION}, last updated @value{UPDATED}, +Document Edition @value{EDITION}, last updated @value{UPDATED}, of @cite{The Z Shell Guide}, for zsh, Version @value{VERSION}. This is a texinfo version of the man page for the Z Shell, originally by @@ -27,13 +27,13 @@ @titlepage @title The Z Shell -@subtitle Edition @value{EDITION} +@subtitle Document Edition @value{EDITION} @subtitle @value{UPDATED} @author Originally by Paul Falstad @page @vskip 0pt plus 1filll @noindent -Edition @value{EDITION}, last updated @value{UPDATED}, +Document Edition @value{EDITION}, last updated @value{UPDATED}, of @cite{The Z Shell Guide}, for zsh, Version @value{VERSION}. This is a texinfo version of the man page for the Z Shell, originally by @@ -169,7 +169,7 @@ @cindex author @noindent -Zsh was originally written by Paul Falstad, @code{pf@@z-code.com}. +Zsh was originally written by Paul Falstad, @code{pf@@software.com}. Programmable completion was implemented by Sven Wischnowsky, @code{oberon@@cs.tu-berlin.de} and Peter Stephenson, @code{P.Stephenson@@swansea.ac.uk}. Richard Coleman, @@ -670,8 +670,8 @@ In non-interactive shells, or in interactive shells with the @code{INTERACTIVE_COMMENTS} option set, a word beginning with the third @pindex INTERACTIVE_COMMENTS, use of -character of the @code{HISTCHARS} parameter (@code{#} by default) causes -@vindex HISTCHARS, use of +character of the @code{histchars} parameter (@code{#} by default) causes +@vindex histchars, use of that word and all the following characters up to a newline to be ignored. @@ -707,10 +707,10 @@ preceding it with a @code{\}. @code{\} followed by a newline is ignored. All characters enclosed between a pair of single quotes @ifinfo -(@code{@'@'}) are quoted, except the first character of @code{HISTCHARS} +(@code{@'@'}) are quoted, except the first character of @code{histchars} @end ifinfo @iftex -(@code{''}) are quoted, except the first character of @code{HISTCHARS} +(@code{''}) are quoted, except the first character of @code{histchars} @end iftex (@code{!} by default). A single quote cannot appear within single quotes. Inside double quotes (@code{""}), parameter and command @@ -6881,3 +6881,6 @@ eg. "-f" to @samp, rather than @code. v2.0.2. June 13th 1996. Several fixes to Programmable Completion. v2.0.3. June 20th 1996. Updated to include changes from 2.6.20 to 2.6.21. +v2.0.4. June 21st 1996. Changed occurances of HISTCHARS to histchars. +Changed mail address for Paul Falstad to pf@software.com. +'Edition' -> 'Document Edition' to save confusion with zsh version. ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 12:30 ` Clive Messer @ 1996-06-21 12:52 ` Zoltan Hidvegi 1996-06-21 15:55 ` Bart Schaefer 1996-06-21 17:32 ` Mark Borges 1 sibling, 1 reply; 13+ messages in thread From: Zoltan Hidvegi @ 1996-06-21 12:52 UTC (permalink / raw) To: clive; +Cc: schaefer, mdb, zsh-workers > > The paragraph on Comments still refers to HISTCHARS; it's now histchars. > > Fixed. That's OK. Although HISTCHARS is valid, histchars is preferred. > > Expansion section: > > > I'd love it if there were more hrefs, e.g. from every reference to an > > option name to the description of that option, or from a builtin's name > > to its description. E.g., in the sentence: > > The PUSHD_MINUS option exchanges the effects of ~+ and ~- > > where they are followed by a number. > > It'd be great to be able to click on PUSHD_MINUS. > > I'll give this some thought when I get home this evening. But these changes should also be made in the manual. Any voulnteers to clean up the manual? The texinfo and the nroff documentation should be updated paralelly. The manual also needs spell checking. I'm quite busy and I think I'm not the best in correcting sylistic problems in English. Zoltan ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 12:52 ` Zoltan Hidvegi @ 1996-06-21 15:55 ` Bart Schaefer 1996-06-21 16:59 ` Zefram 1996-06-21 17:22 ` Clive Messer 0 siblings, 2 replies; 13+ messages in thread From: Bart Schaefer @ 1996-06-21 15:55 UTC (permalink / raw) To: Zefram, Zoltan Hidvegi, clive; +Cc: mdb, Z Shell workers mailing list On Jun 21, 9:06am, Zefram wrote: } Subject: Re: zsh.texi commentary (actually, HTML pages commentary) } } > What the heck happened to NO_NOMATCH when the change } >was made to make the prefix "no" into a magic equivalent of "unsetopt"? } } That patch isn't in the baseline yet. It made the canonical form of } that option NOMATCH, so that "setopt NOMATCH", "unsetopt NOMATCH", } "setopt NO_NOMATCH" and "unsetopt NO_NOMATCH" are valid. So you check for canonical forms before stripping off the leading "no", and then check again after stripping it to invert the sense? Or what? On Jun 21, 2:15pm, Zoltan Hidvegi wrote: } Subject: Re: zsh.texi commentary (actually, HTML pages commentary) } } > Aside: Question about NO_RCS: } > Commands are first read from `/etc/zshenv'. If the -f flag is } > given or if the NO_RCS option is set within `/etc/zshenv', all } > other initialization files are skipped. } > Why doesn't NO_RCS in any init file stop reading of any files that would } > normally follow the one where it is set? Or does it, and the doc just } > doesn't explicitly say so? } } No, the documentation is correct. So then, answer the "Why?" part of the question. } > Precommand modifiers, `exec', should explain that the "parent" zsh is } > replaced by the exec'd command, as if zsh had exited and the command } > was run in its place. } } Also these are builins now, which is not yet documented. Exactly what difference does that make? (Which is part of what ought to be documented ...) } > Aside: Given the above behavior of `disable -r', it'd be nice to be able } > to get at the internal tokens for the disabled reserved words. E.g.: } > foo() { if true ; then echo This function keeps working ; fi } } > alias endif=fi } > disable -r fi } > bar() { if true ; then echo I wish this still worked ; endif } } > Maybe an option to the alias builtin? } } Aliases realy modify the input to the lexer. Yes, I know. I was suggesting, for lack of a better idea, that there be a magic form of lexer input that could force a reference to a disabled reserved word. Anybody have a better idea? It's obviously possible, because functions that were tokenized before the disable still work. } I do not think that such a feature is necessary. Whatever; it was just a suggestion. } > There's something odd here: } > Arithmetic Expansion } > } > A string of the form $[exp] is substituted with the value of } > the arithmetic expression exp. exp is subjected to parameter } > expansion, command substitution and arithmetic expansion before } > ^^^^^^^^^^^^^^^^^^^^^^^^ } > it is evaluated. See section Arithmetic Evaluation. } > Is this wrong, or is it just a goofy way of saying that $[exp] can be } > nested? (Which doesn't seem to be true, so that's not it.) } } It should be possible to nest arithmentic exansions. Unfortunately } $[$[...]] does not work, that's a bug, I'll fix it. But $[$((...))] works. Shouldn't $((...)) be mentioned in the Arithmetic Expansion discussion? Or is it different in some subtle way? } > Why isn't ***/ mentioned anywhere? That's like **/ except it follows } > symlinks, correct? } } It is documented in the manual. I know, but it isn't mentioned in the Filename Generation discussion of the .texi, and I think it should be. On Jun 21, 2:52pm, Zoltan Hidvegi wrote: } Subject: Re: zsh.texi commentary (actually, HTML pages commentary) } } But these changes should also be made in the manual. Any voulnteers to } clean up the manual? The texinfo and the nroff documentation should be } updated paralelly. The manual also needs spell checking. I'm quite busy } and I think I'm not the best in correcting sylistic problems in English. I couldn't promise to have time, unfortunately. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.nbn.com/people/lantern New male in /home/schaefer: >N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday" ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 15:55 ` Bart Schaefer @ 1996-06-21 16:59 ` Zefram 1996-06-21 17:22 ` Clive Messer 1 sibling, 0 replies; 13+ messages in thread From: Zefram @ 1996-06-21 16:59 UTC (permalink / raw) To: schaefer; +Cc: A.Main, hzoli, clive, mdb, zsh-workers >} That patch isn't in the baseline yet. It made the canonical form of >} that option NOMATCH, so that "setopt NOMATCH", "unsetopt NOMATCH", >} "setopt NO_NOMATCH" and "unsetopt NO_NOMATCH" are valid. > >So you check for canonical forms before stripping off the leading "no", >and then check again after stripping it to invert the sense? Or what? Yes. I considered having it check for leading "no" first, but with options NOTIFY and NOMATCH that wouldn't work. >} Also these are builins now, which is not yet documented. > >Exactly what difference does that make? (Which is part of what ought to >be documented ...) That affects "disable exec"/"disable -r exec", and "x=ex; ${x}ec foo". -zefram ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 15:55 ` Bart Schaefer 1996-06-21 16:59 ` Zefram @ 1996-06-21 17:22 ` Clive Messer 1 sibling, 0 replies; 13+ messages in thread From: Clive Messer @ 1996-06-21 17:22 UTC (permalink / raw) To: schaefer; +Cc: Zefram, Zoltan Hidvegi, mdb, Z Shell workers mailing list On Fri, 21 Jun 1996, Bart Schaefer wrote: > } > Why isn't ***/ mentioned anywhere? That's like **/ except it follows > } > symlinks, correct? > } > } It is documented in the manual. > > I know, but it isn't mentioned in the Filename Generation discussion of > the .texi, and I think it should be. Ok. That is fixed as well. I will spend time this weekend checking the texi against the man pages, word for word. Bart: Please point your browser at: http://cust-www.easynet.co.uk/~epos/zsh_toc.html where you will find the latest working copy. Please mail any errors/differences with it and the man-pages to _me_, rather than the whole list, unless the error is also in the man page. > On Jun 21, 2:52pm, Zoltan Hidvegi wrote: > } Subject: Re: zsh.texi commentary (actually, HTML pages commentary) > } > } But these changes should also be made in the manual. Any voulnteers to > } clean up the manual? The texinfo and the nroff documentation should be > } updated paralelly. The manual also needs spell checking. I'm quite busy > } and I think I'm not the best in correcting sylistic problems in English. > > I couldn't promise to have time, unfortunately. Well, if no-one else is volunteering, I will see what time I have spare over the weekend. (BTW, Re: spell checking ... Do we prefer American English or British English ? ;-) Clive. -- C Messer. Epos Systems. UK. | <clive@epos.demon.co.uk> | "I pressed her thigh and death smiled." <clive@epos.easynet.co.uk> | Jim Morrison. ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 12:30 ` Clive Messer 1996-06-21 12:52 ` Zoltan Hidvegi @ 1996-06-21 17:32 ` Mark Borges 1996-06-21 17:45 ` Mark Borges 1 sibling, 1 reply; 13+ messages in thread From: Mark Borges @ 1996-06-21 17:32 UTC (permalink / raw) To: Clive Messer; +Cc: zsh-workers >> On Fri, 21 Jun 1996 13:30:30 +0100 (BST), >> Clive Messer(CM) wrote: CM> On Fri, 21 Jun 1996, Bart Schaefer wrote: >> On Jun 20, 3:03pm, Mark Borges wrote: >> } Subject: Re: zsh-2.6-beta21 released >> } >> } I've applied this patch and re-generated the html files via >> } texi2html-1.50. The URL is still >> } >> } http://www.mal.com/zsh/Doc/test/ >> } >> } where zsh.texi.gz is version 2.03. >> >> I think maybe it should be clearer in the documents that 2.03 is the >> version number of the document and not the version of zsh to which it >> refers. `Edition 2.0.3' on the TOC page is confusing. >> Spell checking still hasn't happened ... "defauly"? CM> That particular mistake was corrected in 2.0.1, is not in 2.0.2 CM> (in the beta21 dist), so I've no idea why that should still be CM> there if Mark has updated his HTML from 2.0.3. Mark ? It's not in my 2.0.2, either. I had to extract the patch to go from 2.0.2 to 2.0.3 with a MIME extraction tool I've never used before, and it was late at night. Apparently I screwed up. My apologies. Anyway, I went back and re-did it (to get to 2.0.4) and these particular problems are fixed now: $ grep defauly *.html $ grep anexternal *.html Maybe the coffee helps ;-). The latest version (2.0.4) is now up at http://www.mal.com/zsh/Doc/test/ where zsh.texi.gz is version 2.03. >> Shell Grammar section: >> Spell checking again ... "anexternal" --> "an external". CM> Again, Mark needs to update/fix HTML ???? Ditto. >> Further, the whole section could benefit from some vertical white space >> between defined terms. Looks like it's there in the source but gets >> squashed out when displayed. I suppose its a texi2html problem (some >> strategic <br> need to be output). CM> Yes, the info and printed tex are formatted correctly, so I guess the CM> problem is with texi2html. Nuts. I'd heard that texi2html did a very good job with the conversion. But apparently it has flaws, too. I'll try to look over the texi2html source and see what can be done. >> texi2html is still having problems with pairs of single quotes (''), >> rendering that as a double quote ("). CM> Having just d/l'd texi2html, the solution to this one would seem to be to CM> run it with the '-expandinfo' option. Thanks, I've done that with this version. -- -mb- ^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: zsh.texi commentary (actually, HTML pages commentary) 1996-06-21 17:32 ` Mark Borges @ 1996-06-21 17:45 ` Mark Borges 0 siblings, 0 replies; 13+ messages in thread From: Mark Borges @ 1996-06-21 17:45 UTC (permalink / raw) To: zsh-workers >> On 21 Jun 1996 11:32:08 -0600, >> Mark Borges(MB) wrote: MB> Maybe the coffee helps ;-). The latest version (2.0.4) is now up at MB> http://www.mal.com/zsh/Doc/test/ MB> where zsh.texi.gz is version 2.03. ^^^^^^^^^^^^ Ack. That should be 2.0.4, of course. Looks like I need another cup. -- -mb- ^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~1996-06-21 17:56 UTC | newest] Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <199606192106.XAA09696@bolyai.cs.elte.hu> 1996-06-19 23:42 ` zsh-2.6-beta21 released Clive Messer 1996-06-20 21:03 ` Mark Borges 1996-06-20 21:05 ` Zoltan Hidvegi 1996-06-21 7:30 ` zsh.texi commentary (actually, HTML pages commentary) Bart Schaefer 1996-06-21 8:06 ` Zefram 1996-06-21 12:15 ` Zoltan Hidvegi 1996-06-21 12:30 ` Clive Messer 1996-06-21 12:52 ` Zoltan Hidvegi 1996-06-21 15:55 ` Bart Schaefer 1996-06-21 16:59 ` Zefram 1996-06-21 17:22 ` Clive Messer 1996-06-21 17:32 ` Mark Borges 1996-06-21 17:45 ` Mark Borges
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).