Well-Known Tool Configurations #3280
halostatue
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
Hmm, I think it would be sufficient to provide examples in the documentation of how set At a higher level, I'm keen that chezmoi provides mechanism, not policy. For example, chezmoi provides a mechanism to plug in external diff and merge tools, but (other than having sensible defaults) no policy limiting your choice of tool. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I wonder if it would be worthwhile adding support for well-known tool configurations. The default configuration for
merge
isvimdiff
and the default configuration fordiff
isdiff -u
, but I wonder if it would be worthwhile to make it easier to support specific tools like Emacs, VS Code, Meld, Kaleidoscope, Beyond Compare, etc. Maybe instead ofmerge.command
it would bemerge.tool
with a string-enum value that holds those. Or we add a new section to the documentation with configurations for those.This is inspired by #3279, but is not wholly restricted to just
diff
andmerge
, although those are the only ones that I can think of because I just replied to that one.The biggest argument against this would be deciding when a new tool would justify being added to either the
.tool
list or documentation. We don't necessarily want to support All The Tools, just the ones that are more likely to be used than not.Beta Was this translation helpful? Give feedback.
All reactions