Ronnie Dutta
Ronnie Dutta
I ended up having to use `persistent` and then manually adding back in the close-on-click-outside and close-on-escape functionality 1. Using `v-click-outside` directive with a handler: ```js onClickOutside = (e) =>...
I think I've got a fix for this, will open a PR soon
I can't reproduce the error in your first example `cylc message -p CUSTOM "abc::efg::hij::sdf"` Note because there is a colon after the first word `abc`, Cylc treats `abc` as a...
Ah, your real example fails validation because `/usr/bin` is not a word (in regex terms, a word is composed of alphanumeric chars)
Quick SCSS implementation: ```scss @for $i from 0 through 16 { .row-gap-#{$i}, .gap-#{$i} { row-gap: $i * 4px; } .col-gap-#{$i}, .gap-#{$i} { column-gap: $i * 4px; } } ```
Repro in Vuetify 3.3.3: [https://play.vuetifyjs.com/#...](https://play.vuetifyjs.com/#eNqlVLFu2zAQ/ZUrl7SAJaFwh8JwChft0K1D0SnKQFN0zZoiCZJSUBj+9x5JKaakBAkQTebd43vvjne+O5OvxpR9x8mGbD1vjaSef6kVwLYvqDHxZzy0VChgkjp3WxNDi881GZIx7RRlpz21gEjdcIkgd9QPv4ZwTcCLluvOY6L4mN0F+H0EfXwHP7jlIBxQGLmukEdrSO+k9hvKvNDKZSzRxd4r2DEp2GmmD7dwoNLxiXD4vkmN0ZylijQZbFtNGjOCRpePwawbwUdPraAq1ItVS6F4g02YmPsuqNR/0Jq33dTZT8MVNCl95c2cZVoDbNr3RD3hRCijtpm3LMQKL7y8Vpe+63skhXmTnrk4Uj71Qi++0aIRWTuWU/H0c2Xulh7G1OQlU33jqGMgzHpaAjykLZgMAR4ds8J4cNx3IS1ao62HM1h+gAscrG7hBtfqJoAZekBo/uIIex8H8kOezjqRA7ZVUkMdsiJJCj2a8q/TChf3HCdiSLiabCBGQgwthHNNjt4bt6kq1ii8hoMielsq7itl2mqHsMp2Kqxo0eh2ty7X5aeqEc7n4ZK7tthb/eC4RZKarDIZLw7/XiE1IKPCOikMoULSvQsSC+oK9XpuC8tVg0OJfyavq2h2La9qllpUFtQvtbpgv3F1T27WauZim+9Gk28qOZIFpvsgeFmR6BOV4wVy/x/x/8RF)
Why has this been closed? It's still reproduceable in the latest nightly build: [https://play.vuetifyjs.com/#...](https://play.vuetifyjs.com/#eNqFU7FOwzAQ/ZXDS0EiSdsw0CpFIBjYGBATYXAdl1p1Yst2ylD137nETeO0RXhJfPf87vnd+XNHrGHJk9bxtuZkTjLHSy2p4w95BZBtI6p1+9tuSioqYJJau8iJptF9Tg7JNm0ryjZLagCRquASQXatft4P4ZyAEyVXtcNENAnOAnysQa2v4JUbDsIChY6rhxylIb2Vys0pc0JVNmBpVSxdBY9MCrY5qQ8LWFFp+aBws56lwmjIkrQ0ASxLBsZ0oE7lMRi40ejYUiNo1dwXby1FxQs0YSDuRVCpvlGaM/VQ2ZvmFRQ+3fMGyoJaB9jQd0894EQoo6Y4tayJRU442d/Or74fvsKpSX8c7CgvdejfHp0ZEdhxPhWX2xWoO9fQpQad9PfrRh0Dzaz7R4Ab/woGQ4Bby4zQDix3dZMWpVbGwQ4MX8EeVkaVMMJnNWrADDUgNOw4wq7bgbwJ04ETISBLfDWsQ/a3JI3T+I7472SGYq3jJp6Op2k0nkXpmHz9AufJJZw=)
Note that if you type above the function declaration `/**`, then autocomplete will offer two options: 1. `/** */` 1. /** Document This */` The first seems to be built-in...
I think this meant to be a feature actually, but it's too subtle in my opinion - it left me scratching my head for an hour over why my workflow...
Getting some funky behaviour with Python 3.7 `socket` library (with @shamil-mubarakshin's above patch applied). Runner: macOS 12.6.9: ```py >>> socket.gethostname() 'Mac-1702490668849.local' >>> socket.gethostbyname_ex('Mac-1702490668849.local') ('mac-1702490668849.local', [], ['192.168.64.23']) >>> socket.getfqdn() 'Mac-1702490668849.local' >>>...