From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Martin Tournoij" <martin@arp242.net>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] add cdtohome setting
Date: Sat, 08 Jun 2024 03:37:59 -0400 [thread overview]
Message-ID: <9070b9a6-268b-47a2-96ce-627e48aa6939@app.fastmail.com> (raw)
In-Reply-To: <3bc6f058-4394-4b64-bd2e-44f7efbd5688@app.fastmail.com>
On Sat, Jun 8, 2024, at 1:51 AM, Martin Tournoij wrote:
> A small patch to add a tcsh setting I miss.
I don't have a strong initial opinion on whether this should be
accepted or not, but...
> -Change the current directory. In the first form, change the
> -current directory to var(arg), or to the value of tt($HOME) if
> -var(arg) is not specified. If var(arg) is `tt(-)', change to the
> -previous directory.
> +Change the current directory. In the first form, change the current
> +directory to var(arg), or to the value of tt($HOME) if var(arg) is not
> +specified unless the tt(CD_TO_HOME) option is not set, in which case
> +var(arg) is required. If var(arg) is `tt(-)', change to the previous
> +directory.
I don't love how many negatives and chained clauses are jammed into
this one sentence. I think something like this would be clearer:
In the first form, change the current directory to var(arg)
or to the value of tt($HOME) if var(arg) is omitted and the
tt(CD_TO_HOME) option is set; if tt(CD_TO_HOME) is unset,
var(arg) is required.
> +pindex(CD_TO_HOME)
> +pindex(NO_CD_TO_HOME)
> +pindex(CDTOHOME)
> +pindex(NOCDTOHOME)
> +item(tt(CD_TO_HOME))(
> +Don't go to home when using tt(cd) without any arguments.
Isn't it the other way around? The option *enables* operand-less
cd to go $HOME. (Not argument-less, because options are arguments.)
Maybe:
If set, a tt(cd) command without operands changes the
current directory to the value of tt($HOME). If unset,
tt(cd) requires at least one operand.
--
vq
next prev parent reply other threads:[~2024-06-08 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 5:51 Martin Tournoij
2024-06-08 7:37 ` Lawrence Velázquez [this message]
2024-06-08 11:59 ` Mikael Magnusson
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=9070b9a6-268b-47a2-96ce-627e48aa6939@app.fastmail.com \
--to=larryv@zsh.org \
--cc=martin@arp242.net \
--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).