balsoft

I don't know if it's of any solace, Linux used to be a much more... ahem... "involved" experience a decade or two ago. This was more-or-less the norm:

I can't really say what the newcomer experience is nowadays, but I can say for sure that even in the worst-case (as it was in the times when I started using it), after a couple months of furious issue-fixing and trying new things, you will eventually settle on a setup that works for you. Some people actually get addicted to all the problem-solving and start looking for more issues to fix; some start distrohopping to find a "more perfect setup", getting their fix of issue-fixing in the process. If you're not one of them, congrats, at that point you can (mostly) just continue using it, until you need to update your hardware, then process may or may not be repeated depending on your luck. If you really hate fixing issues twice, you can look in the direction of declarative distros like NixOS or Guix, but I will warn you that the two-three months of furious hacking is still very much a thing here, but after that you're set more or less for life.

There are only a couple obscure routing engines that can route through areas, so you will have to use interconnected linear ways probably.

What square are you mapping exactly?

If the entire square is open to cars, you should do something like the following:

On the square area itself set

place=square
area:highway=yes

Also connect all the other roads entering/exiting the square to each other, so that they are routable; make sure they all have appropriate highway=* tags set, so that routers don't get confused.

Make sure that all pedestrian paths (sidewalks) are also connected together, using highway=crossing when appropriate.

NIX IS FOR REPRODUCIBLE BUILDS. That’s fucking it, seriously. It’s literally on their website.

This post is specifically about NixOS and friends, though.

IT’S A HORRIFIC EXPERIENCE FOR NEW USERS TRYING TO RUN A DESKTOP. Steer clear.

There are thousands of users who run NixOS on their desktop, and thousands more users of home-manager (or nix-darwin) on macOS. If you are ready to put in the time and learn how it works, it's wonderful - your entire distribution, the thing through which you interact with computers, becomes just another project in your ~/projects, rather than something you have to manually configure. You can't forget "how to configure $X", because it is all recorded in one place and done automatically when you get a new machine or update or whatever. It's GNU Stow on steroids, for your entire system.

There are a lot of downsides for sure as well (mostly the learning curve, and having to fix the buggy bullshit in some software which only runs well in FHS), but if you are a software developer (or adjacent) and like Linux, NixOS is still awesome.

Hmm, I think for me it just picks it up from the project root "magically". I'm starting my editor from the project root too, maybe that matters (i.e. clangd looks for this file in $PWD)?

Actually, looking at the docs, it should just search for it upwards from the source file you're editing, so it can find it in the project root or in the subdirectory where your code lives. If you have it in some other locaiton, you can set this option in the .clangd file in your project root.

This is clearly not "a russian wondering what's wrong", this is "a russian living in russia who doesn't want to die in prison". This would be a fair criticism if there wasn't a law criminalizing pacifism together with many laws making it easy to deanonymize internet users.

Silence does not fix things.

Neither does grandstanding on Lemmy. It especially wouldn't fix anything if a person in Russia trying to build international relations would go to prison for it.

This is about as useful as suggesting to an average USian/brit/german that they violently overthrow their oppressive governments and install socialism. The punishment for trying (at least in UK/germany) is about the same as it would be for a russian wearing an anti-war T-shirt, the benefits for the humanity would be greater than they would be for overthrowing Putin's dictatorship, and yet I don't see people yapping about it any time someone from those countries posts an open-source project.

There's almost no civil society of any kind left in Russia, so it's impossible to say if a nation overall supports or opposes the warfare. People with an active pro-war or anti-war stance are minorities, somewhere in the 10-20% range, and neither are allowed to speak up (interestingly, quite a lot of pro-war social media influencers are in prison right now for daring to speak up against corruption in the army or similar). The vast majority of people are just going about their days. Does that technically help with the war? Yes, I guess, it drives the economy, people pay taxes etc, but then the same can be said about an average american, brit or german right now - I don't see them blowing up munitions factories (that directly supply the ongoing genocide).

There is a complex sociopolitical history as to why it’s likely Russians aren’t as vocal about these sorts of things

There's also a very simple reason: Russian Criminal Code article 280.3, which criminalizes pacifism with up to 7 years' imprisonment.

I don't think there's a law in the US that criminalizes pacifism [yet] (with actual prison time as punishment)

It's easy to blame russians for not resisting the war when you don't have the prospect of spending 7 years in a russian prison

The basis of trust has been breached by whole nation, so it has to be earned by every single member of that nation.

1. WTF is this collective punishment nonsense? Replace "nationality" with "race" (keeping in mind that a person typically doesn't choose either and it's decided by who their parents were) and you should be able to see the issue here
2. I hope you rather quickly uninstall almost all popular FOSS software from your devices, because almost all of it contains sizeable contributions from russian citizens and I don't think you've individually verified their intentions

For context I've been using aerc as my email client for a while now, and was looking for something similar for calendars/tasks myself

I've tried:

• calcurse: fine but clunky, also a bit difficult to set up. The most mature option and probably the best one available, but I just couldn't get used to the interface
• calcure: similarly clunky interface, glitchy/blinking rendering to the point of being headache-inducing, lacking features (couldn't figure out how to look at all event attributes?)
• khal: limited in features (compared to calcurse) and slow when there are a lot of events (even when it's only 2-3 per day), also there are some rendering bugs sometimes. Probably the most intuitive and clean interface of all, and good scripting opportunities.
• gcalcli: only Google Calendar (I also need support for arbitrary CalDAV), didn't investigate further
• plann: no TUI as such, just CLI

A couple weeks ago I've decided to start writing my own. It's still very much a hacky WIP but I'll update in this thread if I ever decide to publish it. In the meantime, I hope one of the above works for you!

Because C++ doesn't have a single well-defined build system, clangd doesn't know how exactly to compile the files you are asking it to - in this case, it doesn't know what headers to include. On some other distros it might "just work" because all headers are lumped together somewhere in /usr/include or something, and something somewhere tells clangd to just look in there. This isn't the case on NixOS (in fact the headers are not installed at all with your system), and so you have to tell clangd where to look for them.

Typically, your build system will have that information somehow. The process can vary depending on the build system you are using - some (like CMake or meson) can do it natively, for others you have to resort to a very useful hack called bear. Judging by your shell.nix, I would guess it's make, which doesn't have native compile_commands.json support, so what you have to do is:

1. Add bear to your nativeBuildInputs
2. Enter the shell again so that you have it in $PATH
3. Run make clean (or otherwise ensure there are no build artifacts already present - maybe git clean -fx but be careful with that)
4. Run bear -- make from the project root.

make should then build your entire project, compiling every file in the process. bear will inspect the system calls that make is executing and determine which commands (and hence which command arguments) it used to compile each file, and create a file called compile_commands.json recording this information. clangd should then automatically find that file and use it to figure out which headers (and other arguments) it needs to compile each file.

This is the setup I personally use to hack on Nix itself BTW, and it works great. Although I'm using helix and not neovim, but that shouldn't matter.