From: Larry Schrof <larrys@fb.com>
To: "zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Please implement auto-handling of ${HOME}/.zsh/
Date: Wed, 20 Mar 2013 19:16:39 +0000 [thread overview]
Message-ID: <ED2B935DE024BE43B79F5C1268FCE9EB58E59561@PRN-MBX01-2.TheFacebook.com> (raw)
I have been dying for this for many years. I have a ton of zsh configs,
so I like to organize them in ~/.zsh/ , but here's the problem.
First, I have to create a symlink ~/.zshenv and point it to ~/.zsh/.zshenv
Then, as the first thing to do in ~/.zsh/.zshenv, I have to do:
export ZDOTDIR=${HOME}/.zsh
This is janky and is messier than it needs to be.
It would be awesome if something like the following happened. Forgive me
if the implementation is flawed; just note the spirit of my suggestion.
- Before zsh begins to process the first user-based config file
(I believe ~/.zshenv), look for the existence of ~/.zsh/ (a directory).
- If this directory does not exist, proceed normally. (Start reading
~/.zshenv)
- If this directory DOES exist:
---> Automatically set ZDOTDIR to ${HOME}/.zsh/
---> Ignore any ~/.zsh* files (If the user is using ~/.zsh/ it's their job
to
understand that ~/.zsh* files won't be read.)
--> Begin reading ${HOME}/.zsh/.zshenv
What's the likelihood this would be implemented in the near future?
next reply other threads:[~2013-03-20 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 19:16 Larry Schrof [this message]
2013-03-20 19:54 ` Moritz Bunkus
2013-03-20 20:55 ` Paul Hoffman
2013-03-20 21:25 ` TJ Luoma
2013-03-21 5:41 ` Bart Schaefer
2013-03-21 12:05 ` Richard Hartmann
2013-03-21 8:17 ` Axel Beckert
2013-03-21 12:03 ` Richard Hartmann
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=ED2B935DE024BE43B79F5C1268FCE9EB58E59561@PRN-MBX01-2.TheFacebook.com \
--to=larrys@fb.com \
--cc=zsh-users@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).