If you want to stick to Debian, you could try switching to Debian Testing and have newer packages (although the mention "syncthing" is not at the latest stable version there either).
8,335 karma · joined February 6, 2016
If you want to stick to Debian, you could try switching to Debian Testing and have newer packages (although the mention "syncthing" is not at the latest stable version there either).
https://github.com/ziglang/zig/issues/9698#issuecomment-9747...
It doesn't have any hot reloading capability out of the box.
g(_M,W-=1<<f;xx=M[f];M[f]=x)Ui(M_,Ux=M[i];x?(W+=1<<i,M[i]=xx,x):30>i?_M(i,M_(i+1))+(2*n0<<i):OO())f(_r,pt?x:65535&rx?(--rx,x):e(if(!Tx)n(_r(xU))_M(mx,x-n0);x))f(r_,pt?x:65535&++rx?x:OO())
Edit: Looking at it a bit more, I can't tell if the code is obfuscated or if the author really wrote it like this...2024: People are willingly activating a key logger.
That's why it doesn't mention Go's generics which landed in 2022.
I wonder where they are now 7 years later.
To my surprise the technician inspected the laptop and said that the keyboard was damaged (a few keys were wonky, remember the butterfly keyboards?) and that there was an official repair program for that. It turns out that the battery, keyboard, and trackpad is a single repair item. If you want to replace one, you have to replace all three. So instead of a battery replacement, I got a keyboard replacement which just happened to include a new battery and a new trackpad. At the beginning of last year the battery started to expand again and I went to an unofficial repair shop instead. They replaced just the battery for ~$150.
That's not that kind of jump the OP is talking about. dumb-jump/anyjump are plugins which allow you to jump to definition / declaration etc. without having any kind of language server running or having preprocessed the source code. They work by essentially grepping through the source code on the fly with some language specific smartness on top to make it work better.
<space> + /
* It's actually not clear whether this is a feature or a bug. Apple never responded to the bug report (FB12088655).
That's fair but also not what I'm looking for in a task runner, that's why I explicitly said "not a build tool", which to me this falls under (although I realize everybody has a different definition of these terms and where they draw the line if at all).
If you're looking for a task runner, not a build tool, then make is not "far superior" in any sense and there are much better alternatives, the most prominent probably being "just". Even something as basic as accepting parameters to a task (make fetch <arg1> <arg2>) is awkward because make doesn't understand this syntax and interprets the arguments as targets. The only way to make it work is either through named arguments or empty target hacks and in both cases you need to write the validation logic yourself. In just it's simply:
fetch PACKAGE VER:
@echo fetching {{PACKAGE}} at version {{VER}}
$ just fetch foo
error: Recipe `fetch` got 1 argument but takes 2
usage:
just fetch PACKAGE VER
$ just fetch foo 1.2.3
fetching foo at version 1.2.3
https://just.systems/man/en/chapter_1.html- You're not quoting your variables properly to prevent splitting and globbing.
- In case there are no jpg files in the working directory, Bash will put the pattern itself (*.jpg) into the $x variable. You need to explicitly check that the file in the variable actually exists before working on it.
Modern shells do not have these footguns.