![]() I optimistically worked on it a bit yesterday just in case. So, if you ever finish packaging it, I’ll give it a try. But since I basically pass all my time into a non-detached mode anyways, it’s not that useful to spend energy in trying to find a nice name where 90% of the time it’s just the name of the branch. ![]() it also takes into account tags), and, of course, the colors have been tailored to my needs. It looks like lilgit does basically what my prompt does, except my prompt tries a little harder in finding a nice name to be shown (ie. Not looking at my notes, but I think the main thing I wanted to fix is figuring out why the rust component stopped building against nixpkgs-unstable on darwin back in October. I’ve been picking at converting more of my own packages to flakes over the past few months and have one almost ready for lilgit. post here: Slow prompt in large git repos? speed up with lilgit.gh: GitHub - abathur/lilgit: a smol (quick) git status prompt plugin.I confirm the hypothesis: after regeneration of the index, the git status on the repository of 16.7 Gb lasted only a few seconds, as with version 5.4.0.I tried gitstatusd but still wasn’t super pleased so I ended up writing a bash prompt plugin to claw back that time in most contexts: If yes this would prove Thomas' assumption. Then restart Eclipse and see if this problem is gone. refresh the git staging view, now it should be empty again since the git index was recreated select the repository in the repositories view and click "Reset. refresh git staging view in Eclipse, this now shows all the files in the repo as untracked files $ cd to root of the working tree of the respective git repository from a shell backup and delete the git index (EGit doesn't allow you to delete files inside the. staging view for this repo is empty, if you have uncommitted changes then commit them ![]() Matthias Sohn wrote on Tue, 10 September 2019 10:37 If that's true recreating the git index should fix this.Ĭan you try to recreate the git index for all git repositories in your workspace? | Biggest objects | * Blobs | * Maximum size | 43.3 MiBħ: window size : 8 k, window cache limit: 500 m, delta base cache limit : 10 m, stream file threshold : 50 mĪnother point: when I go into the perspective "git" of eclipse, a "git status" is triggered for all other repositories for which I have no open project in my workspace. Overall repository size | * Blobs | * Total size | 16.7 GiB ![]() The 3 biggest have this kind of statistics: I attach to the post a screenshot of the progress view of eclipse at startup. So it slows down even more, but before version 5.4.2, I did not have this phenomenon.Ħ : 16 repo currently open. This is a corporate post, and the built-in antivirus scans all files, all the time., and is not deactivatable. If it is on repo very big, the 3 are very slow, and we quickly go to 15 minutes. I noticed that in general there is 3 git status in parallel, no more. it depends on what other repo runs the git status. 1: I see the launch of a git status in the "progress" view of Eclipse only when I open Eclipe in the morning: the rest of the day I can not see it.Ģ : eclipse 2019-06, and the previous version of egit : 5.06121030-rĥ : Between 1 and 10 minutes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |