In the middle of the desert you can say anything you want
It’s possible not to use quotes if have just escaped stuff.
grep "\"Thinker" == grep \"Thinker
After finding a weird error in PIL, found this: Decompression bomb protection · Issue #515 · python-pillow/Pillow
Zip-bombs live on and prosper it seems :)
ncdu is a little neat program that first scans all the subdirectories of the current one and returns a nice visual navigable list.
d to delete selected folder, ? for help.
zip -r result-small.zip ./ -x 'unscoped/*'
-x is a regex of files to exclude. 1
dankbare aufgabe - “rewarding task”
diff -rq folder1 folder2 diffs contents of files inside the two folders.
daff diff can accept a -d parameter giving an epsilon, changes of numbers smaller than eps won’t be shown in the diff!
screen -r seems to accept not just the full name of the screen to attach, but even just the first letters!
Started to crash suddenly. git pull-ing didn’t help, but it and recreating the virtualenv using scripts/mkenv.py did.
der werkzeugkasten - toolbox/kit
This makes empty newlines be part of the fold: 1
" Ignore empty lines when using tabfold
:set foldignore=#<CR>
.. exists and works. 2
.one.two|=sort_by('.whatever')|.next.thing
(Also used in input of some other internal tools) They are: 1
Range Meaning
1.0 x >= 1.0 * The default Maven meaning for 1.0 is everything (,) but with 1.0 recommended. Obviously this doesn't work for enforcing versions here, so it has been redefined as a minimum version.
(,1.0] x <= 1.0
(,1.0) x < 1.0
[1.0] x == 1.0
[1.0,) x >= 1.0
(1.0,) x > 1.0
(1.0,2.0) 1.0 < x < 2.0
[1.0,2.0] 1.0 <= x <= 2.0
(,1.0],[1.2,) x <= 1.0 or x >= 1.2. Multiple sets are comma-separated
(,1.1),(1.1,) x != 1.1
literal_eval - ast - Python documentation - Kite
Safely evaluates Python expressions, nice to use for input.
may only consist of the following Python literal structures: strings, numbers, tuples, lists, dicts, booleans, and None.
To pipe output with jq to for example less preserving the colours, use -C. (Simialar to --color=always etc.)
jq . $filename -C | less
The script that sets dev/prod sets a variable to 1 if using dev. Based on that variable I get (or not) a red (B) in my zsh prompt.
Did these changes to the theme clean2.zsh-theme:
PROMPT='%{$fg[green]%}(%*/%!)$ZSH_USING_DEV%{$fg[$NCOLOR]%}%B%b%{$reset_color%}%{$fg[blue]%}%B%5c/%b%{$reset_color%} $(git_prompt_info)%(!.#.$) '
ZSH_USING_DEV=""
if [ "$USING_DEV" = "1" ]
then
ZSH_USING_DEV="%{$fg_bold[red]%}[B]%{$fg[$NCOLOR]%}"
fi
and in ~/.zsrhc
alias uc='. ~/s/setenv.sh p'
alias ud='. ~/s/setenv.sh d'
Using the usual ./ way doesn’t work!
Note the . ~/s.. in the script above.
Running it as ~/what.sh will create a new shell, export the new values there, and close it. Starting with a . will make it run the script without starting a new shell. 1
“Publish without notifying watchers” exits.
If I paste something from vim that has tabs in it in a Code block, in the Edit window it will look fine, but won’t at the end. Editing again will make it again look fine in the edit window. Moral: use spaces.
If you copypaste things from it to code blocks in jira/confluence it will start being weird. You can do expandtabs/retab to convert it to something that looks just like this with spaces when saved. Though feels suboptimal.