help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: "Kalmár Gergely" <kgregory89@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: --init-file option
Date: Mon, 13 Feb 2023 12:24:12 +0100	[thread overview]
Message-ID: <CAN=4vMqxKA6yzJgfJZ5cCRT8htPL9pi1NYpeeb+fws04oK3+kQ@mail.gmail.com> (raw)
In-Reply-To: <CAKue2cS2c8TuUgWQxOYjgJ9pEnGb7mx-9RZRD-FnWO2afmvv8g@mail.gmail.com>

On Mon, Feb 13, 2023 at 11:58 AM Kalmár Gergely <kgregory89@gmail.com> wrote:
> I was wondering if there is an equivalent to Bash's --init-file
> option or fish shell's --init-command option in Zsh or if one can
> hack around to achieve the same effect. I would need to be able to
> source a virtual environment activation file after the Zsh startup
> files were processed (but before a command is executed) in order to
> be able to start a shell or run commands inside a Python virtual
> environment.

If you are executing a script or a command, then instead of this:

    zsh foo
    zsh -c 'foo'

you can do this:

    zsh -c 'source /path/to/your/file; foo'

If you need to start an interactive zsh that sources an extra file
after the usual startup files, and if you cannot modify any of the
standard startup files, then https://github.com/romkatv/zshi or
something like it is the only option. Disclaimer: It's my project but
I'm not using this code myself.


This question is more suitable for zsh-users than zsh-workers.

  reply	other threads:[~2023-02-13 11:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 10:57 Kalmár Gergely
2023-02-13 11:24 ` Roman Perepelitsa [this message]
2023-02-13 13:43   ` Kalmár Gergely
2023-02-13 20:28     ` Bart Schaefer
2023-02-13 20:34       ` Roman Perepelitsa
2023-02-13 20:59         ` Kalmár Gergely
2023-02-13 21:46           ` Bart Schaefer
2023-02-14 10:18             ` Kalmár Gergely

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN=4vMqxKA6yzJgfJZ5cCRT8htPL9pi1NYpeeb+fws04oK3+kQ@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=kgregory89@gmail.com \
    --cc=zsh-workers@zsh.org \


* 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


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).