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
Using tig 2.2 or 2.3.0 the CWD is ignored to qualify relative paths if GIT_DIR is set; all paths must be given relative to the GIT_WORK_TREE it seems. This is annoying, particularly with vcsh (that sets a GIT_DIR inside ~/.config with a GIT_WORK_TREE of ~/), and is not what git-log does. Example:
cd~
vcsh init test
vcsh test add .config/tig/tigrc
vcsh test commit -m 'tigrc'
vcsh test tig -- .config/tig/tigrc # shows the commit
vcsh test log -- .config/tig/tigrc # does not show anythingcd .config/
vcsh test tig -- tig/tigrc # fails (No revisions match the given arguments.)
vcsh test log -- tig/tigrc # shows the commit
vcsh test tig -- .config/tig/tigrc # shows the commit
vcsh test log -- .config/tig/tigrc # does not show anything
The text was updated successfully, but these errors were encountered:
When running tig as a git alias, git will chdir(GIT_WORK_TREE) and pass the subdirectory tig was invoked in as GIT_PREFIX. So the fix is to chdir(GIT_PREFIX).
Using tig 2.2 or 2.3.0 the CWD is ignored to qualify relative paths if GIT_DIR is set; all paths must be given relative to the GIT_WORK_TREE it seems. This is annoying, particularly with vcsh (that sets a GIT_DIR inside ~/.config with a GIT_WORK_TREE of ~/), and is not what git-log does. Example:
The text was updated successfully, but these errors were encountered: