search

prati0100 / git-gui

Tcl/Tk based UI for Git. I am currently acting as the project's maintainer.
161 stars 87 forks source link

Git GUI Documentation Missing #40

Open JessIAm opened 3 years ago

JessIAm commented 3 years ago

All the documentation links point to GIT manuals. I can't find how to add tools through the GUI.

I'm trying to all Open Office Text as a tool to my Git Gui 0.21.GITGUI. I'm writing a book in *.doc, and want to use code line management on it.

Note: this is my first post on this github.com. Apologies if this is covered somewhere that I couldn't find. I searched throughout the site as much as I could.

Thanks!

prati0100 commented 3 years ago

Hi @JessIAm,

Yes, git-gui does not have very good documentation. The point has been raised before but I, or someone else, have not been able to get any meaningful progress done.

Coming to your use case, I am not very familiar with Open Office Text format, but if I understand correctly, it is not a text based format. It is a binary format instead. Git works best with plain text since the tool was written to version source code. While you can use binary files with it, some parts like diff will not work properly.

If you are still convinced that Git is the right tool for you, then please explain in detail what part you are confused with and I will help you through it. What exactly do you mean by "tools"? What do you intend to do with those tools? All this context will be helpful in finding the right answers.

PhilipOakley commented 3 years ago

One option is to use panadoc as a filter for the stored open doc to convert it into text for diff comparison within Git.

I've not tried it myself, but have seen it suggested before for those using awkward formats (relative to Git's line oriented utf8 text expectation..)