summaryrefslogtreecommitdiff
path: root/contrib/convert-objects/convert-objects.c
diff options
context:
space:
mode:
authorLibravatar Jonathan Nieder <jrnieder@gmail.com>2012-03-31 03:42:34 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-03-31 11:14:26 -0700
commit4e0ce4dfea869cfe383149a3db5a430f0579c3f4 (patch)
tree1e78053f79b0cfe78d5c103000a5885f13798f03 /contrib/convert-objects/convert-objects.c
parentGit 1.7.9 (diff)
downloadtgif-4e0ce4dfea869cfe383149a3db5a430f0579c3f4.tar.xz
var doc: default editor and pager are configurable at build time
Some distributors customize the fallback pager and editor used by git commands when the user has not indicated a preference via the core.editor/core.pager configuration or GIT_EDITOR, GIT_PAGER, VISUAL, EDITOR, and PAGER environment variables, and git's build system provides DEFAULT_PAGER and DEFAULT_EDITOR makefile settings to help them with that (see v1.6.6-rc0~24, 2009-11-20). Unfortunately those compile-time settings do not affect the documentation, so the uninitiated user who tries to understand git by reading the git-var(1) manpage can easily be confused when git falls back to 'nano' and 'more' instead of 'vi' and 'less'. Even if the distributor patches the distributed docs to reflect the new default, the user may read the official documentation from the git-htmldocs repository online and be confused in the same way. Add a few words stating that the defaults are customizable at compile time to make the behavior crystal clear. Reported-by: Rodrigo Silva (MestreLion) <linux@rodrigosilva.com> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/convert-objects/convert-objects.c')
0 files changed, 0 insertions, 0 deletions