lyse @lyse.isobeef.org
 (40m ago)

(#f2cdpva) @movq@www.uninformativ.de Thanks! Iā€™ll have a look at SnipMate. Currently, Iā€™m (mis)using the abbreviation mechanism to expand a code snippet inplace, e.g.

autocmd FileType go inoreab <buffer> testfunc func Test(t *testing.T) {<CR>}<ESC>k0wwi

or this monstrosity:

autocmd FileType go inoreab <buffer> tabletest for _, tt := range []struct {<CR>    name string<CR><CR><BS>}{<CR>   {<CR>   name: "",<CR><BS>},<CR><BS>} {<CR>  t.Run(tt.name, func(t *testing.T) {<CR><CR>})<CR><BS>}<ESC>9ki<TAB>

But this of course has the disadvantage that I still have to remove the last space or tab to trigger the expansion by hand again. Itā€™s a bit annoying, but better than typing it out by hand.

#fjhkxza
movq @www.uninformativ.de
 (2h ago)

(#xwn45gq) @lyse@lyse.isobeef.org Well, I used SnipMate years ago (until 2012). IIRC, itā€™s more than just ā€œinsert a bit of text hereā€, it can also jump to the correct next location(s) and stuff like that. Donā€™t remember why I stopped using it.

Then I used nothing for a long time. Just before Christmas, I made my own plugin (ā€¦ of course ā€¦), which does everything I need at the moment (and nothing more).

It can insert simple templates and then jump to the next location:

https://movq.de/v/67cdf7c827/sisni%2Dpython.mp4

And replace a string after insertion:

https://movq.de/v/67cdf7c827/sisni%2Dheader.mp4

(Itā€™s not public (yet?) and it also uses vim9script, so I guess it wouldnā€™t work on your system.)

#f2cdpva
movq @www.uninformativ.de
 (16h ago)

(#j5s5khq) @lyse@lyse.isobeef.org Iā€™m toying with the idea of making a widget/window system on top of Pythonā€™s ncurses. Iā€™ve never really been happy with the existing ones (like urwid, textual, pytermgui, ā€¦). I mean, theyā€™re not horrible, itā€™s mostly the performance thatā€™s bugging me ā€“ I donā€™t want to wait an entire second for a terminal program to start up.

Not sure if Iā€™ll actually see it through, though. Unicode makes this kind of thing extremely hard. šŸ«¤

#fazzzcq
lyse @lyse.isobeef.org
 (19h ago)

(#j5s5khq) @movq@www.uninformativ.de How about ā€œQuongsiā€? I generated the first five letters with pwgen --no-capitalize --no-numerals 5 and since that already showed up in DDG search results, I simply appended the last two, which yielded nothing on DDG and Google).

What kind of project is it? Maybe we can help you find a name or nudge you in the right direction.

#7tsxwnq
lyse @lyse.isobeef.org
 (19h ago)

The tt URLs View now automatically selects the first URL that I probably are going to open. In decreasing order, the URL types are:

  1. markdown media URLs (images, videos, etc.)
  2. markdown or plaintext URLs
  3. subjects
  4. mentions

I might differentiate between mentions of subscribed and unsubscribed feeds in the future. The odds of opening a new feed over an already existing one are higher.

#sd722yq
prologic @twtxt.net
 (20h ago)

Whoo! I fixed one of the hardest bugs in mu (Āµ) I think Iā€™ve had to figure out. Took me several days in fact to figure it out. The basic problem was, println(1, 2) was bring printed as 1 2 in the bytecode VM and 1 nil when natively compiled to machine code on macOS. In the end it turned out the machine code being generated / emitted meant that the list pointers for the rest... of the variadic arguments was being slot into a register that was being clobbered by the mu_retain and mu_release calls and effectively getting freed up on first use by the RC (reference counting) garbage collector šŸ¤¦ā€ā™‚ļø

#xupmaxa
lyse @lyse.isobeef.org
 (23h ago)

(#pact6sq) @prologic@twtxt.net In my opinion, the integrity isnā€™t lost. The same input data always result in the same output hash, no matter when you calculate the hashes. Itā€™s true that a corrupt database contents yields to corrupt hashes, but then you have a whole bigger problem than just receiving different hashes. :-D

#uugltha
lyse @lyse.isobeef.org
 (23h ago)

(#73l4niq) @zvava@twtxt.net By hashing definition, if you edit your message, it simply becomes a new message. Itā€™s just not the same message anymore. At least from a technical point of view. As a human, personally I disagree, but thatā€™s what Iā€™m stuck with. Thereā€™s no reliable way to detect and ā€œcorrectā€ for that.

Storing the hash in your database doesnā€™t prevent you from switching to another hashing implementation later on. As of now, message creation timestamps earlier than some magical point in time use twt hash v1, messages on or after that magical timestamp use twt hash v2. So, a message either has a v1 or a v2 hash, but not both. At least one of them is never meaningful.

Once you ā€œupgradeā€ your database schema, you can check for stored messages from the future which should have been hashed using v2, but were actually v1-hashed and simply fix them.

If there will ever be another addressing scheme, you could reuse the existing hash column if it supersedes the v1/v2 hashes. Otherwise, a new column might be useful, or perhaps no column at all (looking at location-based addressing or how it was called). The old v1/v2 hashes are still needed for all past conversation trees.

In my opinion, always recalculating the hashes is a big waste of time and energy. But if it serves you well, then go for it.

#qatkviq
prologic @twtxt.net
 (3d ago)

Hmmm I need to figure out a way to reduce the no. of lines of code / complexity of the ARM64 native code emitter for mu (Āµ). Itā€™s insane really, itā€™s a whopping ~6k SLOC, the next biggest source file is the compiler at only ~800 SLOC šŸ¤”

#kaiqxgq
movq @www.uninformativ.de
 (3d ago)

(#gslvc3q) @prologic@twtxt.net That might be a challenge, at least in 16-bit Real Mode: The OS follows the model of COM files on DOS, i.e. the size of the binary cannot exceed 64 KiB and heap+stack of the running program will have to fit into that same 64 KiB. šŸ˜… (The memory layout is very rigid, each process gets such a 64 KiB slice.)

And in 64-bit Long Mode, there is no ā€œkernelā€ yet. The thing in the video is literally just a small bare-metal program.

But some day, maybe. šŸ˜ƒ

#q6pehia