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

format output #73

Open
chalmagean opened this issue Dec 16, 2013 · 6 comments
Open

format output #73

chalmagean opened this issue Dec 16, 2013 · 6 comments

Comments

@chalmagean
Copy link

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 ?

@dgutov
Copy link
Collaborator

dgutov commented Dec 16, 2013

Not currently. Do you have an example of an Emacs mode that does something like that?'
We could adopt the approach.

@asok
Copy link
Contributor

asok commented Dec 16, 2013

It's next-error and previous-error. By default binded to M-g n and
M-g p.

2013/12/16 Cezar Halmagean [email protected]

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 ?


Reply to this email directly or view it on GitHubhttps://github.com//issues/73
.

@dgutov
Copy link
Collaborator

dgutov commented Dec 16, 2013

Ah, ok. That shouldn't be hard to do.

@chalmagean
Copy link
Author

Looks like focussing the first error should be easy with next-error (or something similar) ? (Thanks @asok)

@dgutov
Copy link
Collaborator

dgutov commented Dec 16, 2013

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 M-g n twice won't bring you to the second failing example, but to the second line of the first failure's backtrace.

@asok
Copy link
Contributor

asok commented Dec 16, 2013

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants