racket / racket/drracket

‘jump to binding’ usability change

Open
#584 5 comments 0 reactions 1 assignee View on GitHub

@spdegabrielle is already working on this.

Since Aug 23, 2022.

usability
Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

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.
image 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.
image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.