search

krasa / GrepConsole

IntelliJ plugin - https://plugins.jetbrains.com/plugin/7125
Apache License 2.0
436 stars 57 forks source link

Rider - Should this be able to work in the standard debug console? #181

Open MostHated opened 3 years ago

MostHated commented 3 years ago

Hey there, Over the last 2-3 years I have tried every plugin I could find but for some reason I can never get any sort of highlighting in the default debug console. When I came across this one I had high hopes, but when I went to give it a try, there was unfortunately no change, as with all of my other attempts. Do I just have something setup incorrectly with this, or does it simply not work with the debug console?

I just tried to add two additional items that matched up with what I had here, but as you can see below, nothing has changed:

This is from my Help/About window, in case it helps out any.

JetBrains Rider 2020.3 EAP 10 Build #RD-203.5981.86, built on December 2, 2020 Rider EAP User Runtime version: 11.0.9+11-b1145.21 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. .NET Framework 4.0.30319.42000 Windows 10 10.0 GC: ParNew, ConcurrentMarkSweep Memory: 3959M Cores: 32

Thanks, -MH

krasa commented 3 years ago

That looks like terminal console, unfortunatelly Jetbrains migrated a lot of consoles to it without providing any API support - https://youtrack.jetbrains.com/issue/IDEA-216442

this might help: https://github.com/krasa/GrepConsole/issues/147#issuecomment-667953246

coprocoder commented 1 year ago

Disable default terminal when launching nodejs:

  1. choose Help | Find Action... on the main menu;
  2. type registry to locate the Registry
  3. find nodejs.console.use.terminal key there and disable it
yimun commented 3 months ago

Disable default terminal when launching nodejs:

  1. choose Help | Find Action... on the main menu;
  2. type registry to locate the Registry
  3. find nodejs.console.use.terminal key there and disable it

It works on WebStorm 2023.1.5