zsh-workers
 help / color / mirror / code / Atom feed
From: Ben Woods <woodsb02@gmail.com>
To: zsh-workers@zsh.org
Cc: adamw@freebsd.org
Subject: --enable-etcdir for multiple locations (similar to PATH)
Date: Thu, 23 Jun 2016 12:14:17 +0200	[thread overview]
Message-ID: <CAOc73CDmw2uRuMReVoon-ncnPB-zqYi37x9T-wcqQZ_WdDccKw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

Hi everyone,

I am wondering if it is possible to tell zsh to look in multiple different
locations for it's startup/shutdown configuration files?

I believe it is possible to change the location that it will look for them
at compile time with --enable-etcdir=INSERTDIRHERE. However, zsh then does
not look for the config files in the default /etc/ directory anymore - only
the newly specified directory.

As an example, it would be good if zsh could be configured at compile time
with a list of directories to search for config files in. If /usr/local/etc
is added to the list, it would look for /etc/zshrc and if it is not found,
it would look for /usr/local/etc/zshrc. The priority would be in the order
they were specified in the compile time flag (similar to PATH) - or they
could even both be read and compound each other.

This is important, because in FreeBSD, configuration files for ports are
not supposed to be in /etc, but in /usr/local/etc. However, we are aware
that many people with read the official zsh documentation at the link below
and try to put the configuration files in /etc.
http://zsh.sourceforge.net/Doc/Release/Files.html

Thanks for your help.

Regards,
Ben

--
From: Benjamin Woods
woodsb02@gmail.com

             reply	other threads:[~2016-06-23 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 10:14 Ben Woods [this message]
2016-06-23 23:09 ` Bart Schaefer
2016-06-27  8:38   ` Ben Woods

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=CAOc73CDmw2uRuMReVoon-ncnPB-zqYi37x9T-wcqQZ_WdDccKw@mail.gmail.com \
    --to=woodsb02@gmail.com \
    --cc=adamw@freebsd.org \
    --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).