| #!/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 |
jira.sh in you .bash_profile or .bashrcJIRA_ROOT variable in your environemnt (most likely in your .bash_profile/.bashrc as well) : export JIRA_ROOT='https://jira.yourdomain.com/'jira [issue]
I hereby claim:
To claim this, I am signing this object:
> openssl genrsa -out key.pem 1024
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'
A simple bookmarklet to enable fullScreenMode in modern browsers.
loader.js code into a bookmark's location field.Ctrl+Enter to toogle fullscreen mode
| oaudard@work:~/Projects/sample-grails-project$ grailsenv | |
| GRAILS_HOME=/home/oaudard/dev-utils/grails | |
| grails | |
| grails-1.3.7 | |
| grails-1.3.8 | |
| grails-2.0.0 | |
| grails-2.0.1 | |
| grails-2.0.3 | |
| grails-2.0.4 | |
| grails-2.1.0 |