It would be cool to add Google Translate support, because most likely Google Translate is better than Microsoft Translate.

And maybe it would be good idea to use Google Apps Script, because it has a free unlimited Google Translate. Here is an [example article](https://techstreams.github.io/2016/01/07/translation-automation-with-wor

At some point we should probably upgrade the argument parser to use nom version 5. They got rid of most of the macro magic. I am not familiar with nom (although interested), but there is an upgrade guide that should hopefully make the transition a bit more smooth: https://github.com/Geal/nom/blob/master/doc/upgrading_to_nom_5.md

The below ruby code:

foo = 123

Gives foo a face of tree-sitter-hl-face:function.method which isn't correct (it should be variable or similar). I poked around a bit and my guess would be the ((identifier) @function.method (#is-not? local)) highlight rule is matching too much suggesting the locals stuff isn't working (?).

I'm guessing it is an issue here vs tree-sitter-r

server error: zfs send dry failed: could not parse zfs send -n output: line "incremental\tzroot/ROOT/default@zrepl_20210313_194422_000\tzroot/ROOT/default@zrepl_20210314_195111_000\t18446744073614344448": cannot not parse size: strconv.ParseInt: parsing "18446744073614344448": value out of range

When I start Anki 2.0, "Your Incremental Reading settings file has been modified for compatibility reasons. …", and my custom QuickKey is not there when I start Anki 2.1 after that.

Description

During the installation screen, when clicking back from the plugin install screen, collections get duplicated

Steps to Reproduce

1. Run the installer as usual until reaching the plugin install screen
2. press back

or

1. Run the installer as usual until reaching the plugin install screen
2. Select any of the official plugins to install
3. press back

A good testing regime could include the following:

• Perform an initial backup
• Verify volume
• Perform an incremental backup
• Verify volume
• Prune first backup
• Verify volume
• Diff volume (cross-check with source vol data)

Changing program_name in the code could allow the test data set to be created under a different base folder name without interfering with real-life back