Bought a new toilet brush from the dollar store. Today I used it for literally the second time and it snapped in half. I don't by any means expect a product from the dollar store to last, but are you kidding me!?
NEW 11-PART PODCAST SERIES "THE INSTASCAMMER" - https://www.spreaker.com/podcast/the-instascammer--7247429
In this episode, Kacey interviews author and journal
Physically speaking, it wouldn't necessarily have to occupy the same space, it depends on how the time travel works, but either way this movie is already nonsensical enough that the only answer in-universe is clearly "🤷 whatever"
I get that "laser rubies" are probably difficult to come by, but if it's so fragile and so critical, you'd think they'd have had a spare. I mean $14M in 1970s dollars is nothing to sneeze at. #monsterdon
https://www.spreaker.com/podcast/the-instascammer--7247429
In this episode, Kacey interviews author Ru Marshall about Ru's new book American Trickster: The Hid
What really matters is that the digits are carved at different depths so the total mass of die material removed is the same. Compensating for the mass differences of the paint, if used.
@isaackuo Even this will not guarantee they have the same effect on the rotational moment of inertia, because it matter how close to the centre of gravity the material is removed...
For just capturing the output of a command, you can use:
r !somecommand
But if you want to filter a range of lines through an external filter with POSIX ed(1), you need some sort of temporary storage (whether a file, the system clipboard, a tmux buffer or whatever). There's no analog to
:10,20! rot13
offered by vi/vim.
Someone (can't find the post/author at the moment) did hack this functionality into ed, but it's a custom fork of POSIX functionality.
Depending on your platform, you might have xclip instead (similar functionality on X), pbcopy/pbpaste on OSX, or some similar tool on Wayland or Windows.
@ed1conf @buffet Sam runs just fine on Linux; I use it there daily (alongside Toronto qed). I think it has been ported to OpenBSD, FreeBSD, and even Windows.
It amuses me that people associate it only with Plan 9; it was originally written for ~9th edition Research Unix, before the Plan 9 project started. (I was there, and an early adopter.)
@Harka Won't work. That won't pass the contents of the buffer as input to !command. The contents of the buffer can either be piped into the command or piped out of it, but not both.
Toronto qed (descended from ed in the late 1970s, not the 1960s editor that inspired ed) has three commands for exchanging text with other programs: >command # send to command's standard input <command # receive from standard output |command # send to stdin, read from stdout, replacing original addressed lines
Of course > and | take an address range and < a single address, like w and r.
I use | quite often either in ed or in sam; latter written by the guy from whom I caught the qed bug.
Implementing | takes some thought to avoid deadlock if pipes fill and block. Qed does it by spawing a temporary process to do the writing, while the main process reads into the buffer.
To be fair, all I know about Ultraman is what I've been able to piece together from what I've seen of the last few minutes of the episodes that play before #monsterdon
It's a great series, the first one came out of a non-superhero science heroes show, so it keeps most of the SSSP with 2 minutes of Dan becoming Ultraman. Later series get wackier.
Perhaps there's the slightly better message of: don't be mean to people who are different... or they'll turn into jellyfish monster things and kill you... I guess?
MY BRAND NEW 11-PART SERIES THE INSTASCAMMER -https://www.spreaker.com/podcast/the-instascammer--7247429
In this episode, host Kacey interviews religious satir
Since the lead developer of #Reticulum and #NomadNet has been too overwhelmed as of late to take on feature requests, I'm releasing my fork as it now contains some useful non-trivial enhancements.
My cat's current favourite toy in the entire world: a single Froot Loop that someone dropped on the floor. I don't have the heart to take it away from him.
One of the features I'd like to add to my #NomadNet fork is the ability for the user to change the default keymap. Unfortunately, with the way the code is organised, this would be a rather involved change. I'm sure I could do it, but then it would be a tremendous PITA to keep my fork in sync with the upstream repo. #reticulum
@circfruit there is already a search in announces!
searching in nomadnet pages would be useful indeed! hopefully it can be the same logic sometimes afterwards to also search into the conversations! that would be _extremely_ useful to me!.but... one step at a time! congrats on your current achievement! ;)
@circfruit No, it's only searching the text of the currenty open page, much like pressing ctrl+f in a typical browser. The ctrl+f keybinding was already taken, so I settled on alt+f instead.
I was able to find the function that turns Micron markup into widgets to be rendered in the browser. This enabled me to pop a shim in there that I can use to edit the markup before passing it to the function. I'm thinking of doing something simple, like putting bold tags around instances of the selected text. A bit of a crude solution perhaps, but it gets the job (at least partially) done.
Considering I'm working in an unfamiliar codebase and an unfamiliar language, I'm happy with my progress so far.
As I think more about it, don't think this shim approach is the right one. Sure, I can mutate the markup before passing it to the rendering function, but if I just go adding tags all willy nilly (e.g.: inside of an existing link tag) things can go very wrong. In order to tell whether or not it's safe to alter a piece of markup, I'd need to first parse the markup to do it.
I'm now thinking it's best instead to add an additional optional search_text argument to the parser and make edits to its code directly instead, a tricker approach, but less likely to blow up in my face.
Okay, the parser is a giant mass of code, but I've got my edits mostly working now. I expect this feature will be done within a day or so now. #reticulum #NomadNet
Couldn't sleep with this thing so close to finished, so I just kept hammering away at it until I got it working. I'm going to play around with it a little in the morning to be sure I've not missed anything important, but it looks like my #NomadNet client now has a working "find in page" feature, even if it's slightly janky.
Next on the docket is fixing a bug that causes my client to crash when I try to edit a backbone interface config. I'm 99% certain I know what the problem is, and it shouldn't be difficult to fix. I doubt if I'll have to change more than one line.
...except if the exception gets thrown inside the rendering engine. Then it gets caught and the error message is displayed in the browser... but without a stack trace. Good thing I'm (hopefully) done with my edits to that part of the code. #reticulum #NomadNet
This is the thing I never understand about these movies: if everyone just suddenly vanished, shouldn't there be multi-car pile-ups and planes falling from the sky? #monsterdon
I've just started getting three month refills, hurrah!
Even with that, I would recommend checking the FDA Drug Shortage[1] list about a month before each refill. I've seen various ADHD meds listed there, though not yet the ones prescribed to me.
https://www.spreaker.com/podcast/the-instascammer--7247429
In today's episode, Kacey interviews retired journalist and University of Texas at Austin professor
Now that I've successfully made some small tweaks to my fork of #NomadNet. I'm working on adding a conspicuously absent feature to search the text of the open page in the browser for a user-supplied string.
I've been informed that this has been an oft-requested feature that nobody has currently found the time to work on. Considering I've never really worked on a large #Python project before, I'm happy with the progress I'm making so far.
I've really been enjoying nomadnet, but I've found some rough edges here and there. I know that Mark isn't in a position to be taking bug reports/feature reque...
@PocketVJ aka magdesign I kept the originals intact as well. I didn't want to break anyone's UX. Also, my understanding is that if a keybinding is handled by the OS (or terminal emulator) it won't be passed on to the application.
@Michel 🪱 Fortunately things are named well enough that I can mostly work out what everything does. He has made some... interesting choices though. I want to do a bit of a refactor and have offered to send my changes upstream for review. I know he's not doing feature requests these days, but nothing stops me from implementing changes and fixes, even if only in a private fork.
Jonathan Lamothe
in reply to Jonathan Lamothe • •Jonathan Lamothe
in reply to Jonathan Lamothe • •Jonathan Lamothe
in reply to Jonathan Lamothe • •"You'd do it again if you got the chance, wouldn't you?"
Can you blame her? I want to poison this guy.
Jonathan Lamothe
in reply to Jonathan Lamothe • •"Ridiculous! The roof probably leaks."
Blood!?
#monsterdon
Jonathan Lamothe
in reply to Jonathan Lamothe • •Jonathan Lamothe
in reply to Jonathan Lamothe • •"Well how do you explain what happened to Lance?"
Yes, no one has ever hit their head through non-supernatural means.
#monsterdon
Jonathan Lamothe
in reply to Jonathan Lamothe • •Jonathan Lamothe
in reply to Jonathan Lamothe • •"You don't look like the type who goes around bumping his head."
What exactly does that type look like?
#monsterdon
The Witch of Crow Briar
in reply to Jonathan Lamothe • • •Jonathan Lamothe likes this.
Neia masks
in reply to Jonathan Lamothe • • •probably like this
Jonathan Lamothe likes this.
Jonathan Lamothe
in reply to Jonathan Lamothe • •Jonathan Lamothe
in reply to Jonathan Lamothe • •Jonathan Lamothe
in reply to Jonathan Lamothe • •Jonathan Lamothe
in reply to Jonathan Lamothe • •"I tell you, the guns won't make any difference."
*proceeds to sit staring at the door pointing his gun at it*
Jonathan Lamothe
in reply to Jonathan Lamothe • •David Zaslavsky reshared this.
Jonathan Lamothe
in reply to Jonathan Lamothe • •Jonathan Lamothe
in reply to Jonathan Lamothe • •