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

Fix common "wall of text" issue when commands generate lots of output #12983

Closed
mikemaccana opened this issue Apr 26, 2022 · 3 comments
Closed
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

@mikemaccana
Copy link
Contributor

Description of the new feature/enhancement

A common issue of many terminal is 'wall of text'. For example, the user runs a command, the command generates 4000 lines of text, and it's difficult to scroll, say, exactly to the beginning of the previous command to begin reading the output.

Warp is a new terminal that purports to solve this issue image. Windows Terminal should solve it too.

Proposed technical implementation details (optional)

I can't use Warp (it doesn't have a Windows version yet) but I propose a simple implementation would be to allow the user to specify their prompt, so pressing (some shortcut key) will return to the previous instance of that prompt.

______________________________________________________
$: ls /dir

(5000 lines of text)
______________________________________________________
$: (pressing somekeyboard combo goes to last instance of `$:`

There may be a better way though. Shell prompt could signal the terminal somehow (like the shell beep does).

@mikemaccana mikemaccana added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Apr 26, 2022
@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 Apr 26, 2022
@zadjii-msft
Copy link
Member

Boy would you be interested in #12948 😉

gh-12948-scroll-between-marks
fig 4: scrolling between marks

/dup #11000

@ghost
Copy link

ghost commented Apr 26, 2022

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 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 Apr 26, 2022
@mikemaccana
Copy link
Contributor Author

@zadjii-msft Yes, yes I would 💯

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

2 participants