From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: -C -like option to change CWD on startup
Date: Thu, 2 Feb 2023 09:31:41 +0000 [thread overview]
Message-ID: <CAKc7PVA+z_zZu6YjtB-4a7En45XcKy1m3GWMhYtfzjuxVMEpGA@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMpm=cHbt05rOQZLkRZctKc=t+jocZ4rWsgmziBs_sK5Bw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
thanks for the interesting example. I would want to note two other programs
that follow -C option convention, namely tar and env. The second can be
even used to workaround the problem, i.e.:
env -C ~/github zsh -c 'some commands'
but still, a dedicated option would be good.
On Thu, 2 Feb 2023 at 09:05, Roman Perepelitsa <roman.perepelitsa@gmail.com>
wrote:
> On Thu, Feb 2, 2023 at 9:57 AM Sebastian Gniazdowski
> <sgniazdowski@gmail.com> wrote:
> >
> > Hi,
> > make and git have the -C option which works like:
> > (
> > builtin cd -q $COPT
> > git/make "$@"
> > )
> >
> > I think that it is very useful, because no lengthy subshell is needed.
> Zsh doesn't have such option, could it be added? It's pitty that -C is
> already used by NO_CLOBBER, but maybe some other letter is free (I didn't
> found any)?
>
> You can do this:
>
> zsh-in-dir() ( builtin cd -q -- "$1" && builtin exec zsh "${@:2}" )
>
> This forks and execs once, the same as if there was a native `-C dir`
> option.
>
> Note that your original code has the same performance thanks to an
> optimization in zsh. The second fork is elided.
>
> Roman.
>
--
Best regards,
Sebastian Gniazdowski
[-- Attachment #2: Type: text/html, Size: 2187 bytes --]
prev parent reply other threads:[~2023-02-02 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 8:55 Sebastian Gniazdowski
2023-02-02 9:05 ` Roman Perepelitsa
2023-02-02 9:31 ` Sebastian Gniazdowski [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=CAKc7PVA+z_zZu6YjtB-4a7En45XcKy1m3GWMhYtfzjuxVMEpGA@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=roman.perepelitsa@gmail.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).