Kipras Melnikovas

@maxiejbe looks good to me! Let's remove the basic usage example right before we ship `2.x` but not earlier to avoid confusion. :shipit:

1.2.1 is fine, 1.2.2 is broken ``` npm i -g [email protected] ```

Another reason why someone'd want this is because I don't want the frequent updates to impact my github contributions graph, and using a deploy key seems to solve the issue...

See also https://github.com/sarpik/git-backup -- I see that I've created a very similar feature:D Mine also supports including untracked changes, but it uses `git stash push` instead of `git stash create`...

update: I think I figured something out! ```patch diff --git a/x.c b/x.c index 696ade9..6fc70a7 100644 --- a/x.c +++ b/x.c @@ -1684,8 +1684,9 @@ xdrawcursor(int cx, int cy, Glyph g, int...

another update: I think I got it working! The thing was - the extremely large value of `g.fg` would cause the segfault, but using the other value (`g.bg`) as `new_drawcol_idx`...

oh wow that's so much better, thanks!! The only problem I had was that my cursor was hidden if it was in INSERT mode and my background was dark (it...

> It's better to have a ready patch when submitting to the suckless site, the patches area is more of a user space and it is not to my knowleddge...

@bakkeby > @eeeXun can you try this change and see if that works in all situations for you? @eeeXun > @bakkeby No, it seems not work.Still can't see the cursor...

fyi you can now enable `-F` to always be true via the new config option since #101: ```ini [absorb] oneFixupPerCommit = true ```