| # Note that while this file is in our config folder, it is | |
| # symlinked to our site folders, so paths are relative from there | |
| # Require gems and Compass plugins | |
| # require 'rgbapng' | |
| # require 'compass-fancybox-plugin' | |
| require 'compass-growl' | |
| # General | |
| output_style = :expanded |
| # source: http://st-on-it.blogspot.com/2010/01/how-to-move-folders-between-git.html | |
| # First of all you need to have a clean clone of the source repository so we didn't screw the things up. | |
| git clone git://server.com/my-repo1.git | |
| # After that you need to do some preparations on the source repository, nuking all the entries except the folder you need to move. Use the following command | |
| git filter-branch --subdirectory-filter your_dir -- -- all | |
| # This will nuke all the other entries and their history, creating a clean git repository that contains only data and history from the directory you need. If you need to move several folders, you have to collect them in a single directory using the git mv command. |
| @ECHO OFF | |
| SETLOCAL | |
| SET VERSION=%1 | |
| SET NUGET=buildsupport\nuget.exe | |
| FOR %%G IN (packaging\nuget\*.nuspec) DO ( | |
| %NUGET% pack %%G -Version %VERSION% -Symbols -o artifacts | |
| ) |
This is a text consisting of a list of pangrams, sourced from the Wikipedia article, including characters from many common languages featuring true alphabets (mostly Latin-extended, Cyrillic and Greek). This is useful as an informal Unicode coverage tests for fonts, as well as a general generic prose test for fonts.
The quick brown fox jumps over the lazy dog.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
Docker issues are frequently logged for DNS resolution in containers because it doens't inhert or get values for DNS from NetworkManager which leverages a built in dnsmasq to inteligently manage DNS.
sudo bash -c "echo listen-address=$(ip -4 addr show dev docker0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}') > /etc/NetworkManager/dnsmasq.d/docker-bridge"
sudo systemctl reload NetworkManager
sudo bash -c 'echo -e "{\n\t\"dns\": [\"$(ip -4 addr show dev docker0 | grep -oP "(?<=inet\s)\d+(\.\d+){3}")\"]\n}" > /etc/docker/daemon.json'
sudo systemctl restart docker
| /** | |
| * @license Copyright 2020 - Chris West - MIT Licensed | |
| * @see https://www.yourjs.com/blog/snippet-toggle-fullscreen/ | |
| * Either toggles the fullscreen view on the document or a specified element or | |
| * turns the fullscreen view on or off depending on the optional value passed | |
| * in. | |
| * @param opt_elem {Element|undefined|null} | |
| * The element that should be targeted for fullscreen viewing. | |
| * @param opt_value {?boolean=} | |
| * Optional. If not given or undefined or null fullscreen will simply be |
rebase vs merge).rebase vs merge)reset vs checkout vs revert)git rev-parse)pull vs fetch)stash vs branch)reset vs checkout vs revert)
I've worked with AngularJS for many years now and still use it in production today. Even though you can't call it ideal, given its historically-formed architecture, nobody would argue that it became quite a milestone not only for evolution of JS frameworks, but for the whole web.
It's 2017 and every new product/project has to choose a framework for development. For a long time I was sure that new Angular 2/4 (just Angular below) will become the main trend for enterprise development for years to come. I wasn't even thinking of working with something else.
Today I refuse to use it in my next project myself.