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

go layer: clickable file:lineno links in test output stack traces #5868

Closed
edrex opened this issue Apr 22, 2016 · 1 comment
Closed

go layer: clickable file:lineno links in test output stack traces #5868

edrex opened this issue Apr 22, 2016 · 1 comment

Comments

@edrex
Copy link
Contributor

edrex commented Apr 22, 2016

I would be nice if file:lineno ranges in stack traces in test output were clickable links.

The current in-tree implementation uses shell-mode for the test output.

Thoughts:

  • Other languages output stack traces with the same file:lineno format (Ruby, probably JS and Python too) . Maybe this should be reusable across languages? Could it be a refinement to shell mode or a "minor mode"? IDK how minor modes work.
  • There's https://github.com/nlamirault/gotest.el, which introduces a specific Go-Test mode with clickable links and some highlighting. I've done some limited testing of it and it seems to work fine. Maybe we should pull that in to replace the in-tree implementation.
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
@lebensterben lebensterben removed the stale marked as a stale issue/pr (usually by a bot) label Feb 4, 2022
@lebensterben lebensterben moved this from Unanswered to To close in Forum Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Forum
  
To close
Development

No branches or pull requests

4 participants