This is mostly what I use too. Additionally, on images with high ISO I usually add the profiled denoise module, often without changing the default values. If the image has a lot of noise, I sometimes use the preset that only reduces chroma noise (so the image stays grainy, but without the color mismatches)
crater2150
joined 5 months ago
...and all I hear is: "this stuff isn't ready yet" and "I'm going to be starring at Unicode glyphs the next time I have to tinker outside of my GUI".
This really isn't a zsh problem, but a "people putting too much stuff in a 'getting started' config".
I used zsh for 15 years before looking at any plug-in manager, you can get a lot of the good stuff like the completion by just going through the first-run wizard included in zsh. A lot of stuff is included directly with zsh, including various prompt themes (which is what that tutorial wants extra fonts for, because they use a fancy prompt with custom glyphs; I don't think any of the built-in ones need that)
Things like fuzzy history search with fzf is usually included with fzf's distro package and the additional zsh-completions package for less used or newer commands is also packaged by most distros. In my experience, a lot of the other plugins are stuff that could be a standalone script instead of a plug-in anyway.
In my experience, that is usually a problem with the GPU OpenCL drivers. Sadly, the Mesa OpenCL implementation didn't include image support when I last checked (you can check with
clinfo | grep "Image support"). For AMD cards you need to have either the "pro" driver or ROCM installed, both aren't packaged by all distros. Similar with Intel, don't know about Nvidia, but I'm sure if it works, it's only with the proprietary driver.I ended up installing darktable in an arch distrobox container, as arch has ROCM packages (in AUR) and ever since GPU acceleration is working fine.