Since my last quack on URL Scroll-To-Text fragments, availability has increased to 92.76% and is now supported by FF on Android. Latest builds of Firefox also allow you to create these fragmented links directly through the UI by highlighting some text then selecting "Copy Link to Highlight" in the context menu. It is still currently gated behind the
dom.text_fragments.create_text_fragment.enabledoption inabout:config, but enabling that is simple and the feature works just fine for me!After my latest system update, I noticed that Firefox reverted back to light mode, despite my GTK Theme being a dark theme (Arc-Dark).
A bit of searching later, I found this comment on a Cinnamon DE github issue, which solved the issue for me:
dconf write /org/gnome/desktop/interface/color-scheme "'prefer-dark'"Someone once asked (mildly edited):
After you create a pipe, say
pipe2((int arr arg), O_CLOEXEC)in the parent process, when the child process calls exec, why doesn't the close calls that should originate from theO_CLOEXECflag show up in the child process's strace – or any of the strace outputs for that matter? I assumed thatO_CLOEXECdoes something internally, but I'm not sure.The short answer is that the closing of
O_CLOEXECmarked file descriptors is done by the kernel, and not by a syscall from a userspace process. But since I love spelunking in source code, I decided to look for a reverse stack trace or how such aO_CLOEXECfile descriptor is closed onexec, starting from theexecvesystem call:execvedo_execvedo_execveat_commonbprm_execveexec_binprmsearch_binary_handler- funky dynamic searching for a binary format handler, assuming ELF binaries here so
load_elf_binarybegin_new_execdo_close_on_exec
which walks a bitset and calls `filp_close`. Yay!
I added the same "hover info" support for CSS just like I have for Rust!
pre { : absolute; : bold; : stretch; }You can see it in action in the code block above. The information shown is taken from vscode-custom-data, which is used by VSCode's CSS LSP server. One day, I'll add the selector specificity + HTML element view info as well!
The curse of Wayland:
I don't need fractional scaling on my main monitor.
I need to set fractional scaling to anything that isn't 1.0 because due to potentially a niri bug that causes problems with kitty (this might be the issue
Discord doesn't work with Wayland because WHO KNOWS.
Discord in xwayland-satellite is blurry because of fractional scaling due to this issue that is hopefully fixed soon.
Finally got around to making my post headings clickable! It was a bit weird to implement because the HTML structure looks like this:
<section id="Variables"> <h2> <a href="#Variables"></a> </h2> ... </section>instead of the more conventional "heading contains the `id`" method. If you're confused about the `h2`, check out There Is No Document Outline Algorithm by Adrian Roselli.
Rabbit hole of the day:
I wanted to join the by-invite lobsters community, so I joined their IRC channel on Libera Chat.
I have been thinking about trying out iced for a medium-sized GUI project, so I decided to use halloy as the client.
While trying it out, I got annoyed with a bug where changing focus to the halloy window with a keypress (through my tiling window manager) inserts the key pressed in the chat buffer.
Ended up on squidowl/halloy#284, which led me to iced-rs/iced#2621.
Since I was already in a procrastination session, I did some research and filed a PR to fix the problem in iced.
Now I wait...
TIL about URL Scroll-To-Text fragments. Availability seems limited so far (89% with FF for Android not supporting it being my primary limiting factor) so I'll be keeping an eye on it.
While working on my latest post, I realized that the outlines for focusable elements in code blocks were partially hidden by the next line. A
position: relativeandz-index: 1later, everything is good to go!Implicit string literal concatenation considered harmful 😠
Once again I am bitten by Python unexpectedly breaking code because I forgot to add a comma between two string literals:
["hello", "a" "b"].
Quacks
The position CSS property sets how an element is positioned in a document. The top, right, bottom, and left properties determine the final location of positioned elements.
(Edge 12, Firefox 1, Safari 1, Chrome 1, IE 4, Opera 4)
Syntax: static | relative | absolute | sticky | fixed
Specifies weight of glyphs in the font, their degree of blackness or stroke thickness.
(Edge 12, Firefox 1, Safari 1, Chrome 2, IE 3, Opera 3.5)
Syntax: <font-weight-absolute>{1,2}
Defines the default justify-self for all items of the box, giving them the default way of justifying each box along the appropriate axis
(Edge 12, Firefox 20, Safari 9, Chrome 52, IE 11, Opera 12.1)
Syntax: normal | stretch | <baseline-position> | <overflow-position>? [ <self-position> | left | right ] | legacy | legacy && [ left | right | center ]