-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
format output #73
Comments
Not currently. Do you have an example of an Emacs mode that does something like that?' |
It's 2013/12/16 Cezar Halmagean [email protected]
|
Ah, ok. That shouldn't be hard to do. |
Looks like focussing the first error should be easy with |
Or rather, it already works. @asok I guess that was a reply to the original question. The main problem of these commands, I guess, is that they visit each backtrace line. Typing |
@dgutov yup I was answering the original question. But as you said, that will actually not bring you to the next failing example only to the next error in the backtrace. |
Hi, is there a way to format the output so that it can fit in the error buffer (when a test fails) or an easy way to visit each error without actually needing to switch to the error buffer and then pgup/pgdown to find the errors ?
The text was updated successfully, but these errors were encountered: