I've installed this plugin to WebStorm, but I can't seem to find a way to actually launch it.
How do I do that?
That plugin is available for IntelliJ IDEA only and not compatible with any other products like WebStorm/PhpStorm etc (possibly because it may require Java-specific functionality that other IDEs do not provide).
You can see all WebStorm-compatible plugins if you switch to WebStorm tab (e.g. https://plugins.jetbrains.com/?webStorm).
You can also see (and install) such plugins directly in WebStorm -- Settings/Preferences | Plugins --> Browse repositories...
Related
After I downloaded Notepad++, I installed Plugin Manager and tried to install Emmet. Only "Installation of Emmet failed" I saw after that. I've tried everything. Install different versions of Notepad++ (including x86) and Python Script. Tried to install it manually. Nothing worked.
How can I install Emmet on Nodepad++?
UPD: I have deleted everything from APPDATA and used "Programms and Components" to uninstall Notepad++
Emmet doesn't show up on Notepad++ Plugin Manager window. Maybe it's outdated or not compatible anymore. Anyway, when you manually install Emmet and you still can't see the plugin please follow those steps;
Open Notepad++ and install Python Script plugin (available in Plugin Manager)
Then open plugins folder from Plugins menu and extract emmet-npp.zip into plugins folder.
Note: If it doesn't work, you might need to move EmmetNPP.dll file inside EmmetNPP folder.
Now restart Notepad++ and you should see the Emmet plugin in your Plugins menu.
You have to put the "EmmetNPP.dll" file into the "EmmetNPP" plugin folder, after having extracted both files into the plugins folder in Notepad++. The official GitHub site missed out this step.
I did all of the following to get it working. One or two of these steps might not be required, but after the final step it started working (i.e. it appeared on the Plugins menu without needing to install via Plugins Admin, and Emmet functions correctly via the Plugins -> Emmet dropdown menu. Next step is to setup keyboard shortcuts (i.e. Tab) as described elsewhere).
Plugins Admin -> install Python Script (restart NPP)
Download and extract the NPP plugin from https://emmet.io/download/
Copy the extracted EmmetNPP.dll and the EmmetNPP folder into:
%USER%\AppData\Roaming\Notepad++\plugins\config folder
Copy file EmmetNPP.dll file into:
%USER%\AppData\Roaming\Notepad++\plugins\config\EmmetNPP folder
Copy file EmmetNPP.dll file into:
C:\Program Files (x86)\Notepad++\plugins\EmmetNPP folder
Notes:
a. I am using the 32-bit version of NPP; if you are using the 64-bit version then step 5 should copy the EmmetNPP.dll file into:
C:\Program Files\Notepad++\plugins\EmmetNPP folder
b. After step 4, Emmet still did not appear either in the Plugins dropdown OR in the Plugin Admin tool. After step 5, though, it now appears in the Plugins dropdown and is functional. (Note that I was careful to restart NPP after each of the above steps. Future readers will not need to restart after each step (just keep NPP closed for steps 2-5) - I did so to test at what point it started working.)
Emmet is installed on Notepad++ using the plugin manager (full instructions found on Emmet for Notepad++ GitHub repo). If you have installed a clean Notepad++ (latest version) and have installed the Notepad++ plugin manager, use Plugins > Plugin Manager > Show Plugin Manager menu action and find and install “Emmet” plugin.
If this isn't working for you, the first thing I would do is uninstall Notepad++ and all extensions/modifications you've added to it and start fresh:
Install Notepad++
Install Nodepad++ Plugin Manger
Install Emmet from the Plugin Manager menu
I need to build in my pepper plugin in chromium source code for building browser with already installed plugin. Is there possibility to do that?
A handful of plugins are built in. Since these are plugins, they are built independently from Chrome and loaded dynamically rather than directly linked to the Chromium executable. This is the function that causes them to be loaded into Chromium:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/common/chrome_content_client.cc&rcl=1436599777&l=118
The NaCl plugin is special, since it runs "in process", which means it is loaded into the renderer process. Eventually, support for this kind of plugin will be eliminated, so it is best to follow the pattern of the "out of process" plugins, which run in their own process, such as PDF.
I have tried the mentioned steps to debug my FB plugin and I am unable to put a break point in the Plugin APIs.
Steps:
1) Launch a “sample page” on Firefox browser which loads my FB plugin.
2) Go to Debug -> "Attach to Process" in Visual studio 2008.
3) Attach the FireFox.exe process which has the “sample page” title.
4) Unable to put a breakpoint in the plugin API as my plugin DLL symbols are not loaded in Visual Studio.
I am not sure why my Plugin DLL symbols are not loaded. Please help me out.
NOTE: FB Plugin is built in Debug mode.
Thank you, Sande
Your problem is that firefox runs plugins in a seperate process; I think it's called something like plugin_container.exe
More info on FireBreath's debugging plugins page
My plugin has some dependencies and it automatically install these dependencies (other third party plugins) when I install my plugin.
When I uninstall my plugin, its dependencies are uninstalled as well.
As these other plugins may be useful to the user, is there any way to uninstall my plugin but leave these dependencies installed?
As far as I could investigate, if I install these other plugins before installing my plugin then they will remain there, but if I install them as dependencies they get ripped off.
If you installed the dependencies explicitly before installing your main plugin, then P2 treats them as installed by the user. In the dependency case, it treats them as installed by the system.
All plugins, which were installed by the system (not by the user), are automatically removed during an uninstallation, if there are no dependent plugins. At least that is what I remember from an EclipseCon presentation by the P2 guys.
That said, it is simply not your job to decide for the user. The user installes features. If those features are uninstalled, their plugins are gone. If the user still wants that functionality, he should install the features containing those plugins.
I'd suggest you disable the plugin instead of uninstalling it, if possible. The answer swimmingfisher provides to Temporarily Disable Eclipse Plugin tells you how to do it.
I have a few plugins in my Jenkins installation which I no longer need. I've already disabled the plugins (and my build still work), and I'd like to remove the plugins completely. What is the right process for completely removing a Jenkins (Hudson) plugin?
As mentioned by Jesse Glick in his answer, if you are using Jenkins 1.487 or higher, then there is a native way to uninstall plugins in the Jenkins UI. See JENKINS-3070 for details.
If you are using a version of Jenkins earlier than 1.487, then you can try manually uninstalling the plugin. As some people point out in the comments, this may not work on some platforms (in those cases, upgrade to at least 1.487 so that you can use the official uninstall feature).
To manually uninstall a plugin, stop Hudson/Jenkins, go to your HUDSON_HOME/plugins directory and remove both the .hpi file and the folder with the same name. So, if you were going to remove the CVS plugin, you would remove both the cvs.hpi file and the cvs directory.
After that, restart Hudson/Jenkins and the plugin won't be there anymore.
Jenkins 1.487 adds a UI for uninstalling plugins: JENKINS-3070
Deleting the <plugin>.hpi file and corresponding <plugin>-plugin directory will effectively remove the plugin.
However, if you have configured parameters that belong to the plugin within your jobs your Hudson or tomcat logs may contain *CannotResolveClassException: hudson.plugins ... * exceptions because it attempts to load the plugin. This can result in build failures even if build is successful.
To fix that,
go to the job configuration and save it again. This should get rid of the plugin reference
if not, go into the hudson home jobs directory and open the config.xml found under the folder named after the job and remove the reference to the plugin
restart hudson
Hudson Plugins explains that some core plugins ("Tier 1" plugins, as they are called) are shipped with Hudson itself, and I assume cannot be deleted therefore.
You can disable it using the Jenkins » Plugin Manager. Go to Installed tab and untick the plugins you want to uninstall and restart Jenkins. Though it does not unintall, at least keeps it away from appearing from configuration pages..