![](https://lemmy.one/pictrs/image/b7851e03-2b33-4cfa-b610-cb5d4f51d9ce.jpeg)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
To be fair, it’s also missing open_dialog_file
, dialog_open_file
and most crucially file_open_dialog
To be fair, it’s also missing open_dialog_file
, dialog_open_file
and most crucially file_open_dialog
mod+shift+q
so you wouldn’t close hours of work by accident (e.g. when typing other mod+_
keybinds)
Half of the linux ecosystem is personal projects.
Linux itself started as
just a hobby, won’t be big and professional like gnu
It’s not useless as you can learn from it.
Almost. It doesn’t try to solve all the problems, though. I’d say it’s a passion project like Haiku and TempleOS.
From interview: it started as a research project. The author wanted a distribution that uses the least system resources with maximum performance.
He started with archlinux, moved on to gentoo and to go even deeper - found the infamous “linux from scratch” and started to shape his own distro.
Ok, because of this post - I decided to bite the bullet and try wayland again. And it was much better experience this time:
I’ve installed sway “pattern” on OpenSuse-Tumbleweed and:
waybar absolutely supports clicking tray icons.
I confused it with swaybar, that’s installed with sway by default and should be an i3bar-compatible. Waybar doesn’t seem to support i3bar protocol, but anyway, after I configured it - it’s like 95% there from what I want.
I could switch tomorrow if I could do my current setup:
Last time I tried Wayland in December, I had issues with waybar not supporting clicking tray applet icons. Also I’ve ported my dropdown terminals script to support sway - and it worked half the time, like, literally every second key press was ignored.
On one hand I have X session that currently has no downsides for me, on other - wayland that has no upsides. Tell me, why would I switch?
If it was near the shore - they might’ve stole the section of wire. Copper is really expensive.
it seems to be a variation of “cargospace” meme.
Yes. It’s also a Rube Goldberg machine, where photons travel millions of kilometers from sun to bump into some electrons, electrons then bump into some metal and fast metal pushes air in your room to make it move a little bit faster.
only a small number will sign up for a specific forum
Most people don’t have to sign-up, 90% of cases should resolve on just searching the problem. Good chances it was already asked and answered.
Most of the time, forums with few users aren’t dead, they’re just really slow, whenever you post a question - expect at least 12-hour delay. I’ve never seen a message on Discord answered 12 hours later - you either get somewhat instant response or it’s ghosted forever.
Also good luck asking questions if there’s heated/rapid discussion in the room, or you have a little time and other responsibilities other than checking discord every couple minutes.
as yet
It’s Nim, but I have no idea why you can’t do this in Rust:
var seeds = lines[0].split(": ")[1].splitWhitespace().mapIt(it.parseInt)
Full solution: https://codeberg.org/Archargelod/aoc23-nim/src/branch/master/day_05/solution.nim
I would accept discord/irc over mailing list. But nothing beats a proper forum website.
And no, subreddit is not a proper forum.
In theory this issue can be solved with LD_PRELOAD trick. E.g. redirect all/most/some fopen
calls to “$HOME” to some other directory. But before I try to tackle it myself: is there already a similar solution like that?
Yes the compiler/interpreter can figure it out on the fly, that’s what we mean by untyped languages.
Are there untyped languages? You probably meant ‘dynamically typed languages’.
But even statically typed languages can figure out most types for you from the context - it’s called ‘type inference’.
I don’t understand.
How is it hard to remember: “eXtract File” = “tar xf …”?
If tar is gZipped - it’s “tar xzf …”.
I don’t think I’ve ever seen tarball that wouldn’t work with one of these two commands.
For one - the error handling. Every codebase is filled with messy, hard to type:
if err != nil {
...
}
And it doesn’t even give you a stack trace to debug the problem when an error happens, apparently.
Second reason - it lacks many features that are generally available in most other languages. Generics is the big one, but thankfully they added them in last half a year or so. In general Golang’s design principle is to implement only the required minimum.
And probably most important - Go is owned by Google, aka the “all seeing eye of Sauron”. There was recently a big controversy with them proposing adding an on-by-default telemetry to the compiler. And with the recent trend of enshittification, I wouldn’t trust google or any other mega-corporation.
I have all apps I use daily in the appimage format. Yesterday I decided to try btrfs for my root partition and did my annual Linux reinstall. All my apps were already there and ready for work from the start.
I also have a usb flashdrive always on me with the same appimages. Just in case I’d wipe a hard drive by accident and wouldn’t have an internet connection or something like that (in case of emergencies). You can’t do this with flatpaks or snaps.
Zip is fine (I prefer 7z), until you want to preserve attributes like ownership and read/write/execute rights.
Some zip programs support saving unix attributes, other - do not. So when you download a zip file from the internet - it’s always a gamble.
Tar + gzip/bz2/xz is more Linux-friendly in that regard.
Also, zip compresses each file separately and then collects all of them in one archive.
Tar collects all the files first, then you compress the tarball into an archive, which is more efficient and produces smaller size.