From: Parke <parke.nexus@gmail.com>
To: dash@vger.kernel.org
Subject: Re: dash unset idiosyncrasies
Date: Mon, 6 Jul 2015 09:02:57 -0700 [thread overview]
Message-ID: <CAPxz1+bDwhGNBzv-b5cD6iML6jTkNbRLjJT-hsVCgk3pOWVsYw@mail.gmail.com> (raw)
In-Reply-To: <CAPxz1+Zuye=Oj=tWvto9_ir5XcgazBY=2asesR77qRrFuTbc2A@mail.gmail.com>
On Sun, Jul 5, 2015 at 7:18 PM, Parke <parke.nexus@gmail.com> wrote:
> Based on my experiments, I would recommend the dash man page be
> changed as follows. Changes are in capital letters.
>
> unset [-fv] name ...
> The specified VARIABLES OR FUNCITONS
> (BUT NOT BOTH) are
> unset and unexported. If -f or -v is speci‐
> fied, the corresponding functionS or variableS
> ARE unset, respectively. IF NEITHER OPTION
> IS GIVEN, ONLY THE NAMED VARIABLES
> ARE UNSET.
I just realized that, perhaps most importantly, the first line should
be changed to:
unset [ -f | -v ] name ...
Cheers,
Parke
prev parent reply other threads:[~2015-07-06 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 2:18 dash unset idiosyncrasies Parke
2015-07-06 3:23 ` Martijn Dekker
2015-07-06 16:02 ` Parke [this message]
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=CAPxz1+bDwhGNBzv-b5cD6iML6jTkNbRLjJT-hsVCgk3pOWVsYw@mail.gmail.com \
--to=parke.nexus@gmail.com \
--cc=dash@vger.kernel.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).