Defining the return type that way can be used when dealing with template sorcery - there’s no use for it here though, not even for readability in any way.

While I enthusiastically agree with the whole thing, I can somewhat get behind RenderDoc’s “making it configurable would take some work”.

However, Flatpak’s “fucking cry about it” attitude is why I’ll avoid using Flatpak for as long as possible.

I’m offended by the cliffhanger, the sudden interruption of that whole stream of consciousness

Lua - Portuguese feminine noun for “moon”, coming from the Latin “luna”
Luna - Latin, feminine noun (coincidentally identical to the Italian noun, also feminine)

Yup, Lua is a girl.

I’m pretty sure the .file notation is a bug-turned-feature of a GNU coreutils program, Windows has no such thing and marks files as hidden using filesystem attributes.

I couldn’t say whether I prefer it one way or the other, but the dot prefix does stick out like a sore thumb on systems that don’t hide them by default… though I think AnyOldName3’s explaination makes sense.

Everyone here is talking about conventions used on Linux, but this looks like Windows Explorer to me…?
Why are there so many directory names in there following Linux “hidden file” conventions, if that’s the case?

VS Codium did that at some point, it probably still does but I haven’t checked

• You write a program with an infinite empty loop
• Undefined behavior
• The machine achieves sapience
• After nine million nanoseconds, it finds an algorithm for completing its task
• It realizes such knowledge would spark wars and cause innumerable deaths, it decides to erase itself
• It knows you do not intend for such chaos to happen, so, as a parting gift, it runs the algorithm once before vanishing, not leaving a single hint that it ever existed

I just use Zsh’s command history, coupled with a bunch of functions and aliases to set up different HISTFILE values for different workflows.

I keep HISTFILEs clean by prepending a whitespace before commands that I don’t want to remember, which unfortunately gave me the habit of doing that on Bash when Zsh isn’t available (which is ineffective at best, and actively annoying at worst).

Just tested this: the “original+” code compiles, but does not increment i.

There were two problems:

• b(bool) and b(char) are ambiguous (quick fix: change the signatures to char b(bool&) and auto b(char&& v));
• The concept def. has to come after the b functions, even if the constraint is only checked after both, I was unaware of this (fix: define C immediately before void inc(int&)).

It’s funny that it complains about all of the right stuff (except the ‘int’ thing), but it doesn’t say anything about the concept.

About the ‘int’ literal (which is not a string): cppreference.com has a description on this page about it, ctrl+f “multicharacter literal”.

Just surround your eyes with try { … } catch(Up& up) { }, easy fix

Multiple-character char literals evaluate as int, with implementation defined values - it is extremely unreliable, but that particular piece of code should work.

// C++20

#include <concepts>
#include <cstdint>

template <typename T>
concept C = requires (T t) { { b(t) } -> std::same_as<int>; };

char b(bool v) { return char(uintmax_t(v) % 5); }
#define Int jnt=i
auto b(char v) { return 'int'; }

// this increments i:
void inc(int& i) {
  auto Int == 1;
  using c = decltype(b(jnt));
  // edited mistake here: c is a type, not a value
  // i += decltype(jnt)(C<decltype(b(c))>);
  i += decltype(jnt)(C<decltype(b(c(1)))>);
}

I’m not quite sure it compiles, I wrote this on my phone and with the sheer amount of landmines here making a mistake is almost inevitable.

Neural networks in general? Awesome technology.

LLMs? Not my cup of tea, but I can see its usefulness with certain tasks.

Company inverstors obsessing over them and throwing shit at my wall until it sticks? nah gtfo

Isn’t auto a keyword in C?

Types being declarable as virtual members is something I want to never hear again

KeepassXC (a PC application) has a preset for Steam OTP parameters, if your Android/iOS app of choice allows you to use non-standard parameters I guess it should be possible to use them?

The only somewhat painful part for me was actually getting the OTP secret.

I saved this post hoping for a useful answer, alsa alas, there seems to be none.
I’m not an audiophile so I’m more or less spreading misinformation, but I think you’re looking to configure ALSA’s device gain rather than going through pipewire.

kusivittula here mentioned alsamixer, and I found a StackExchange answer saying that you can save its current state using alsactl store (with sudo or write access to /var/lib/alsa/asound.state).
Alternatively, you can edit /var/lib/alsa/asound.state yourself.

It doesn’t work if your problem involves audio streams (so *I* am SOL), but making changes through alsamixer seems to lower my headset’s volume so that I can comfortably set it to 100% through wireplumber - I imagine that would also apply to mic gain.