- Copy/Paste the function defined in
jira.sh
in you.bash_profile
or.bashrc
- Export
JIRA_ROOT
variable in your environemnt (most likely in your.bash_profile
/.bashrc
as well) :export JIRA_ROOT='https://jira.yourdomain.com/'
jira [issue]
/** | |
* 1. Go to "Likes" section of your profile (e.g. https://twitter.com/<your_twix_handle>/likes) | |
* 2. Open browser Console (Cmd + Option + I on Mac, F12 otherwise?) | |
* 3. Copy/Paste the script and press enter to run it. | |
* | |
* At some point, depending on the number of items you need to process, you might see the following error in the console: | |
* > "the server responded with a status of 429" | |
* That's TwiX rate limiting. Reload the page, wait a few minutes/hours before trying again, and you should be fine. | |
* Inspired from https://stackoverflow.com/a/72515907 | |
*/ |
/** | |
* $.pinger | |
* | |
* If your page runs into an iframe hosted by another domain, you may want to keep the session open. | |
* This plugin automates the "ping URL" process and provides some options. | |
* | |
* The pinger will ask the given URL every 'interval' minutes if it detects | |
* some activity by listening to the events listed in 'listen' parameter. | |
* | |
* Have a look to the 'defaults' variable below for further details about available parameters and default values. |
#!/bin/sh | |
# | |
# This pre-commit hook run `shellcheck` against your code when you go to commit. | |
# See: http://www.shellcheck.net/ | |
# | |
# To use this script copy it to .git/hooks/pre-commit and make it executable. | |
# Work out what to diff against, really HEAD will work for any established repository. | |
if git rev-parse --verify HEAD >/dev/null 2>&1 | |
then |
;(function($) { | |
/* | |
* jQuery Observer pattern | |
* inspired by @addyosmani 's code | |
* see: http://addyosmani.com/resources/essentialjsdesignpatterns/book/#highlighter_506612 | |
*/ | |
var topics = []; | |
function getTopic(id) { | |
var callbacks; | |
topic = id && topics[id]; |
Here is the results of a few tests I ran on various "TV browsers" environments.
I wanted to know how those TV environements behaves regarding keyboard events. Is there a reliable standard way of handling remote controllers that we can work with?
The simple JS script I used to test keyCode behavior is available here : jsbin.com/OqAhIcA/13
Tested devices :
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta name="description" content="A Simple Video Instant Preview Demo" /> | |
<meta charset=utf-8 /> | |
<title>JS Bin</title> | |
</head> | |
<body> | |
<video id="video" controls></video> | |
<form> |
See also : 'lsyncd'