When trying to incorporate large aliases into my ~/.gitconfig file via `git config --global "!$(cat myscript)"`, I determined that there appears to be a limit to the size of a value. When exceeded, git prints out "fatal: bad config file line 82 in ~/.gitconfig". I was able to strip enough comments and such from myscript that it then no longer invalidated the config once the value was less than 1024 chars. (Minor aside, I am doing this as a small experiment to potentially aid in synchronizing all my git behaviors across machines by inlining them into the config file. Whether this is a good path to explore or not is a separate issue.) My questions are: Is this 1024 char limit on config file values documented somewhere? Should it be considered a bug that git config can write out config files which it can not then read (e.g. it should be changed to either enforce the value-length limit during writing, or the parser updated to handle large values)? Thanks, Jeff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html