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
Related
I have the 4.0.3 Octave version on my machine.
and I would like to upgrade my version using windows.
Can someone tell me please the steps to follow?
Thanks.
If you want to remove v4.0.3, the complete answer will depend on how you installed that version in the first place.
If you used an executable installer, then there should be an 'uninstall' option available. On Windows 10, you can sometimes right click on the shortcut in the startmenu and an Uninstall option will appear. Otherwise you can follow the directions at this link to navigate through the Settings to the Apps & Features window, which lists everything installed and will provide an Uninstall option.
If you used a zip package to 'install' Octave 4.0.3 just by unzipping it to a folder on your hard drive, then no uninstall process is necessary. you can just delete the folder and shortcuts manually.
You can have multiple octave versions installed next to each other, the folders will have version numbers to prevent them from overwriting themselves.
To install the latest version (5.1.0 as of this answer, although 5.2.0 will be released very soon):
You can find the installation files for Windows by going to the Octave download page and clicking 'Windows'. There will be several file options there. Most people choose the first one (octave-5.1.0-w64-installer.exe) for 64bit systems. You can just download that or one of the other .exe versions, execute that program, and follow the prompts. If for some reason you would rather download a zip package and do a manual setup, I suggest you follow the instructions at the Octave for Microsoft Windows Wiki page to make sure everything is configured correctly.
I was used to the phpfmt plugin for Sublime Text, and I'm not able to install it on a fresh installation : the package controller does not seem to find it anymore.
While waiting for a fix, I tried to copy/paste phpfmt folder from Sublime Text's packages folder to my new laptop, but it doesn't seem to work : on the first launch, the plugin is recognized but its directory is deleted.
How can I manually install this plugin ?
As you can see on the Package Control page you linked, the package only supports Sublime Text 3. There's a post on Y Combinator explaining the original author has deleted his version of the package. There is a guide on how to downgrade the package, but I'm not sure that includes Sublime Text 2.
I found this plugint SublimePaneNavigation, and from the fitures it looks great but it's suppouse to be only for sublime 2, I cant find it on sublime 3 package control. Can I install it some other way, on a Sublime text 3?
SublimePaneNavigation
SublimePanelNavigation
From what I can tell this plugin should work in ST3, but you'll have to install it yourself to find out. Go to your Packages directory (select Preferences -> Browse Packages... to find it) via the command line, and (assuming you have git installed) run the following command:
git clone https://github.com/borist/SublimePaneNavigation.git
It should then be installed.
When I go to browse packages in Sublime Text 2, the packages folder is full of all the plugins I wanted like Zen coding and SidebarEnhancements. My installed packages folder only has package control in it though. Should other installed packages be located in here?
SidebarEnhancements, for example, does not work, even though it is in the packages folder. If I right click the sidebar I just get the "close" option. I've been trying to figure this out for weeks, and I figured I would just ask here and see if anyone could tell me what I need to do after I have the package in the packages folder, if anything.
With Package Control in Sublime Text 2, you really need to become cozy with a couple of different things to make it all work:
Always look up a package in the wbond community. There you'll be able to see how many people have installed that package (the more popular, the better) as well as the documentation on the package (if any).
Menu Items under Prefs > Package Control. Here you can install, remove or see a list of all installed packages.
Prefs > Package Settings. Here you'll find the settings that can be tinkered with as well as shortcut keys that are available. Make sure to make any changes in the User Settings, rather than the Default Settings. Otherwise, your settings will be overwritten when that package is updated.
CTRL+SHIFT+P. This will bring up a menu where you can look up a lot of the functions your installed packages can do. Just start typing and it will start filtering.
Here is a link to a shorter and to the point description:
http://www.granneman.com/webdev/editors/sublime-text/packages/how-to-install-and-use-package-control/
The steps are:
Install package control.
Go to http://wbond.net/sublime_packages/package_control/installation and grab the install code.
In Sublime Text 2 open the console (Ctrl+`) and paste the code.
Restart Sublime Text 2.
Open command palette via Command+Shift+P (Mac OSX) or Ctrl+Shift+P (Windows).
Start typing Package Control and choose the package you are looking for.
Try using Sublime Package Control to install your packages.
Also take a look at these tips
The Installed Packages Directory You will find this directory in the
data directory. It contains a copy of every sublime-package installed.
Used to restore Packages
So, you shouldn't put any plugin to this folder.
For getting works of SidebarEnhancements plugin try to disable and reenable this plugin with using Package Control. If it doesn't work then try to remove folder "SidebarEnhancements" from "Packages" folder and install it again via Package Control.
You may try to install Package Control first by following simple instructions available at Installation Guide (which is like 1. Open the Console, 2. Paste the code).
Then please check Package Docs Control Usage for Basic Functionality:
Package Control is driven by the Command Pallete. To open the pallete,
press Ctrl+Shift+P (Win, Linux) or CMD+Shift+P (OS X). All Package
Control commands begin with Package Control:, so start by typing
Package.
The command pallete will now show a number of commands. Most users
will be interested in the following:
Install Package
Show a list of all available packages that are available for install.
This will include all of the packages from the default channel, plus
any from repositories you have added.
This recently worked for me. You just need to add to your packages, so that the package manager would be aware of the packages:
Add the Sublime Text 2 Repository to your Synaptic Package Manager:
sudo add-apt-repository ppa:webupd8team/sublime-text-2
Update
sudo apt-get update
Install Sublime Text:
sudo apt-get install sublime-text
Enabling a previously-installed Sublime Text package
If you have a subdirectory under Sublime Text 2\Packages for a package that isn't working, you may need to enable it.
Follow these steps to enable an installed package:
Preferences > Package Control > Enable Package
Select the package you want to enable from the list
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..