Skip to content

Instantly share code, notes, and snippets.

View dflock's full-sized avatar

Duncan Lock dflock

View GitHub Profile
@dflock
dflock / dark-theme.css
Created June 30, 2016 02:31
Dark theme for Just Read Chrome extension.
@font-face {
font-family: 'Source Sans Pro Semibold';
src: url("chrome-extension://dgmanlpmmkibanfdgjocnabmcaclkmod/fonts/SourceSansPro-Semibold.ttf");
}
@font-face {
font-family: 'Source Sans Pro Bold';
src: url("chrome-extension://dgmanlpmmkibanfdgjocnabmcaclkmod/fonts/SourceSansPro-Bold.ttf");
}
@font-face {
font-family: 'Source Sans Pro Light';
@dflock
dflock / nucleotide_name_from_number.sh
Created December 31, 2015 06:55
Returns the Definition from Nucleotide (http://www.ncbi.nlm.nih.gov/), given the accession number.
#!/bin/bash
if [ -z "$1" ]; then
echo "Returns the Definition from Nucleotide (http://www.ncbi.nlm.nih.gov/), given the accession number."
echo "Usage:"
echo " $0 <accession_number>"
echo "eg: $0 U49845"
echo "Returns the definition/name string"
echo "eg: Saccharomyces cerevisiae TCP1-beta gene, partial cds; and Axl2p (AXL2) and Rev7p (REV7) genes, complete cds"
exit
@dflock
dflock / README.md
Last active April 9, 2019 10:57
Docker bash aliases.

docker_aliases

Docker bash aliases - new bash shell commands to make working with Docker containers & images easier.

Installation

Save the docker_aliases.sh file to your home directory. Rename it to .docker_aliases and add this to your ~/.bashrc file somewhere:

if [ -f ~/.docker_aliases ]; then
# Generated by Vagrant
dev ansible_ssh_host=127.0.0.1 ansible_ssh_port=2222
[all_boxes]
dev
[hadoop_name_nodes]
dev
@dflock
dflock / keybase.md
Created March 31, 2014 05:51
keybase.md

Keybase proof

I hereby claim:

  • I am dflock on github.
  • I am duncanlock (https://keybase.io/duncanlock) on keybase.
  • I have a public key whose fingerprint is CE38 BEB1 0A59 D8A8 F9A2 537C 3D48 3E3F 091B 310E

To claim this, I am signing this object:

We can make this file beautiful and searchable if this error is corrected: It looks like row 2 should actually have 17 columns, instead of 15 in line 1.
id summary reporter owner description type status priority milestone component version severity resolution keywords cc changelog apichanges
886 Add support for Master tickets dmurphy25@… nkantrowitz "It would be cool if you could create master tickets that other tickets refer to. Work could then be broken down into chunks (and assigned to different people), but the master ticket could only be closed when all referring tickets had been resolved.
You could also have it so that referring tickets are excluded from the Roadmap ticket counts." enhancement reopened highest next-major-releases ticket system devel major relations marcandre.lureau@… hwinkel@… mrovner@… trac@… dpeterson@… bruno@… shishz@… alecclews@… jorvis@… jkletsky@… peter.merel@… Andreas.Podgurski@… nick+trac@… gerz@… daved@… josh.moore@… dlawson@… mark81@… carwyn@… tobias.roeser@… erikand@… patrik@… zeph.gillen@… janne@… m.galante@… dilshod@… fotos@… j.vargas@… trac-eolg@… planders@… trac@… Ingmar@… zhenxin0603@… luke@… motumboe@… munsey@… alex.c
We can make this file beautiful and searchable if this error is corrected: It looks like row 2 should actually have 17 columns, instead of 15 in line 1.
id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,changelog,apichanges
886,Add support for Master tickets,dmurphy25@…,nkantrowitz,"It would be cool if you could create master tickets that other tickets refer to. Work could then be broken down into chunks (and assigned to different people), but the master ticket could only be closed when all referring tickets had been resolved.
You could also have it so that referring tickets are excluded from the Roadmap ticket counts.",enhancement,reopened,highest,next-major-releases,ticket system,devel,major,,relations,marcandre.lureau@… hwinkel@… mrovner@… trac@… dpeterson@… bruno@… shishz@… alecclews@… jorvis@… jkletsky@… peter.merel@… Andreas.Podgurski@… nick+trac@… gerz@… daved@… josh.moore@… dlawson@… mark81@… carwyn@… tobias.roeser@… erikand@… patrik@… zeph.gillen@… janne@… m.galante@… dilshod@… fotos@… j.vargas@… trac-eolg@… planders@… trac@… Ingmar@… zhenxin0603@… luke@… motumboe@… munsey@… alex.c
We can make this file beautiful and searchable if this error is corrected: Unclosed quoted field in line 3.
ticket,summary,component,version,milestone,type,severity,owner,status,created,_changetime,_description,_reporter
886,Add support for Master tickets,ticket system,devel,next-major-releases,enhancement,major,nkantrowitz,reopened,2004-11-05T12:44:10+01:00,2012-11-05T09:34:19+01:00,"It would be cool if you could create master tickets that other tickets refer to. Work could then be broken down into chunks (and assigned to different people), but the master ticket could only be closed when all referring tickets had been resolved.
You could also have it so that referring tickets are excluded from the Roadmap ticket counts.",dmurphy25@…
10755,CommitTicketUpdater does not allow user to define what state to jump to,ticket system,0.12.3,unscheduled,enhancement,major,,new,2012-07-02T22:27:07+02:00,2013-04-30T20:15:56+02:00,"The CommitTicketUpdater will only ever close a ticket. In general, the closed state is for when no more work is to be done, aka ''after'' QA has verified the fix. Trac should allow configuration of wh
This file has been truncated, but you can view the full file.
<!--
RSS generated by JIRA (6.0-rc1#6085-sha1:c75e7300f4c262d9e27cea8c81b31271cb2eb431) at Tue May 14 11:43:45 CDT 2013
It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
https://jira.atlassian.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=text%7E%22greenhopper+api+plugin%22&tempMax=200&field=key&field=summary
-->
<!-- If you wish to do custom client-side styling of RSS, uncomment this:
<?xml-stylesheet href="https://jira.atlassian.com/styles/jiraxml2html.xsl" type="text/xsl"?>
<!--
RSS generated by JIRA (6.0-rc1#6085-sha1:c75e7300f4c262d9e27cea8c81b31271cb2eb431) at Tue May 14 11:28:29 CDT 2013
It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
https://jira.atlassian.com/si/jira.issueviews:issue-xml/WBS-49/WBS-49.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>