-
Notifications
You must be signed in to change notification settings - Fork 361
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
Allow fold / excerpting of blocks and previous individual commands #23
Comments
This functionality would compliment / be complimented by #1 With both there might be some utility of offering the option to re-insert a previous command at the end of the history (without actually re-running and promenantly linking back to the original — or possibly even actually rerunning but still linking, offering a diff of output?) if one did that, it would be potentially useful to be able to (re)excerpt the same command different ways: e.g. highlighting (simultaneous) detection of problems (or say, a problem requiring intervention on several hosts/instances of a service) that were dealt with in serial |
from #291 @JosephTLyons
|
from #291 @elviskahoro In terms of passive indicators, I'm only able to come up with changing the divider color and maybe the collapse caret color to yellow (in the case of dark theme) / whatever the highlight hex code is.
|
from #291 @elviskahoro
|
from #291 @elviskahoro
|
from #291 @elviskahoro
|
this was filed in July 2021, how difficult it is to make blocks at least collapsable, you already received a bunch of similar requests. |
I spent half an hour digging through docs and expected this to be a built-in feature, the same way that ie. Jupyter notebooks allow you to toggle a block's output. +1 on this request! |
Thanks, Folks who have 👍 and commented on this request. I believe we've begun to investigate the possibility of hiding/collapsing blocks as it's been a common request. No official ETA on any launch, but we'll post any additional updates on this thread. We appreciate your patience and interest in Warp! |
This is super useful to cleanup the screen from intermediate commands with noisy output. I use it regularly with the Apple Terminal (cmd+L). |
Came looking for the same feature |
Shameless new comment 👍 to this. Only gripe I've run into. Great software! |
This might not be directly related, but I did not find any issue about it – would it also be possible to support folding of some output, like |
I too was assuming this would be available right from the start. A workaround can be to use the filter feature and search for something that doesn't exist (just type some gibberish) and the block will collapse. You can reset the filter to "expand" the block again. But it would be way better to have native support for this. It would also be great to have an option so that blocks automatically collapse if they exceed some defined line count that can be adjusted in the settings. And/or to have blocks auto-collapse once they are a certain number of items back in the history, so it's easier to scroll back in your history. |
Wish for older blocks to auto-collapse (to their sticky header) as they move out of the current viewport when I create new blocks. So that when I scroll up, I see a bunch of collapsed blocks, and I only need to open the block that I'm interested in (which would stay open permanently even when I scroll back down). |
I just contributed to the crowdfunded bounty on this issue. Each contribution to this bounty has an expiry time and will be auto-refunded to the contributor if the issue is not solved before then. This is an 80% PR author bounty, with 80% of the reward going to the merged PR author. |
EDIT 7/29, 7pm Eastern:
A separate open issue describing hide/delete, and potentially collapse, is (more) active as #50. If desired (lmk, warp folx; or just use your edit powers directly), I am happy to reduce scope of this feature request / Issue to just the excerpting bits.
on Discord, @s278gupt, shared some mock-ups of
Collapsing:
And
Deleting:
This seems like an obvious enough extension of the current model so as to likely already be on the roadmap, but better safe than sorry:
The separation and scroll of individual commands on a per-block basis is great for being able to quickly get back-past an excessive length output of a command to useful output further back – but moreso when that long output is at the end of a session's recent-history than if its in the middle
sometimes, e.g. when debugging an operational command, there can be some chatty commands you ran that were either largely or, it turns out, entirely irrelevant - but there is info further back in the history you still want to get/refer to. Currently (in Warp and other shells) your best bet is to either just copy and paste those commands output to a text file or to run them again so they are further down in history.
Warp's copy and paste functionality make the former easier than before, and share offers another maybe quicker option (open the command in a browser tab, paste link into slack, etc)
Nevertheless, I think it would be neat if one could more pro-actively curate the scrollback down to useful info:
I can imagine option (3.) being useful both actively as one is doing some work (here I imagine too some ability to bookmark-or-pin-to-float), and retroactively (along with other annotation facilities) to turn a shell session into (part of) ~a postmortem report
The text was updated successfully, but these errors were encountered: