This is pretty specific to my setup but the idea can be adapted to work with pretty much anything.
Go has a flag package which makes parsing command line arguments really easy.
package main
CONNECT | |
DELETE | |
GET | |
HEAD | |
OPTIONS | |
PATCH | |
POST | |
PUT | |
TRACE |
This is pretty specific to my setup but the idea can be adapted to work with pretty much anything.
Go has a flag package which makes parsing command line arguments really easy.
package main
Either copy the aliases from the .gitconfig
or run the commands in add-pr-alias.sh
Easily checkout local copies of pull requests from remotes:
git pr 4
- creates local branch pr/4
from the github upstream
(if it exists) or origin
remote and checks it outgit pr 4 someremote
- creates local branch pr/4
from someremote
remote and checks it out<build> | |
<plugins> | |
<plugin> | |
<groupId>org.apache.maven.plugins</groupId> | |
<artifactId>maven-shade-plugin</artifactId> | |
<version>2.0</version> | |
<configuration> | |
<createDependencyReducedPom>false</createDependencyReducedPom> | |
<filters> | |
<filter> |
Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
// see http://www.netlib.org/clapack/cblas/dgemv.c | |
package main | |
/* | |
#cgo LDFLAGS: -L/usr/lib/libblas -lblas | |
#include <stdlib.h> | |
extern void dgemv_(char* trans, int *m, int *n, double *alpha, | |
double *A, int *lda, double *x, int *incx, double *beta, double *y, | |
int *incy); | |
*/ |
This is a super basic beginners guide to Solr Lucene query syntax. We're going to cover running a straightforward query, as well as some of the more useful functionality such as filtering and creating facets. We'll point out some things you can't do and generally give you enough instruction so that you can get yourself into trouble.
To specify a list of fields to return instead of the default Solr response use fl
and provide a comma delimited list of fields:
prefix | publisher | journals | dois | |
---|---|---|---|---|
10.12679 | 0 | 0 | ||
10.7579 | 123Doc Education | 0 | 0 | |
10.3731 | 21st Century COE Program (Toplogical Science and Technology) | 1 | 40 | |
10.5775 | A. I. Rosu Cultural Scientific Foundation Fundatia cultural-stiintifica A. I. Rosu | 1 | 80 | |
10.4037 | AACN Publishing | 2 | 766 | |
10.1306 | AAPG/Datapages | 4 | 21817 | |
10.3183 | AB Svensk Papperstidning | 1 | 1550 | |
10.5769 | ABEAT - Associacao Brasileira de Especialistas em Alta Tecnologia | 1 | 57 | |
10.7597 | ACOPIOS - Revista Iberica de Mineralogia | 1 | 9 |
Do you have a WARC file of a website all downloaded and ready to be added to the Internet Archive? Great! You can do that with the Internet Archive's web-based uploader, but it's not ideal and it can't handle really big uploads. Here's how you can upload your WARC files to the IA from the command line, and without worrying about a size restriction.
First, you need to get your Access Key and Secret Key from the Internet Archive for the S3-like API. Here's where you can get that for your IA account: http://archive.org/account/s3.php Don't share those with other people!
Here's their documentation file about how to use it, if you need some extra help: http://archive.org/help/abouts3.txt
Next, you should copy the following files to a text file and edit them as needed:
export IA_S3_ACCESS_KEY="YOUR-ACCESS-KEY-FROM-THE-IA-GOES-HERE"
GitLab is open source software to collaborate on code (a GitHub clone to run on your own server). Clicking a blob (a file in a repository) in GitLab shows a nice rendering if GitLab supports the file type (e.g., images, Markdown documents), or its content as plain text otherwise. The patch described here adds support to GitLab for rendering IPython notebooks (.ipynb files).