Closed Linuus closed 6 years ago
This is all very related to #319, so I'll keep most of the discussion there.
This is all stemming from the fact that the github repo context is on Project A
even inside the Project B
section. A lot of the repo-specific stuff still doesn't respect thing-at-point – this is probably why you're getting the wrong issue list.
To answer the overall question about UI, yes: you should expect w
to open the thing-at-point in the browser and RET
to visit it within emacs (when possible). evil-magit shouldn't impact this, but as I don't use evil, YMMV :-)
Thank your for the answers and this awesome project! I’m really impressed so far!
Just to clarify, that w is not working on Project B is a bug in Magithub?
If I understand the situation correctly, yes.
Ok, thanks! I'll try to send a PR when I get time to fix it :)
Hi!
If I open a project
Project A
and runmagithub-dashboard
I can see issues assigned to me, like this:Now, if I put the cursor on
Project B
and press<RET>
it opens the issue list forProject A
. I believe it should open the issue list ofProject B
, right?Another thing:
If I put the cursor on
#123 Some issue
above, and pressRET
it opens the issue/PR and if I pressw
it opens the issue/PR in the browser. If I put the cursor onProject B (2)
above and pressRET
it opens the (wrong) issue list in the browser, andw
opens themagit-am-popup
. Shouldn'tw
browse the issue list as well? Otherwise it's a bit confusing to know when to usew
and when to useRET
.NOTE: I'm using evil-magit, perhaps that messes with keybindings?