- Navigate to Eclipse's installation folder
- Open eclipse.ini and find the '-product' flag. Mine was something like this: -product org.eclipse.epp.package.jee.product
- Open the plugins folder and look for your product folder. It looks similar to your product flag (mine was org.eclipse.epp.package.jee_4.4.0.20140612-0500)
- All you need to do now is to replace the png files (javaee-ide_x32.png, javaee-ide_x64.png, ...) with the icons that you want.
- (Optional) In case you want to use the brand new "flatty" icon, just navigate to plugins\org.eclipse.platform_4.4.0.v20140606-1215, copy the flat png icons and repeat the step 4.
If you clone a git repo that enforces a linebreak-style: unix
on a Windows machine then ESLint will probably throw the warning below even if you've made no local changes.
Expected linebreaks to be LF but found CRLF. linebreak-style
In order to fix this you'll need to tell git to default to Unix style line endings rather that OS defaults.
git config --global core.eol lf
git config --global core.autocrlf input
links for old versions of Docker for Mac
Docker provides download links in release note. They promised that
(we) will also include download links in release notes for future releases.
Note:
- Download Git for Windows Portable (Comes with Git Bash included)
- Download Node with npm
- Create Applications folder in C: drive so that you have the proper permissions
C:\Applications
- Install Git for Windows inside of Applications directory
C:\Applications\Git
- Install Node inside of Applications directory
Firstly, what is <details>
<summary>
?
The HTML Details Element (
<details>
) creates a disclosure widget in which information is visible only when the widget is toggled into an "open" state. A summary or label can be provided using the<summary>
element. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details.
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
<^>!'::Send `` ; AltGr + ' => ` | |
<^>!vkDD::Send ~ ; AltGr + ì => ~ |
defaults write com.apple.Dock appswitcher-all-displays -bool true | |
killall Dock |
With this AutoHotKey script, you can use most macOS style shortcuts (eg, cmd+c, cmd+v, ...) on Windows with a standard PC keyboard.
Note that
- You should disable the
Between input languages
shotcut fromControl Panel\Clock, Language, and Region\Language\Advanced settings > Change lanugage bar hot keys
because it conflicts withcmd + shift + ↑ / ↓ / ← / →
(select text between cursor and top / bottom / beginning of line / end of line) - you shouldn't change the modifier keys mapping with keyboard DIP. This script assumes you use a standard PC keyboard layout, and wish to use shortcuts as if it was a mac keyboard layout.