@rockorager I'm using IMAP backend.

four #hardware #loopback's is pretty amazing. afaik #rme uses #fpga in #babyface to manage the total 24 channels. #audio

@rockorager I did read through https://man.archlinux.org/man/aerc-templates.7.en but MessageId is not documented over there. Still a bit confused about template language but it is definitely worth of learning.

I tried to look also whether the template language gives me a way to remove duplicate emails (in the manner of ~= filter in mutt) but could not come up with anything so far.

Rest in peace Bram Moolenaar. I've been a #vim user since 1998. https://groups.google.com/g/vim_announce/c/tWahca9zkt4?pli=1

@rockorager thanks a lot!

Reading a diff patching another diff can be nasty, and it is not unheard use case to patch a #dependency during the #build.

it would be a nice to have a #git #diff #option that would #pretty #format patched #patch files.

apparently folder’s can be cycled in #aerc with the cursor keys when the capslock is turned on. holding shift was getting painful to say the least. #email #shortcut

@Andi how do you make them work with aerc so that i can quickly remove duplicates in any imap folder? i'm not seeing the connection but i've only recently switch from #mutt so...

I wonder how to pick Message-ID from #email in #aerc, in order to pipe it to #b4. #rfc2822

i use #evolution to delete #email duplicates because i have no idea how to do it in #aerc.

Hi! 👋 Here's our #introduction.

We're BBC Research & Development; we explore and test new technology to discover how the BBC can best make use of it in the future.

For 100 years our engineers have been at the forefront of developments in broadcasting.

We're now researching how everyone could get TV & radio via the internet – along with all the flexibility and creativity that brings.

5G, AI, next-gen audio, UHD, personal data… we are investigating all these – and more!
https://www.youtube.com/watch?v=rzztGFXYR1Y

reminder to myself. in order to plumb #kernel #config file for a particular #buildroot build:

make linux-patch
# edit output/build/<linux directory>/.config
make # continue with the build

#linux

@polarity yeah it is perfect way to get insights for random topics, and much better quality than any other social media I'm aware of.

ordered a new sound card, can't wait: https://www.rme-audio.de/babyface-pro-fs.html

#rme #audio #babyface #musicproduction

@beef wow thanks i will check it out!

code generation with AI. i do not get it and it has enormous legal risks for commercial use. i’d wait at least to wait for precedent legal cases before seriously using it.

also even when manually written code paths, which in some level address the functionality in a an software package, it will take about 5-10% of the overall project time. 90-95% of the time goes into QA and finding out ways of fitting the implementation to the constraints defined by all sorts of non-functional issues.

that’s why case tools never succeeded, and that’s why i’m skeptical of the whole idea of AI code generation. there’s always someone offering a magic wand to write the code for you but it never works - at least if you aim for the highest possible quality, i.e. aim for offering more value for customers than your competitors.

even the most modern thing in the system programming keeps the old bad pattern of enforcing a strong binding between the build system and test harness, which is largely incompatible with modern world applications, such as #iot.

it would be cool if #rust #cargo had a method of generating self-contained binary that you could copy to a device and it’d do the same thing as running cargo test on the host. cargo could select the code paths for the binary based on parameters that you would otherwise put after, such as --features

imho in any software project binding integration tests with the build system is not a great design decision but it is still commodity among open source projects.