[ Update 2020-05-31: I won't be maintaining this page or responding to comments anymore (except for perhaps a few exceptional occasions). ]
Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).
It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.
| Replace this line with imperative summary | |
| An awesome description of WHY you did this work, not HOW/WHAT it does. | |
| The diff attached to commit should describe implementation (HOW) | |
| well-enough. | |
| # [TICKET-12] | |
| #------------------------------------------------^---------------------^ | |
| # 50^ 72^ |
Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.
My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important).
During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.
Here are main principles we use to write CSS for modern (IE11+) browsers:
| # Copyright 1999-2011 Gentoo Foundation | |
| # Distributed under the terms of the GNU General Public License v2 | |
| # | |
| # /etc/screenrc | |
| # | |
| # This is the system wide screenrc. | |
| # | |
| # You can use this file to change the default behavior of screen system wide | |
| # or copy it to ~/.screenrc and use it as a starting point for your own | |
| # settings. |
| # This task will notify Sentry via their API[1] that you have deployed | |
| # a new release. It uses the release timestamp as the `version` | |
| # (like 20151113182847) and the git ref as the optional `ref` value. | |
| # | |
| # This task requires several environment variables be set (or just | |
| # hardcode the values in here if you like living on the edge): | |
| # | |
| # ENV['SENTRY_API_ENDPOINT'] : API endpoint, https://app.getsentry.com | |
| # ENV['SENTRY_ORG'] : the organization for this app | |
| # ENV['SENTRY_PROJECT'] : the project for this app |
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
| <?php | |
| namespace Acme\Serializer\Normalizer; | |
| use Doctrine\Common\Collections\ArrayCollection; | |
| use Doctrine\Common\Collections\Collection; | |
| use Symfony\Component\Serializer\Normalizer\DenormalizerInterface; | |
| use Symfony\Component\Serializer\Normalizer\NormalizerInterface; | |
| use Symfony\Component\Serializer\Normalizer\SerializerAwareNormalizer; |
Sometimes you need to keep two upstreams in sync with eachother. For example, you might need to both push to your testing environment and your GitHub repo at the same time. In order to do this simultaneously in one git command, here's a little trick to add multiple push URLs to a single remote.
Once you have a remote set up for one of your upstreams, run these commands with:
git remote set-url --add --push [remote] [original repo URL]
git remote set-url --add --push [remote] [second repo URL]
Once set up, git remote -v should show two (push) URLs and one (fetch) URL. Something like this:
| #!/usr/bin/env bash | |
| # Colours picked from https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/ | |
| ### | |
| # Label definitions | |
| ### | |
| declare -A LABELS | |
| # Platform |
