Dionisio E Alonso
Dionisio E Alonso
> We have decided that wildcards are unnecessary with the current implementation. I think they are necessary. For instance, at work we have all the testing sites at say, *.playdev.net,...
> I compiled this using Rust stable (**1.27.2**) now **1.28** > > Though I think upstream could use cargo-deb to build some binaries, however providing a Debian stable package is...
``` $ apt policy rustc rustc: Candidate: 1.28.0+dfsg1-2 Version table: 1.29.0+dfsg1-1 500 500 http://httpredir.debian.org/debian sid/main amd64 Packages 1.28.0+dfsg1-2 990 990 http://httpredir.debian.org/debian testing/main amd64 Packages ``` this is why I am...
@XVilka you do realize that's a false statement, don't you? https://blog.rust-lang.org/2019/02/28/Rust-1.33.0.html ``` baco@aurora:~$ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux buster/sid" NAME="Debian GNU/Linux" ``` ``` baco@aurora:~$ apt policy rustc rustc: Installed: 1.32.0+dfsg1-1 Candidate:...
I understand, but the setup function is Lua. For the time being I have not migrated my `init.vim` nor `ginit.vim` to `init.lua` (and I can not find the time to...
Ok, many things happening here: 1. the setting was renamed, used to be `g:vscode_transparent`, the same termination as the Lua setting, but it suddenly change to `g:vscode_transparency`: https://github.com/Mofiqul/vscode.nvim/commit/ecb73a11 .. https://github.com/Mofiqul/vscode.nvim/commit/5b812ce5...
> I won't change it to that because the code that checks for the `vim.g.vscode_*` variables is only there for backwards compatibility. Wouldn't be as easy as: ```lua transparent =...
> ```lua > local c = require('vscode.colors') > require('vscode').setup({ > transparent = false, > group_overrides = { > Normal = { fg=c.vscFront, bg= (vim.g.colors_name and vim.g.colors_name == 'vscode') and c.vscBack...
Reviewing other GTK4 apps (GNOME's Text-Editor and Builder), when underlining spelling mistakes, the GTK4 decoration is a dotted line. It seems de default has changed from curly line to a...
Ok, my bad about the update flag, I missed that option. For the wirte part, sure! There are many many fields beets fetches from MusicBrainz when importing a release; among...