You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 8, 2024. It is now read-only.
Please reconsider support for $GIT_DIR in gina.vim. Concrete use case:
The vcsh tool for versioning $HOME is designed to overlay several managed git repositories on the user's home directory. It works very well. Example:
>echo$GIT_DIR# nothing> vcsh vim
# now in a subshell with $GIT_DIR set>echo$GIT_DIR
/Users/foo/.config/vcsh/repo.d/vim.git
> git status
# ... status of vim repo ...
Only $GIT_DIR is set by vcsh. There are some similar tools that also use $GIT_DIR to manage this style of work.
Related to #130. IMO, I feel like the prior issue overcomplicated things. Fugitive, for example, does handle $GIT_DIR and $GIT_WORK_TREE, but not $GIT_COMMON_DIR. I'm not aware of any user tooling that uses $GIT_COMMON_DIR. I attempted to search GitHub looking for examples, but found only git scripting and git-* tools (outside of git forks).
The text was updated successfully, but these errors were encountered:
Please reconsider support for
$GIT_DIR
in gina.vim. Concrete use case:The vcsh tool for versioning $HOME is designed to overlay several managed git repositories on the user's home directory. It works very well. Example:
Only $GIT_DIR is set by vcsh. There are some similar tools that also use $GIT_DIR to manage this style of work.
Related to #130. IMO, I feel like the prior issue overcomplicated things. Fugitive, for example, does handle
$GIT_DIR
and$GIT_WORK_TREE
, but not$GIT_COMMON_DIR
. I'm not aware of any user tooling that uses$GIT_COMMON_DIR
. I attempted to search GitHub looking for examples, but found only git scripting andgit-*
tools (outside of git forks).The text was updated successfully, but these errors were encountered: