I have five command extension points (org.eclipse.ui.commands). They all have handler extension points (org.eclipse.ui.handlers). Two of them launch two different view extension points (org.eclipse.ui.views). They show up in the "Quick Access" box as intended. The three others are different commands to launch the same editor extension point (org.eclipse.ui.editors). For some reason, two of these other commands unexpectedly appear in the QA box. It was a fluke that I even noticed it as this was unintended behaviour. I am at a loss as to explain how two of them show, but the other does not. I would like to ensure none of these three editor commands appear in the QA box. Please advise.
Related
The output window in Visual Studio Code is extremely annoying when messages keep popping up, considering that the only tab I use is the Terminal tab. Is there an extension or built-in method that suppresses all messages to the output window or outright disables it? I've come across multiple questions and they all require disabling the bottom tabs entirely which is inconvenient for me, or requires tasks which I don't use. There's also multiple issues on the VSC github where it's extremely helpful and say something along the lines of: It's an extension problem, report it to the extension creator.
Can anyone explain these three debug symbols on VSCode I have found on the internet?
My vs code has the one with the play icon.
All demos online on debugging have the one in the middle. How do I get that?
Also, node js debugging is installed but I think it shows as disabled, with no option I can find to enable it.
To answer your question directly [TL;DR]: you already have it if you are using the latest version of vscode. It will take you to the same view as the one on the right
If you look at the codicon libray ref the middle one you pointed out is not present.
Visual Studio Code made changes in February 2020 ref that incorporates running and debugging to be something more harmonious:
User studies revealed that new users have difficulties finding how to run their programs in VS Code. One reason is that the existing "Debugging" functionality is not something that they relate to "Running" a program. For that reason, we are making "Run" more prominent in the UI.
The main menu Debug has become the Run menu.
The Run and Debug view has become the Run view and the corresponding Activity Bar icon now shows a large "Play" icon with a small "bug" decoration.
So in other words, there is no difference. The 'Run' and 'Debug' view is synonymous and the icon reflects those changes. As they noted, the Debug view is now called the 'Run' view, but it still offers debugging and breakpoints.
There are 2 possibilities you are running into however:
The tutorials and guides you are using are out-dated (showing an outdated version of vscode)
The tutorial or guide is using an extension that offers debugging capabilities. Extensions have some control over the icon you see
The extension is for single file debugging, according to the June 2020 ref notes, vscode recommends the following:
For debug extensions that want to improve the single file debug experience by adding a "Run" and/or "Debug" button to the editor, we recommend following these guidelines for a consistent look and feel:
Contribute Run and/or Debug commands in the package.json (see Mock Debug):
Use the command titles "Run File"/"Debug File" or "Run Python File"/"Debug Python File".
Use the $(play) icon for Run and $(debug-alt-small) for Debug.
Where their codicon library was updated in June to reflect the following:
As you can see, none of them are prefixed with verbiage like 'run', but they all represent the same functionality.
Additionally, you may see this icon as well:
This represents the panel (view) where the output of your debug will go.
VS Code: 1.23.1
OS: OSX 10.12.6
If I have two different editors open (I think that's the term for two different windows, each of which could have multiple tabs, and could also be workspaces), and I run Find... in one window, the search text and settings (e.g. Match Case, Match Whole Word) in the other window are unaffected. I'd like to find a way so that these are always linked, they're always kept in sync. Is there a setting or an extension to do this? I could not find one. Thanks!
That does not seem to be possible, as each Windows has its own GUI states (including the current find search pattern)
This is similar to issue 10121 "Allow for floating windows" where Terminal or Debug Console would be applied to all opened editor windows instead of being tied to the current one.
For now, those GUI elements (including Find) are specific to the current opened editor, not sharing their state with other VSCode windows.
I have a number of monitors. I typically move between up to 4 or 5 workspaces for different areas of focus during the day (simply different projects, PyCharm for Python projects vs Eclipse for Java projects, e-mail and project management activities, etc.)
I would like to throw a chat application up on a monitor that would be mapped into all workspaces so that it's always up attracting my attention and doesn't change when I change workspaces.
I don't see in Cinnamon any option to do this and find no search expression getting me help in Google to solve it.
At the moment, this is not possible in Cinnamon. It is a long standing feature request (since 2012!).
However, there are alternatives to it. Namely, the program devilspie2 (available in the repositories) allows one to manage windows and their placement, with the help of a small Lua script.
Here1 is how I stick my Firefox and Pidgin window on all workspaces, while some other windows in a given workspace WORK (because I don't want to see them when I'm not working (: ).
-- Make windows of all these apps visible on all workspaces
GLOBAL_WINDOWS='Firefox;System Monitor;Pidgin'
if (GLOBAL_WINDOWS:find(get_application_name())) then
pin_window();
end
-- Firefox should be tall maximised
if (get_application_name() == 'Firefox') then
maximize_vertically();
end
-- Put the Sublime on their correct workspaces
if (get_application_name() == 'Sublime Text' and get_window_name():find('WORK')) then
set_window_workspace(4);
end
This should be placed in a config file in your home directory. Check the documentation :). And don't forget to set devilspie2 as the first startup app.
1 also posted in that issue
I have an Eclipse workspace with a bunch of projects. I manually created some run configurations for each project (it's necessary to pass some arguments to VM, so I can't just run it directly, e.g. using shortcut ALT+SHIFT+X, T in the specific file).
Most of the time, I just use one run configuration (whereas for the first time I manually launch it using Run -> Run configurations -> (name) -> Run). Since I configured Eclipse to always run the last run configuration (on F11 or CTRL+F11), it's usually enough.
However, sometimes I need to switch to a different run configuration and then back to previous one and then to a different one etc. Is there a quick way to do it? I'd like to see a shortcut, which would display pop-up window with all existing run configurations. By typing first few letters, I'd find an appropriate one and would be able to immediately run it by pressing ENTER. I mean something similar to what CTRL+SHIFT+T or CTRL+SHIFT+R looks like.
I'm afraid there's not something like that. Nonetheless, any advice on how to get more effective would be greatly appreciated, because I'm bored of switching run configurations via menu (as I described above). I can press ALT+R, N and then select a run configuration using arrow keys, but it's not really that comfortable.
You already gave most of the answer yourself. Start by pressing ALT+R, N and then simply start typing the name of the configuration you want. The cursor should be positioned in the filter field and thus incrementally reduce the list of launch configurations as you type. When you've narrowed it down to 1, complete the selection by ALT+R.
BTW: thanks for the reminder, I, too, was using the mouse way too much in this particular use case. I will stop doing so, now that I gave the answer :)
Since Eclipse 4.12 (June 2019, 4 years later) you can also launch any of the Run or Debug configurations available in your workspace from... the Quick Access menu (Ctrl+3 shortcut)
Note: For performance reasons, the extra Quick Access entries are only visible if the org.eclipse.debug.ui bundle was already activated by some previous action in the workbench such as editing a launch configuration, or expanding the Run As... menus.