Hello,
Thanks for tldraw, it is really great!
I noticed that the background is not really white (RGB: 248, 249, 250). When the drawing is exported to PNG and imported in Word (for example), the background is therefore not white (or transparent) and it is not "nice".
Could you change the background to white or an option to do it?
Thanks :-)
| Q | A |
|---|---|
| Bug report? | no |
| Feature request? | yes |
| Library version | 1.13.0 |
Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.
Maybe something like:
'parameters' => '--format=json -d memo
The fix for #3307 was done for GitRepository only. This bug tracks the rest of the repositories.
Since the default output is meant to be human-readable, would it make sense to add thousands separators to make the output more easily readable?
Lite-xl doesn't remember how i left the zoom level,
I mean when i use it i zoom it a little bit for readability and when i quit and reopen it, that time it doesn't remember how i left it off i.e the zoom level.
I'm running cargo-crev 0.17, installed via cargo install, on Debian Bullseye.
A user I trust on a "medium" level disappeared from cargo crev id query trusted. (I initially attributed that to me changing that user's level from "low" to "medium", but I think it was really caused by cargo crev fetch all that I ran about the same time.) I had to play with --depth to understand that this is
Please add C# syntax support.
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
Add a description, image, and links to the code topic page so that developers can more easily learn about it.
To associate your repository with the code topic, visit your repo's landing page and select "manage topics."
Perhaps we should document this issue in the FAQ? Using pre-commit with Black is pretty common (and it's not always instantly clear it passes all of the files to the hook directly bypassing any file discovery the hook may implement). I'd suggest pre-commit's exclude configurations first, and then black's force-exclude.
_Originally posted by @ichard26 in psf/black#3013