zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Kalmár Gergely" <kgregory89@gmail.com>
Cc: Roman Perepelitsa <roman.perepelitsa@gmail.com>, zsh-workers@zsh.org
Subject: Re: --init-file option
Date: Mon, 13 Feb 2023 13:46:03 -0800	[thread overview]
Message-ID: <CAH+w=7aRM++g6yuWbPBaU-n2-uKdAu_=ih60zwVMeF24XF+iGQ@mail.gmail.com> (raw)
In-Reply-To: <CAKue2cRDk0j_4jPmQd6rQxb3utc5N=BvS0jDSrOXVASLbDcyqQ@mail.gmail.com>

On Mon, Feb 13, 2023 at 12:59 PM Kalmár Gergely <kgregory89@gmail.com> wrote:
>
> Yes, I could do something similar as what zshi does, but that seems like a suboptimal solution, because it would require a duplication (and indefinite maintenance) of the startup file processing logic in an independent codebase.

I don't follow that at all.  You're keeping the file for --init-file
somewhere now (I presume), so why would pointing ZDOTDIR at it require
a new codebase?

Anyway "bash --init-file" replaces (both global and user) bashrc
rather than run the file after them, which doesn't match what you
originally asked for.  Does it  in fact do what you want?

Does your file need to create internal variables or functions, or is
it just populating the environment?


  reply	other threads:[~2023-02-13 21:46 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
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 [this message]
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:
  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=7aRM++g6yuWbPBaU-n2-uKdAu_=ih60zwVMeF24XF+iGQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=kgregory89@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).