Skip to content
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

FR: Marks for easy navigation like Terminal.app #4884

Closed
jkuebart opened this issue Mar 11, 2020 · 4 comments
Closed

FR: Marks for easy navigation like Terminal.app #4884

jkuebart opened this issue Mar 11, 2020 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@jkuebart
Copy link

Description of the new feature/enhancement

I would really like to see a feature I use heavily when working on the command line in Terminal.app on macOS: marks.

When pressing enter, the current line is automatically »marked«. Visually, this is indicated by little brackets on the side of the line – but that's not the interesting/useful part: subsequently, it's possible to navigate between these lines using Command-↑ and Command-↓, among other things. The marked lines scroll into view, making it very convenient to navigate the terminal's back buffer.

This is very useful when programs produce long outputs, such as the debugger lldb: simply press Command-↑ and you see the top of the list and can then scroll back down using scroll bars, mouse wheel, whatever…

Another really nice feature is Command-Shift-A which selects the text up to the most recently marked line: for example, one can simply type »ls« enter, Command-Shift-A Command-C, which selects the output of the command and copies it to the clipboard.

Proposed technical implementation details (optional)

I have no idea how it could be implemented in practice, but it doesn't feel like a very big feature. I think that the visual feedback is secondary, just marking a line automatically after hitting enter already covers 99% of use cases.

The most important keyboard shortcuts are »up« and »down« to scroll the back buffer between the marks. The second most important shortcut is to select from the current position to the most recent mark, but even that could be implemented as a second step.

Terminal.app has more features such as marking manually, bookmarks &c which I have never used, so seems comparatively unimportant.

@jkuebart jkuebart added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 11, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Mar 11, 2020
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #1527 for more discussion.

/dup #1527

@ghost
Copy link

ghost commented Mar 11, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Mar 11, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 11, 2020
@DHowett-MSFT
Copy link
Contributor

There's no explicit note about inserting a mark when you press Enter in that bug, but it does mention prompt positions so I believe it's sufficient. Thanks!

@jkuebart
Copy link
Author

@DHowett-MSFT I briefly looked at #1527 but that looked like it's just about visual cues on the scrollbar rather than navigation shortcuts. I see now that keyboard bindings are mentioned in a comment, so I'm taking the liberty to add my suggestions on that ticket as well.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants