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] Search text in Terminal, Output, Console and/or any editor #28333

Closed
savioret opened this issue Jun 9, 2017 · 4 comments
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@savioret
Copy link

savioret commented Jun 9, 2017

  • VSCode Version: 1.12.1
  • OS Version: Any

It would be really powerful and flexible to be able to search using the common inline search widget (ctrl+f) in the Terminal window, Debug Console, Output, Problems window as if they were common Editors.
The same would be nice for the Extension windows, the screen that shows the information about an extension has no way to search text.

If any of you has ever worked with emacs, you'd probably know the advantadges of being able to search anywhere.

Thank you and congrats for this geat editor.

@iamdevlinph
Copy link

Isn't the Terminal Window an independent application? Just an instance in VS Code.

@savioret
Copy link
Author

savioret commented Jun 9, 2017

I'm not sure what are the limits, I don't think it's just a closed "blackbox", searching is just a readonly operation, if the containing text is somehow readable, it's searchable.
For example, using the c++ plugin and running a compile task, the compiler errors shown in the terminal are read and parsed and then shown formatted in the "Problems" window.

@Tyriar
Copy link
Member

Tyriar commented Jun 12, 2017

Duplicate #15198, I've been thinking about this a bit recently. I'm not sure if we can offer a consistent search experience (as cool as that would be) as it's built on https://github.com/sourcelair/xterm.js which is probably what @iamdevlinph was calling out.

@Tyriar Tyriar closed this as completed Jun 12, 2017
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 12, 2017
@Tyriar
Copy link
Member

Tyriar commented Jun 15, 2017

@savioret FYI we have a really basic version landing in Insiders tomorrow, more details in #15198 (comment)

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants