In the middle of the desert you can say anything you want
Things I can pass to
mypy --disallow-any-generics can be configured in
[tool.mypy] show_error_codes = true warn_unused_ignores = false disallow_any_generics = false ignore_missing_imports = true
Is nice! It transparently got all vim’s configs plugins and they seems to work!
set runtimepath^=~/.vim runtimepath+=~/.vim/after let &packpath = &runtimepath source ~/.vimrc
deoplete for faster completions, jedi-vim for goto and friends.
let g:jedi#usages_command = "<leader>n" let g:jedi#goto_command = "<leader>d" let g:jedi#rename_command = "<leader>r" let g:jedi#documentation_command = "K"
But it didn’t work for packages not living inside the default python environment, and manually each venv would be tedious. poet-v to the rescue!
let g:poetv_executables = ['poetry'] map <leader>va :PoetvActivate<CR>
To select on enter, had to add this to vimrc/nvimrc:
In general deoplete faq in vim help is much longer than the one on their github repo.
nvie/vim-flake8: Flake8 plugin for Vim,
<F7> to run it on the current buffer.
Describes a setup that uses poetry, black, flake8, pytest, mypy and new to me
isort to sort imports.
The Fast track section has a TL;DR of how to create that setup.
I also really like this intro to poetry: Package Python Projects the Proper Way with Poetry
xdg-settings gets the award for least intuitive interface ever.
xdg-settings get default-web-browserwas firefox.
xdg-settings set default-web-browser qutebrowser.desktopis quiet
xdg-settings get default-web-browseris still firefox.
2, which is
file not foundbasically.
--help), and having
--listas a parameter, but
> xdg-settings set default-web-browser xdg-settings: invalid application name
Created a file with
-> in the name, it didn’t appear on mobile, checked sync logs - not there because the name is “illegal”. Is not allowing
> a global thing or only for Android?
For an executable (..qutebrowser.sh) to be an ‘application’, it has to have a
.desktop file in
For qutebrowser, created this:
[Desktop Entry] Name=Qutebrowser Comment=Qutebrowser Exec="~/.local/bin/qb %f" Terminal=true Type=Application StartupNotify=true MimeType=application/x-www-browser; Keywords=python;
sudo desktop-file-install qutebrowser.desktopthen put it in
This describes all the things needed to set qb as default browser: New option for open link with browser · Issue #716 · RocketChat/Rocket.Chat.Electron
At the end, symlinked
/usr/bin/qb to it’s location in my home folder, maybe the universe will come crashing on me but then I don’t have to mess with the usual creation of bash runner scripts in
~/.local/bin/.. to have it globally available. Including for things like
update-alternatives that seem to want a global thing.
[ Main docu for this is UnityLaunchersAndDesktopFiles - Community Help Wiki. ↩︎
(learned it when it failed because of no
screen -R screenameattaches a screen with this name or creates it.
<C-a> :sessionname newscreennamerenames an existing instance
~/.screenrcexists. Some useful settings:
defscrollback 200000for “infinite” scrollback
deflog onto log everything automatically
screenwhen no screen is installed1 : connect to it with ssh from any other server that does have screen installed.
thought of this myself and really proud of it ↩︎
ssh -L 6006:127.0.0.1:6006 servername -p 1234maps port 6006 of
localhost:6006, using ssh that’s running there on port
If you do it often, you can add these settings to
Host pf Hostname servername LocalForward 6007 localhost:6007 LocalForward 6006 localhost:6006 Port 1234
…and then you connect to it as
sshfs mounts a remote folder to one on the local filesystem.
sshfs server:/data/me ./local-folder -p 12345
sshfs -o Ciphers=aes128-ctr -o Compression=no server:/data/me ./local-folder -p 12345may be faster
When I tried it at the beginning it was horribly slow, the problem was the
zsh prompt that had info about the current git repo. Disabling it or using bash solved the issue.
If you copy a directory, there may be symlinks there, that will also show fine when you
cat or whatever. What saved me was their different color in the terminal.
.. How did people do this in b/w terminals?
TODO How can I avoid this in the future, given my heavy symlinks use?