|
 |
Finally some good news on the Git front! My life is starting to ease up
a bit.
I found myself confused over what changes I made between a couple of
branches last month, so I tried to use the Diff Branches feature of
Git-Cola. But I couldn't figure out what Git-Cola was diffing. Some
blob in the /tmp directory doesn't really tell me what it's looking at.
So I did a git diff from the command line. Problem is, it piped the
output into Less. Sorry, but I've been spoiled by GUIs since the late
1980s, and find terminal apps such as Less a bit clunky.
So, after a futile attempt to find clear instructions about Git-Cola
online, I went back to Git-Cola to try to figure things out myself. But
everything I tried showed a comparison of I-don't-know-what to some
*previous* commit (and I only knew *that* due to a change I did remember
making), which was not what I wanted.
Then Captain Obvious whispered to me: just go back to the CLI and see if
redirecting git diff into a text file would lose the Less pipe! It
worked. I can now just peruse the differences with my GUI text editor.
One of the things I appreciate about Git-Cola is how seamlessly it works
with Git. I can go back and forth between Git-Cola and the CLI at will.
Post a reply to this message
|
|
|
|
hi,
Cousin Ricky <ric### [at] yahoo com> wrote:
> ... Problem is, it piped the output into Less.
you mean 'less', yes ?
Sorry, but I've been spoiled by GUIs since the late
> 1980s, and find terminal apps such as Less a bit clunky.
wondering which use of "spoiled", ie "(transitive) To ruin the character of, by
overindulgence; to coddle or pamper to excess", or "(transitive) To ruin; to
damage in such a way as to make undesirable or unusable" you had in mind ?
surely not "to become sour".. </grin>
so, using your usual method, if you want to look at the contents of a zip file
(not extract it), what program do you use ? or you want to look at a '.tar',
more common on GNU/Linux, perhaps compressed, again, not wanting to extract.
which program ? if you want to read a compressed text file, say .gz or .xz,
which program do you use ? or you want to quickly read some part of a PDF,
which program do you open ? or, say, you are reading through some program
source (in your viewer) and spot a typo, can you edit it ?
'less' lets me do all of the above, including invoking the editor with the
cursor pretty near the "offending" bit (if it was approx centre of 'less' view).
and all w/out a single rodent click, "hands on keyboard" ;-).
regards, jr.
Post a reply to this message
|
|
