‘jump to binding’ usability change

[spdegabrielle]

Is your feature request related to a problem? Please describe. (5 days ago on slack)

:face_palm: <-- me when clicking on "Jump to binding occurrence" rather than "Jump to Definition (in other file)" This moves the cursor to the provide line, which means I need to manually move the cursor back to the original site and click on "Jump to def..."

Stephen: I’m glad it’s not just me

Describe the solution you'd like Suggest that ‘jump to binding’ has a different behaviour.

Ideas:

1. Just jump to the definition when the binding is a require form
2. add an indicator to ‘jump to binding’ (e.g. make it pink in the menu) so you know you are going to a require e.g.
3. 'Cursor undo’ function that retraces the cursor location history

Describe alternatives you've considered I don't have a favourite

Do you want to contribute to this feature yes

[Optional] Additional context

e.g. this shows an identifier with the context menu - if you select jump to binding it will go to the require.

[sorawee]

This is a duplicate of https://github.com/racket/drracket/issues/273 (and should be an issue in the DrRacket repo). I will close it.

[rfindler]

I saw this one as different than racket/drracket#273. Here it is a question of which keybindings should go to which operations and there it was a question of what "jump to definition" does. I do think collecting all interested parties to one place and having a discussion could be very helpful, tho! And if I'm misunderstanding the request in racket/drracket#273, then great! It would be nice to be able to make progress there.

[sorawee]

Ah OK, I misunderstood the original post then. Sorry about that.

[rfindler]

But you're totally right that we should put this in the drracket repo, @sorawee I'll start the transfer.

[spdegabrielle]

(can we have a 'usability' label for this ticket?)