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

[Feature Request] Merge stdout and stderr in the Output View #613

Open
2 tasks done
zsmatrix62 opened this issue Jun 29, 2022 · 6 comments
Open
2 tasks done

[Feature Request] Merge stdout and stderr in the Output View #613

zsmatrix62 opened this issue Jun 29, 2022 · 6 comments
Labels
good first issue Good for newcomers Severity 3+ The issue is rare or cosmetic, or unfixable

Comments

@zsmatrix62
Copy link
Contributor

Description

Hi,

Im new to Vimspector, today I wrote a config file for my go project but it seems launch failed, I want to check the failing reason and it provides Failed to launch: Build error: Check the debug console for details.

But where is the mentioned console

image

Works in vim?

Reproducable in Vim

Works with clean config?

Yes

Minimal Reproduction

List of steps to reproduce:

  1. Run vim ---clean Nu /path/to/vimspector/support/minimal_vimrc
  2. Open this project...
  3. Press this sequence of keys

Expected Behaviour

show failing reason in some place

Actual Behaviour

nothing shows

Additional information

No response

Installation Type

Plugin Manager (git clone)

Vimspector version

latest

Debug Info

No response

Log file

No response

Vim version

NVIM 0.7.2

Python version

No response

Neovim diagnostics

No response

Operating System

No response

Declaration

@puremourning
Copy link
Owner

where are the steps to reproduce?

Please complete all elements of the template.

@puremourning
Copy link
Owner

Screenshot 2022-06-29 at 15 17 28

If you use vim, you'd see the WinBar with the stderr tab. It would have a little * next to it to show there is output.

Anyway, use :VimspectorShowOutput stderr in this case. I don't control what the debug adapter says in its failure message. The "debug console" could mean anything in any client.

@puremourning
Copy link
Owner

hmmm, wonder if it would be better to pipe the stderr from the debug adapter into the Console buffer. :/
not sure how useful that might be, but perhaps it would make these sorts of messages easier to find.

@puremourning puremourning reopened this Jun 29, 2022
@puremourning
Copy link
Owner

the spec has been updated/clarified since I last looked at it:

     * 'stdout': Show the output as normal program output from the debuggee.
     * 'stderr': Show the output as error program output from the debuggee.

I think therefore it makes no sense to do what vimspector is currently doing, which is putting the stdout in Console and the stderr in a different buffer. I'll fix that.

@puremourning puremourning added good first issue Good for newcomers Severity 3+ The issue is rare or cosmetic, or unfixable labels Oct 22, 2022
@puremourning puremourning changed the title No where to check launch failed message [Feature Request] Merge stdout and stderr in the Output View Apr 21, 2023
@angles-n-daemons
Copy link

Would it be as simple as modifying the BUFFER_MAP in output.py so that stderr points to the Console?

@puremourning
Copy link
Owner

If memory serves it wasn't that simple. But feel free to try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers Severity 3+ The issue is rare or cosmetic, or unfixable
Projects
None yet
Development

No branches or pull requests

3 participants