Buy this Domain

Community Discussions

Explore the latest discussions and community conversations related to this domain.

Anyone know the value of my old original 1998 GT Show? And any other GT Show owners out there? Been getting this out of the garage lately and getting back into it and loving it.

Main Post: Anyone know the value of my old original 1998 GT Show? And any other GT Show owners out there? Been getting this out of the garage lately and getting back into it and loving it.

Top Comment:

Yep that’s about 2k

Forum: r/flatland

Git branch show empty when I checkout a new branch : git

Main Post: Git branch show empty when I checkout a new branch : git

Forum: r/git

Is there any way have git diff show that a file was moved, instead of removed and added

Main Post:

I am looking for a way to display this, and I know that git knows that information because when you move a file it shows up as renamed and what percent of the file content was moved.

Edit: My initial question wasn't really helpful. I'm trying to work through a large refactor merge and would like to see if a bunch of files that were renamed also had additional changes to their content.

I think the simplest recreation of the situation is this

mkdir tmp cd tmp git init echo "Hello" > first git add first git commit -m "first entry" git checkout -b "moving" git mv first second git commit -m "Moved"

Git knows that the file was just renamed, but if I just run git diff --summary master moving it says I deleted first and created second.

Edit 2: Thanks, Dr. Krieger, git diff -M --summary master moving was what I was looking for

Top Comment: git diff --summary

includes rename/move information. Note that git doesn't "know" it, it's guessing based on how similar the files are.

Forum: r/git

Is there some gui tool which can show files locked in lfs?

Main Post:

Hi, I'm trying to convince my boss to switch from perforce to Git for future projects. The biggest obstacle I'm facing is locking binary files. That's a must. I've got a Gitea setup with lfs. Everything is working fine(including locks), but it is only really usable from command line. It looks like none of the Guis for Git can handle locks in some user friendly way. In most of them(Sourcetree, TortoiseGit, Giteye, Gitkraken, Git Cola, Giggle) there's not even an option to lock the file. The only one I've found which has an option to create lfs lock from GUI is Gitahead. But you cannot see which files are locked anyway and you find out that another user has the file locked only on pre-commit hook(which is quite useless).

Basically the only thing I need is a program which would check "git lfs locks" and show it in the UI. It baffles me why none of the programs can do that. The tool does not have to be free, because the perforce license is crazy expensive.

Top Comment: Try SmartGit. It supports locking of git lfs files, so it might view the status in the ui. If not, ask the developers on user echo if they might implement it.

Forum: r/git

lazygit is not using the "delta" pager to show git diff

Main Post:

As shown below,

  • I can see the diff of a local git repo using git diff with delta as the pager in the terminal.
  • However, lazygit doesn't show this diff in the delta style although I have specified delta as its pager.

My .gitconfig and config.yml for lazygit are shown below.

Strangely, the same configuration works in Mac OS with git diff highlighted with delta in both command line and lazygit....

May I ask what important steps I may have missed here?

Thanks.

git diff as highlighted by delta in the terminal git diff as shown in lazygit with delta as its pager specified

My ~/.gitconfig

[user] name = USER email = [email protected] [core] pager = delta [interactive] diffFilter = delta --color-only --features=interactive [delta] navigate = true light = false side-by-side = true line-numbers = true features = decorations [delta "interactive"] keep-plus-minus-markers = true [delta "decorations"] commit-decoration-style = blue ol commit-style = raw file-style = omit hunk-header-decoration-style = blue box hunk-header-file-style = red hunk-header-line-number-style = "#067a00" hunk-header-style = file line-number syntax [merge] conflictstyle = diff3 [diff] colorMoved = default

My ~/AppData/Roaming/lazygit/config.yml

git: paging: colorArg: never pager: delta --dark --paging=never # pager: ydiff -p cat -s --wrap --width={{columnWidth}} useConfig: false

I also have the latest lazygit and delta installed via scoop:

My system: Windows 11, 64bit

Top Comment: The documentation is clear. It's supported https://github.com/jesseduffield/lazygit/blob/master/docs/Custom_Pagers.md I would recommend you to open a ticket on github on lazygit repository. I don't think this sub is about helping you to with this specific configuration on a tool that provides a GUI for git. Most people here are not using the tool you talk about or using windows, so I'm not sure how you could get help here. But first, and by experience I would say you either have a PATH issue when calling delta in the lazygit conf, or the config file you expect lazygit to open is not the right one (wrong path, .yaml vs .yml, anything Murphy's law can provide). One solution is to try change another setting in lazygit and see if it works. Please note you may already have tried this, and then I can only recommend you to open a bug ticket on lazygit github repository

Forum: r/git

Git blame "show commit message"

Main Post:

I'm using vim-fugitive and often when I'm working I ask the question:

"What does this line do again?"

So I want a similar output as git blame but the hash of the commit isn't useful to me. I just use it up to go look at the commit log message summary. Is there a way to print the lines of git blame but instead of having the hash and person who committed, you'd have the commit log message summary?

If git does provide this function, is it also possible in vim-fugitive?

Top Comment: No, git blame itself doesn't have the ability to provide custom formatting for its output. But it does have a "porcelain" output with which external tools can format it. Here's something I've just cooked up: #!/bin/bash set -o errexit set -o nounset set -o pipefail declare sha line key value declare -A kv unset GIT_PAGER [[ -t 1 ]] && GIT_PAGER=$(git var GIT_PAGER || :) unset abbrev abbrev=$(git config core.abbrev || :) [[ $abbrev == +([0-9]) ]] || abbrev=10 git blame --line-porcelain "$@" | { while read -r sha _; do kv=() unset line while IFS= read -r line; do [[ $line != $'\t'* ]] || break read -r key value <<<"$line" kv[$key]=$value done [[ -n ${line:+set} ]] || break printf "%-${abbrev}.${abbrev}s (%-40.40s) %s\\n" "$sha" "${kv[summary]:-}" "${line#$'\t'}" done } | eval "${GIT_PAGER:-cat}" Drop this into your path under some useful name, git-better-blame for example, and you could use it in place of git blame. It's undergone only very minimal testing, and I can think of a few ways it will definitely break horribly, but maybe it will be useful for you. The kv associative array ends up being populated with a whole bunch of useful info, so you might be able to find the bits that interest you most there.

Forum: r/git

What is the difference between git log and git show?

Main Post: What is the difference between git log and git show?

Top Comment: git show is primarily for showing a single commit. It defaults to a verbose display, including the entire diff. It can also show other, non-commit objects. git log is primarily for showing a range of commits. It defaults to only showing the commit message, and can be reduced to one line. Both take similar options for the format. You can, with an appropriate command line, persuade git log to display a single commit with full diff just like git show.

Forum: r/git

Is there a way to use 'git show' on staged changes?

Main Post:

I'm trying to implement my own version of git diff (long story), but I'm stuck on how to deal with staged changes.

I have a tool that compare two files (they're not text files), and I've been using git show commit:path/to/file to get the file from one commit to compare to another, but I'm not sure how I can do this for staged changes?

(And yes I'm aware of git difftool, like I said long story).

Top Comment: Found an answer! Leaving this up in case others stumble upon it https://stackoverflow.com/questions/5153199/git-show-content-of-file-as-it-will-look-like-after-committing

Forum: r/git

Using git show to export files

Main Post:

I know the file exists at the specific commit because I can successfully do `git checkout eb26338aa2c34d759ac053a2301e17aeac7d886c src\Reown.AppKit.Unity\Runtime\Components\Modal.cs`

However it seems that git show always fails when I try to export it: `git show eb26338aa2c34d759ac053a2301e17aeac7d886c:src\Reown.AppKit.Unity\Runtime\Components\Modal.cs > Modal-my_version.cs`

The error is `fatal: path 'src\Reown.AppKit.Unity\Runtime\Components\Modal.cs' exists on disk, but not in 'eb26338aa2c34d759ac053a2301e17aeac7d886c'`

But why is it throwing this error when checkout is able to locate the file just fine?

Top Comment: Flip your separators \ -> / in git path strings. backslashes are ok when there is a file system thing to check against. And fire off an invective at the curse MS-DOS 1.0 left for the Windows users of today.

Forum: r/git

Git Diff vs Git Show and ranges

Main Post:

When I use git show someCommitHash then I see the difference between the commit in question and it's predecessor, why when doing a git diff somePreviousCommitHash..someCommitHash must I give the double dot and the previous hash to see the same thing?

I presume git diff with the double dot range, requires a from and to commit to see the delta. However it seems git show is a much more elegant and quick way to see the delta between a commit and it's immediate predecessor. Why don't people use git show more?

Top Comment: Why do you suggest that people don't use git show often? I certainly use it more often than git diff in my day to day work. git diff is obviously a more generic and powerful tool for viewing diffs, so I guess one could argue if one were only going to learn one, it should be git diff?

Forum: r/git