I've been a very happy user of mise since when it was named rtx - before that I used asdf. Thanks, jdx, for creating this! And I found the blog post useful, as there seems to be several features that I was not aware of that I might want to adopt going forward. For instance the task sources and outputs was new to me!
I don't think you can choose 30 days. It is 5 years or no service. At least that's what it looks like to me, I did not find a way to accept the new policies without accepting 5 years.
Notice that other shells also has associative arrays, or at least zsh. I've found hyperpolyglot [0] to be a nice Rosetta stone for translating syntax between e.g. bash and zsh.
* A password manager (PasswordStore [0]), in which I may make entries without passwords but where I indicate my ID on a given account.
* A personal wiki in which I may indicate for something that I have an account connected to e.g. Google or whatever.
When I come to some service that I vaguely remember having used before, I will find the necessary info either in my personal notes or in my password manager.
> But somehow this suggests to me that I might have been doing something wrong. I use vim+ultisnips+(your excellent vimtex) while you use neovim. Out of curiousity, do you specifically set your python provider for your neovim in your config?
Yes, I do. I use a dedicated virtual environment for neovim which I create with the following snippet; then I set the `g:python3_host_prog` accordingly [0].
Just be aware that the marker based folding can be annoying to collaborators if you are working on documents with other authors. With a plugin like FastFold [0] you should be able to have fast folding with the expr foldtype.
I don't think this is a big problem with VimTeX; I've worked quite a lot on these things, and my personal experience is that VimTeX is now quite fast both with syntax highlighting and with folding; although for folding, you do want to use the various "hacks" like the manual fold option or a plugin like FastFold.
I use both Vim (with wiki.vim, a plugin I've made based on Vimwiki) and Anki. I find the combination is very powerful!
I keep a journal for work related stuff and a wiki/personal knowledge base for everything (both work and personal). I use Anki to memorize things I believe may be useful to have readily available and I use my wiki as an extended "long-term memory", sort of.
> But UltiSnips works terribly with neovim [1] [2]. Why? Because UltiSnips uses python, and neovim's python interface is 100x slower than vim's python interface. There are design decisions for this and I'm not trying to say that neovim is bad. I use both vim and neovim. But I use vim+UltiSnips+vimtex for writing LaTeX.
I'm using neovim with UltiSnips (and VimTeX), and I don't really have any big issues with it. I'm not saying you are wrongm but I do think the problem may be somewhat exagerated.
I think these rules are more or less the same in Scandinavia. The Norwegian rules are well explained at Arbeidstilsynet [0]. Basically 5 weeks per year, 6 weeks if you are 60 years old or older. Of course, people may have more vacation per contract, but in general, you can't have less.
Most Norwegians take about 4 weeks of vacation during July.
Cool! I've seen similar ideas before and made my own inspired by these some years ago. It's a simple bash script based on Flameshot [0] for taking the screenshot and Tesseract:
#!/usr/bin/env bash
rm -f /tmp/screen.png
flameshot gui -p /tmp/screen.png
tesseract \
-c page_separator="" \
-l "eng" \
--dpi 145 \
/tmp/screen.png /tmp/screen
if [ "$(wc -l < /tmp/screen.txt)" -eq 0 ]; then
notify-send "ocrmyscreen" "No text was detected!"
exit 1
fi
xclip /tmp/screen.txt
notify-send "ocrmyscreen" "$(cat /tmp/screen.txt)"
In Norway, self checkout is more or less scan-scan-scan-pay. It works well, in my experience, and most stores also have the traditional regular checkout.
I'm curious if the shop-lifting challenge is similar in Norway. I would expect not, since it is a very trusting society, but I have never seen any real numbers on this topic.