arrr traffick boss cannot defeat the alpine email spam replies! so i tried alpine earlier and after i read an email it was all 'inbox closed due to access error' or something like that, and i rebooted it, and it said the same thing on launch, so i went to chatgpt to complain but then alpine started working again :s i wonder how minimal or clear the sourc-- :s so last gpt4 log was sent as some kind of inlined file, it seems like alpine reads the file and writes it into the email. maybe hit the wrong button for attachment. also xapian is still trying to build. maybe i can figure out how to attach files with alpine on my own! it's 1346 on 2024-10-21 . - oh! also, i want to take a sewing class and a cnc class (free at library in this city). registration for the sewing class opens on the 26th or the 30th (depending on which class). registration for the cnc class opens on november 1st. it stays open for a only a couple days before filling up, so everybody who actually gets in signs up right when it opens. at least they said something like that at the cnc space. 1348 cnc ... computer numeric control ... what about human numeric control? can we be controlled with numbers? karl loads gco-- 1348 oops xapian crashed time to debug it was a 'no rule to make file' make issue oh there it is again make[3]: Entering directory '/shared/src/xapian/xapian-applications/omega' make[3]: *** No rule to make target 'common/closefrom.cc', needed by 'common/closefrom.o'. Stop. blrugh confusing to not be in vim i wonder if alpine can launch vim so i guess i can diagnose it from within the omega module folder 1350 i did make clean and make common/closefrom.o and got the same error i guess it makes sense i woul i'll look at the buildfiles and see what that intended logic is 1351 common/closefrom.cc is listed in am__omindex_SOURCE_DIST which means i should be looking at the automake file rather than the makefile it's listed in omindex_SOURCES so it's a sourcefile for omindex but it's not in git? oh the common folder is a link to xapian-core ! it's a symlink to another folder, using a shared git repository symlink so this buildfile is out of sync with core's state ok it's actually a symlink into a subfolder under omega called .common.git which appears to be an independent clone of the entire git repository, copying all the files, unsure :/ 1354 i guess i could just delete it and see if the bulidsystem remakes it it's dated oct 20 22:30, same date as the common symlink, earlier date than the compile script in this subfolder i'll use the bootstrap script to clean and recreate everything i guess kinda wishign i'd learned how to build this rather than asking chatgpt, or had done it's alternative approach where i bootstrapped manually 1355 noting the bootstrap script fails on line 91 maybe i should check that looks like it's just a version check 1356 what was i doing outside this? oh looking up how to attach files 1357 i found https://alpineapp.email/alpine/UW/faq/attachments.html 'how do i attach a file in alpine'. 1358 ok so it kind of sounds like it matters where you add the file to the email. if you add it to the body, you can insert it into the body. you want to move your cursor to the file attachment field to add it as an attachment. i'll try to attach file! i wonder if vim can function as an email client ... although i feel like that wouldn't be as robust as i'm looking for ... maybe i should learn lisp and emacs or whatever vim's scripting language is ... here's my attempt to attach a file! 1400