Meanwhile, my modern LCD makes a high pitched noise thanks to coil whine.

Rainbow-kahvi sai taannoin UTZ-sertifioinnin, mikä on hyvä juttu ja kannatan sitä ehdottomasti. Ikävä kyllä pakkaus vaihtui samalla hieman erityyppiseen, ja tämä uudempi, UTZ-sertifioidun pakkaus on nyt paljon aiempaa hankalampi avattava. Se vanha pakkaus aukesi ihan helposti ylhäältä käsin vetäen. Tämä uusi pitää avata saksilla ja jää vielä sittenkin hankalan muotoiseksi, niin että kahvinmuruja menee aina väkisinkin vähän pöydälle ja siis hukkaan.

Sarjat

Minä haikailen Perryä, mutta aika kuvaavaa on että olisin väittänyt sitä päärynänmakuiseksi, kun se näköjään olikin todellisuudessa sitruunanmakuinen. Tuskin siis maistuisikaan nyt niin hyvältä kuin nostalgiahermo yrittää minulle uskotella. (Muistan kyllä päärynänmakuisiakin merkkejä, joku Mikki Hiiri -sellainen ainakin oli.)

Mildly off topic: I’m slightly surprised that Disney allow preaching work there. I thought they generally try to appear neutral wrt. to religions, politics and such, and I’d think the easiest way to achieve that here would be an outright ban on all evangelizing within the park. I mean, if they allow the JW there, that opens the door for the likes of Westboro Baptist Church, whom Disney would then either have to also allow in or (more likely) deny. The latter could then be used to argue that they aren’t truly unbiased.

I wonder if this allowance is something they are required to do by the 1st amendment.

I think your CMS has eaten up all the XML tags above, only the settings’ values and comments are visible.

== Background ==

Reporting from Xenial, but this is currently reproducible in Artsy too.

$ locale
LANG=fi_FI.UTF-8
LANGUAGE=fi:en
LC_CTYPE=fi_FI.UTF-8
LC_NUMERIC=”fi_FI.UTF-8″
LC_TIME=”fi_FI.UTF-8″
LC_COLLATE=fi_FI.UTF-8
LC_MONETARY=”fi_FI.UTF-8″
LC_MESSAGES=fi_FI.UTF-8
LC_PAPER=”fi_FI.UTF-8″
LC_NAME=”fi_FI.UTF-8″
LC_ADDRESS=”fi_FI.UTF-8″
LC_TELEPHONE=”fi_FI.UTF-8″
LC_MEASUREMENT=”fi_FI.UTF-8″
LC_IDENTIFICATION=”fi_FI.UTF-8″
LC_ALL=

== Test case ==

$ git init test
$ cd test
$ echo ”foo” > bär
$ git add [hit tab key]
$ git add \”b\\303\\244r\” [hit enter]

== What happens ==

fatal: pathspec ’”b\303\244r”’ did not match any files

== What I expect to happen ==

For the filename to be correctly completed, like with ls:

$ mkdir test2
$ cd test2
$ echo ”foo” > bär
$ ls [hit tab key]
$ ls bär [hit enter]
bär

From what romainl only linked to (the relevant parts of links should be quoted when answering):

You can tell syntastic which checkers to run for a given filetype by setting a variable ’g:syntastic__checkers’ to a list of checkers, e.g.
let g:syntastic_php_checkers = [”php”, ”phpcs”, ”phpmd”]

As for your question about invocation: according to the FAQ, the ”command line is constructed using an internal function named makeprgBuild(), which provides a number of options that allow you to customise every part of the command that gets run. You can set these options using global variables”. (See this answer.)

For optimizing files in-place with jpegtran, especially from scripts and when dealing with lots of pictures, it’s handy to be able to specify input file as -outfile.

But there’s a catch:

Steps to reproduce:
0. Have a large JPEG file, or, alternatively, somewhat slow CPU
1. `jpegtran -optimize -copy all -perfect -outfile large.jpg large.jpg`
2. Hit Ctrl-C before the command finishes

Result:
You now have a broken large.jpg with only part, if any, of the image data remaining.

What I expect to happen:
To have large.jpg as it was before I invoked jpegtran.

Workarounds:
Obviously the traditional workaround of specifying an intermediate temporary output file, then replacing the original with the temporary file only once jpegtran has finished.

But how does the latter scenario differ from one where `mktemp` is invoked without `-u`? Even if the file is created (as opposed to just the name), nothing prevents another process from writing to the same file once it has been created.