New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: 190: Configurable diffs #201
Conversation
Thanks for this. Can we get configuration instructions please? My
|
@snoblenet I would have a look at your logs and see what command it's using. I use this alias when working with local branches:
logrus has added those backslashes, so after removing those, I get:
Which gives me a side-by-side diff if I paste that directly into my terminal. Having said all that, looks like the original command template I used doesn't need the last Let me know if that helps :) |
Do I have to check out a specific branch for logging? As I tried just logging with my current installation using |
@snoblenet you don't have to use a specific branch for logging.. |
Ah sorry I was expecting Some output from
|
I was keen to test this branch so that it can be merged. However, I have encountered a roadblock:
I don't have a background with Go so I'm not sure what do next. |
It looks like just one failing test is blocking the merge: |
hey @snoblenet apologies for the late reply I had a holiday and have since been very busy :) I've just merged master into this PR and it looks pretty much good to go, except for one bug where the currently selected line in staging-lines mode doesn't get highlighted. I've managed to fix this in my rebasing PR that I expect to merge soon but I can't recall how I did it haha. My plan is to merge that rebasing PR and then merge this in straight afterwards, hopefully soon! Regarding your |
…py one third of the screen)
For some reason, after merging master into this branch, attempting to open a file caused a crash. The OS section of the default config in app_config.go didn't get overridden by the user's config, and I'm not sure why. I'm going to comment it out for now and see if the issue resurfaces in some other way later
Codecov Report
@@ Coverage Diff @@
## master #201 +/- ##
==========================================
+ Coverage 83.5% 83.52% +0.02%
==========================================
Files 19 19
Lines 3158 3174 +16
==========================================
+ Hits 2637 2651 +14
- Misses 490 491 +1
- Partials 31 32 +1
Continue to review full report at Codecov.
|
It doesn't seem to be reading my In Is the syntax above correct? I couldn't find any documentation to answer that question myself sorry. |
When I use your config i.e.:
I get the correct split diff view. Perhaps your config file is in the wrong location. If you go into lazygit and go up to the status panel at the top, and hit 'o' it should open your config file in your editor (or hit 'e' to directly edit it). Do you get the expected file when you do that? |
It opens to the correct file when I press My config file as it Previously I had a symbolic link from somewhere in the Where should I create my link? I previously have installed Lazygit using |
my config is at |
I wonder if that package does not like symlinks?
|
Replaced all symlinks with hard files in |
Have you tried |
On linux linked folder seems to work fine, cd ~/.config/jesseduffield/
mv lazygit lazygit-real
ln -s lazygit-real lazygit
cd /to/some/git/repo
lazygit # lazygit opens with my config |
I am regrettably closing this because the codebase has shifted so much since I first put it up and I'd need to come up with a smarter way of supporting it. |
This allows for users to specify a git diff template which will have its placeholder values populated at runtime.
TODO: benchmarking to see if this slows things down for the regular git diff
TODO: don't use runDirectCommand unless there is a user config option