There is a demo shows you the minimal code and working example of how to set up a astro project to make use of Svelte compiles to Custom Element feature at https://stackblitz.com/edit/svelte-ce-on-astro-demo?file=README.md.
During a development of one of my web project, I discovered the gap between DaisyUI and tailwindcss on how each handles the system's theme (via prefers-color-scheme: dark) and manual theme override (via something like [data-theme] in case to give users to override against the system theme). Although the proposed the solution from me (you can see by continouly reading this gist) is not very complex, this can be confusing for people who have no similar experience on handing these. Hence sharing it as gist.
DaisyUI (v5) and tailwindcss (v4) both work (automatically) well with prefers-color-scheme: dark (aka following OS theme).
And DaisyUI allow you to override the theme with [data-theme], which tailwindcss does not work with it unless you manually override the config as describe as https://tailwindcss.com/docs/dark-mode#using-a-data-attribute.
This is about the script originally written for https://github.com/ryuheechul/dotfiles/commit/1c5795d4e69ad7ad8c191e3e96fe43155522739a#diff-4f848b5499b37dbeb494a252ab49d56831abb5b12dbd362ab5182f509f7ad97b
the script is pretty short and relatively simple, so I recommend you to read it but the gist is below
resolvectl for systemd-resolved with the parse information from the previous stephost device.home.arpa) should work as well as search domain (e.g. host device)
https://sre.google/sre-book/monitoring-distributed-systems/ ์ ๊ฐ๋จํ ์์ญ ๋ฐ ์์ฝ
Existing references I looked at before I went on trial and error until eventually I managed to make it work:
Note
Although links above were good references to look at so I didn't have to start from scratch, following none of them actually worked for me. Hence, I'm leaving my own note after figuring things out.
My situation:
| """ | |
| seems like hard coding is the only way to make literal type to accept anything to be literal | |
| (which makes sense if you think about it) | |
| """ | |
| from typing import Any, Literal | |
| my_literal_type = Literal["a", "b", "c"] |
| Regular expressions and data from | |
| http://lh3lh3.users.sourceforge.net/reb.shtml | |
| Regular expressions benchmarked: | |
| URI ([a-zA-Z][a-zA-Z0-9]*)://([^ /]+)(/[^ ]*)? | |
| Email ([^ @]+)@([^ @]+) | |
| Date ([0-9][0-9]?)/([0-9][0-9]?)/([0-9][0-9]([0-9][0-9])?) | |
| URI|Email ([a-zA-Z][a-zA-Z0-9]*)://([^ /]+)(/[^ ]*)?|([^ @]+)@([^ @]+) | |
| Word .*SCSI- |
I actually didn't really know about the difference between $@ and "$@" until now.
I always had assumed that "$@" is not desirable thinking this would deliver argsments as just one.
Turns out that's not true and you can read about it from man bash.
@ Expands to the positional parameters, starting from one. In contexts where
word splitting is performed, this expands each positional parameter to a separa
te word; if not within double quotes, these words are subject to word splitti
This is mostly a short version of information dump and sharing my experience regarding installing (and using) NixOS on Microsoft Surface Pro 8 device.