zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [PATCH] More doc for zsh/ksh93
Date: Sun, 5 Mar 2023 15:44:35 -0800	[thread overview]
Message-ID: <CAH+w=7bxKbUTdECy1YjavfNLX2mBx0sOD3Oge-u6oJnx9uYbkw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 88 bytes --]

Shuffled some things around, made mention of more ksh features that
aren't implemented.

[-- Attachment #2: ksh93-doc-update.txt --]
[-- Type: text/plain, Size: 3365 bytes --]

diff --git a/Doc/Zsh/mod_ksh93.yo b/Doc/Zsh/mod_ksh93.yo
index 3ae644bd1..d58b979b9 100644
--- a/Doc/Zsh/mod_ksh93.yo
+++ b/Doc/Zsh/mod_ksh93.yo
@@ -118,23 +118,6 @@ The following features of ksh93 are not currently supported but may be
 available in a future release.
 
 startitem()
-item(var(pathdir)tt(/.paths))(
-Each directory var(pathdir) in the tt(PATH) parameter may contain a
-text file `tt(.paths)' which may define additional directories to
-be searched for function definitions (tt(FPATH)), external executables
-(tt(PATH)), and plugin files (similar to tt(MODULE_PATH)).
-
-em(THIS FEATURE IS UNLIKELY EVER TO BE IMPLEMENTED.)
-)
-item(tt(builtin -f )var(file))(
-Installs a new shell builtin command dynamically linked from var(file),
-where var(file) is found by a path search and the base name of the file
-is the name of the builtin to be added.
-
-Similar to `tt(zmodload -F zsh/)var(file)tt( +b:)var(file)'.
-
-em(THIS FEATURE IS UNLIKELY EVER TO BE IMPLEMENTED.)
-)
 item(tt(namespace )var(ident)tt( { )var(list)tt( }))(
 This reserved word executes the current shell compound command
 tt({ )var(list)tt( }), with the special behavior that all functions
@@ -208,4 +191,58 @@ of `tt($LPAR())var(list)tt(RPAR())' but without forking.
 
 em(THIS FEATURE IS NOT YET IMPLEMENTED.)
 )
+item(tt(typeset -C )var(name)[tt(=)var(values)tt( ...)])(
+Creates a em(compound variable).
+
+em(THIS FEATURE IS NOT YET IMPLEMENTED, and the syntax of var(values)
+is unlikely to be fully ksh compatible.)
+)
+enditem()
+
+subsect(Other Differences)
+
+The following features of ksh93 are not currently supported and there are
+no plans to implement them.
+
+startitem()
+item(var(pathdir)tt(/.paths))(
+Each directory var(pathdir) in the tt(PATH) parameter may contain a
+text file `tt(.paths)' which may define additional directories to
+be searched for function definitions (tt(FPATH)), external executables
+(tt(PATH)), and plugin files (similar to tt(MODULE_PATH)).
+
+em(THIS FEATURE IS UNLIKELY EVER TO BE IMPLEMENTED.)
+)
+item(tt(builtin -f )var(file))(
+Installs a new shell builtin command dynamically linked from var(file),
+where var(file) is found by a path search and the base name of the file
+is the name of the builtin to be added.
+
+Similar to `tt(zmodload -F zsh/)var(file)tt( +b:)var(file)'.
+
+em(THIS FEATURE IS UNLIKELY EVER TO BE IMPLEMENTED.)
+)
+item(tt(typeset -H )var(name)[tt(=)var(value)])(
+Used for em(host-name file mapping) on some operating systems.
+
+em(THIS FEATURE IS UNLIKELY EVER TO BE IMPLEMENTED.)
+)
+item(tt(typeset ){tt(PLUS()|-)}tt(M )var(mapname)tt( )var(name)[tt(=)var(value)])(
+Declares a character translation var(mapname) for values assigned to var(name).
+)
+xitem(tt(typeset -S))
+xitem(tt(typeset -T ) [tt(-f)] [ var(tname)tt(=LPAR())var(values)tt(RPAR()) ])
+item(tt(typeset -h )var(str))(
+Used to define em(typed variables) and properties of their em(sub-variables).
+The tt(-T) and tt(-h) options conflict with existing zsh usage.
+)
+item(tt(typeset -X )var(name)[tt(=)var(value)])(
+Declares a floating-point variable displayed in hexadecimal format.
+)
+item(tt(typeset -b )var(name)[tt(=)var(value)])(
+Declares a parameter stored in em(base64) format.
+)
+item(tt(typeset -m )var(newname)tt(=)var(oldname))(
+em(Moves) var(oldname) to var(newname).  Conflicts with native zsh usage.
+)
 enditem()

                 reply	other threads:[~2023-03-05 23:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAH+w=7bxKbUTdECy1YjavfNLX2mBx0sOD3Oge-u6oJnx9uYbkw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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).