-
Notifications
You must be signed in to change notification settings - Fork 48
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
Strange branched from master
section
#122
Comments
What branch is checked out? |
I'm getting it for https://github.com/SkynetLabs/skynet-js, branch |
I'm not sure what to do about this. Please report whether this still happens with the latest version. |
Thanks for circling back to this. Looks like I still get it for that branch. Were you unable to reproduce? I noticed the latest commit in that branch is a merge from master, that probably has something to do with it? |
You don't have the (setq magit-todos-update nil) |
No, I didn't set that. And now that I've noticed that, I think there's no bug here. Since you're blocking automatic updating of the lists, the section doesn't know whether any items exist to be displayed, so like the non-branched section, it informs the user that manual update is required. |
Should there be two |
The way I see it, when you disable automatic updates, the sections tell you that they may not be up-to-date. Otherwise, when items do exist but aren't shown due to not being updated, you might not realize that something is missing. In other words, showing the empty section with the reminder prevents false negatives. You could argue that showing both sections that way is redundant, but I would argue that I don't want to add a special case and make the code more complicated, especially since it only happens when automatic updates are disabled, which AFAICT is rare. Maybe we should talk about why you've disabled automatic updates. If we could solve that, this issue would go away for you, right? |
I don't mean the I mean there are two
Updates incur noticeable lag in large repos, even with |
I'm confused. I'm getting the impression that you're misunderstanding the purpose of the "branched from master" section. You do realize that it only appears when in non-master (or main, whatever the default branch is) branches, right?
Ok, how large is "large"? And how many items are we talking about? And what platform are you on? |
Yeah, could be a misunderstanding on my part. And apologies for the unclear original issue. So, there being two TODOs sections is not a bug, but intentional, to have a separate section for I assumed it was a bug due to this section only appearing with
Either of these would have made it more clear to me and avoided this issue. At any rate, I appreciate your patience in sorting this whole mess out.
I don't use magit-todos anymore, so maybe the lag is no longer an issue. This is a good example of a big repo. |
Yes, one section shows only todos in the checked-out, non-master branch.
That could be done, but I don't think it's necessary, because out of the apparently thousands of users this package has, no one has ever complained about that before. As well, it would make the main section more verbose by default.
I don't think that would help; I don't even understand what it means. As well, my impression is that few users disable
I appreciate your feedback, although I wish I had known sooner that you don't use the package anymore.
I started to download it to test, but seeing that it is at least 500 MB, I decided not to. Anyway, with a repository that large, then, yes, it can be expected to take a while. FWIW, testing on the emacs.git repo (about 1.3 GB) using ripgrep on my system, it takes about 3 seconds to scan the repo's files (about 4,800) and and insert 2,300 items (on an SSD). |
When I set
it shows a new extra
branched from master
section:I am profoundly preplexed and deeply disturbed.
The text was updated successfully, but these errors were encountered: