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

Make Hightail a good tool for debugging #29

Open
dj3500 opened this issue Sep 30, 2012 · 4 comments · May be fixed by #117
Open

Make Hightail a good tool for debugging #29

dj3500 opened this issue Sep 30, 2012 · 4 comments · May be fixed by #117

Comments

@dj3500
Copy link
Owner

dj3500 commented Sep 30, 2012

This is far-fetched and might not be possible to do / to do right. But I'm thinking about something along the lines of:

  • the user has a macro like
    #define DBG(x) cout << "DBG: " << #x << " = " << x << endl;
  • we ignore (in diffing) lines beginning with DBG, but in diff view, we truncate the "DBG: " and display the lines in green, or something.
  • or, we could display everything that came from stderr in green (however, can we sync it with what came from stdout and display both things in the same textarea?)
    Don't know if this would be usable.
@dj3500
Copy link
Owner Author

dj3500 commented May 13, 2013

Currently, we're not displaying the standard error output anywhere to the user; we could at least do that. (Display it where? The table is wide as it is.)

@AuroMun
Copy link
Contributor

AuroMun commented Jan 27, 2015

image
A simpler solution could be just to ignore any lines starting with "DBG", and print them as they are.
The only problem is that Hightail takes in the output string by string, so debug statements with spaces would create a problem.

@dj3500
Copy link
Owner Author

dj3500 commented Jan 27, 2015

Actually, I'm wondering if it could be possible to display the cerr output of the program (don't use it for diffing, just for displaying), say in green. My vision is that it should be intertwined with the output of the program, just as it would be if displayed when run in the console. My first thought is that it would be hard, since we can't say which line "came first", but the console does manage to display it in the right order somehow, so maybe we could as well. I didn't research it (and whether it is possible in Java) though.

@dj3500
Copy link
Owner Author

dj3500 commented Feb 2, 2015

ShafinKhadem added a commit to ShafinKhadem/hightail that referenced this issue May 14, 2021
show line and token number of 1st mismatch, redirect stderr to stdout, exclude lines starting with "DBG#~ ". Attempts to fix dj3500#5 and dj3500#29
@ShafinKhadem ShafinKhadem linked a pull request May 14, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants