Programmer, writer, philosopher, and neophyte artist. My legal name is Ryan Westlund (putting this here for prospective employers to know the account is me)
From Evin Yulo to ~rjarry/aerc-devel
aerc crashed and I got this log telling me to report it. Steps I've found to reproduce it (worked 3 times in a row): * Load the inbox * Put computer to sleep, causing it to shut off internet * Wake the computer and try to delete a message from the inbox before internet reconnects * Wait a few seconds for crash to happen My environment: Artix Linux. First discovered in the packaged version of aerc 0.17.0-1 from Arch Linux repositories, but I've found it also occurs on current master branch (commit d582ac682cdf859a4c350f4a96806c75606c5b57). Here's the log: aerc has encountered a critical error and has terminated. Please help us fix this by sending this log and the steps to reproduce the crash to: ~rjarry/aerc-devel@lists.sr.ht
From Yujiri to ~andreafeletto/public-inbox
multiple arguments to riverctl spawn must be quoted. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index bdbdbe6..a830654 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ zig build --prefix ~/.local install Add the following toward the end of `$XDG_CONFIG_HOME/river/init`: ``` riverctl spawn levee pulse backlight battery [message trimmed]
From Yujiri to ~andreafeletto/public-inbox
Apologies if this gets sent incorrectly, this is my first time using sourcehut by email. I found that levee fails to start without these quotes, river version 0.2.0-dev.117+c0e6482.
From Yujiri to ~sircmpwn/public-inbox
On Fri, Nov 21, 2021 at 10:55 AM Lennart Regebro <regebro@gmail.com> wrote: > On Fri, Nov 19, 2021 at 11:50 AM Yujiri <yujiri@disroot.org> wrote: >> An >> end-user who doesn't program should never have to use pip or npm. > That is absolutely true, in theory. In practice, however, they have no choice. > There is no possible way for me to make packages for all Linux distros. > In fact, every time I've tried to look into how to make them, I've failed. > Making a RPM or a DEB is an obtuse and arcane form of magic. And > how would I go about making one for the infinite amount of Linux distros > that exist? I haven't got a clue. > And that's not even mentioning Windows.