-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Define number of lines when output is large #1973
Comments
What about |
The yesno() expects only 1 char
|
the value in scr.interactive can be pager perfectly. i was talking about the function itself |
instead of saying "wanna dump 300KB of text" just say: "wanna see 200 lines of text?" |
This issue has been automatically marked as stale because it has not had recent activity. Considering a lot has changed since its creation, we kindly ask you to check again if the issue you reported is still relevant in the current version of radare2. If it is, update this issue with a comment, otherwise it will be automatically closed if no further activity occurs. Thank you for your contributions. |
Still waiting for feedback or comments after 5 years. Personally i dont think we need any configuration overcomplications here. but maybe its worth to check when the output contains a very long line show in size instead of lines. to confirm the user, because a 100MB single line will just say: "do you want to print 1 line?" which makes not much sense to warn the user for that when the reality is another. So yeah, this bug must be fixed still |
@trufae I'm going to check that |
Any hints where to start? |
i would start like this:
grep in the r2 source code to find this message. ( git grep 'Do you want to print') when found. youll see something like this: so the steps to solve this problem would be:
|
When output is too big in
scr.interactive
there should be more options than just "Yes" or "No".I'm proposing the following:
scr.pager
(less, more, ..)We can add
r_cons_head()
andr_cons_tail()
functions to chop the non-flushed buffer.The text was updated successfully, but these errors were encountered: