Today's question: how do you keep a code-reorganizing commit as clean of behavior changes as possible when part of the ultimate reason for the reorganization is to stop doing X in case A, but the way X is currently done is too tangled with the existing code path which is better repurposed for Y?
Today's answer: add an instantly-deprecated flag parameter to the function that should stop doing X. Then the actual behavior-change commit can prune it again.
Good idea? Crazy?
I'm not amazingly happy that their Mercurial support went away.
I _hate_ their stylesheets for Markdown/reStructuredText. The heading spacing is ugly enough to give me a mild headache.
At least installing Roboto Mono stopped their code elements from using the squinty x-height of what I think was Courier.
Today: putting a character-cell-art banner in the header of a hand-written placeholder page.
Also today: <pre role="image" aria-label="[appropriate banner text]">
Hope I'm doing that right. The #Accessibility developer tab in Firefox looks non-horrible at least.
Today is a day for being reminded that https://archiveofourown.org/works/3673335 exists. A nice short Stargate fan story about software testing, and almost an ad for Hypothesis.
I am being irritated at gettext's use of the original-language text as the primary key. (I am aware of pgettext.)
What it makes me want to do is write the original text in Lojban out of spite.
But this is a bad idea, for I do not know enough Lojban for that and neither do any of the other potential maintainers.
Initial #release of xbell-ringer 0.1.1! I needed a ringer for the X bell after I switched to #PipeWire, and the existing version wasn't quite doing it for me. Feel free to give feedback here and/or report issues on Bitbucket.
Dreamwidth post: https://dasyatid1.dreamwidth.org/1435.html
Repository link: https://bitbucket.org/DasyatidPrime/xbell-ringer/src
Release download: https://bitbucket.org/DasyatidPrime/xbell-ringer/get/v0.1.1.tar.gz
Comment of the day (that I am writing): “Argh! SemVer 2.0.0 has a notion of prerelease but not postrelease versioning, so if we're working _forward_ from a tag, we have to increment the patch level. It's slightly easier to do the increment in sed than to take apart the version string with shell operators or awk, in this context.”
Have I gone mad?
Can anyone attest to the existence of “supraunity” as a word meaning “greater than 1”, especially with regard to multipliers or proportions (“greater than 1:1”) and double-especially with regard to amplification factors? Am I misremembering that one? I felt sure it was a known term, but I'm wondering if maybe I made it up or confused it with something else, since I can't seem to find easy references to it on the 'net.
It has its own XSettings protocol implementation because libxsettings-client wants Xlib but this program uses xcb. 🙃
… and it recreates the libcanberra context every time.
Wait a minute, given libcanberra's available backends (which don't include PipeWire directly), does this imply that a PipeWire module is opening an entire _new_ connection to itself _via_ its Pulse emulation every time the bell is rung?
I have encountered a form of dependency hell involving needing a dependency on a recent enough dependency determiner to read the more recent format and location of dependency information. I wrote at least two block comments cross-referencing multiple files with each other so that someone who opened up one would understand which others related to this issue.
Perversely, I have found out that this is, at least sometimes, what makes me feel alive.
I'm not sure what that says about me.
I am so tempted to pronounce “#SQLAlchemy” as [skl̩ˈælkʰəˌmi]. (With some ambiguity over whether that first group before the [kʰ] really has a syllabic [l] followed by [æ] or is all one syllable.)
A well-intentioned hacker-type creature—by the old “drilling into the sky” definition, that is, not the later “criminal” definition. Austin, TX, USA.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!