Zizek’s take on 300 is so good, here’s an excerpt:

it is the story a small and poor country (Greece) invaded by the army of a much larges state (Persia), at that point much more developed, and with a much more developed military technology - are the Persian elephants, giants and large fire arrows not the ancient version of high-tech arms? When the last surviving group of the Spartans and their king Leonidas are killed by the thousands of arrows, are they not in a way bombed to death by techno-soldiers operating sophisticated weapons from a safe distance, like today’s US soldiers who push the rocket buttons from the warships safely away in the Persian Gulf? Furthermore, Xerxes’s words when he attempts to convince Leonidas to accept the Persian domination, definitely do not sound as the words of a fanatic Muslim fundamentalist: he tries to seduce Leonidas into subjection by promising him peace and sensual pleasures if he rejoins the Persian global empire. All he asks from him is a formal gesture of kneeling down, of recognizing the Persian supremacy - if the Spartans do this, they will be given supreme authority over the entire Greece. Is this not the same as what President Reagan demanded from Nicaraguan Sandinista government? They should just say “Hey uncle!” to the US…

Run all of them for extra brightness.

Being a jerk in Obsidian games is fun. I used to do every small errand to please everyone, mainly for the rewards, but then found out as long as you can figure out the main mechanism, most tasks are optional.

Being more assertive really amps up the role playing aspect. Sadly not every RPG is this open and well-written.

If I can pull myself up, I’ll just have the pie in the sky.

Meh, it’s what you get when you write a language in a different language’s “style”.

*invisible corn on the invisible cob

As other comments point out, they are usually not properly packaged through nix.

If you read the vim/plugins modules, for most plugins, the derivation just downloads the plugin, puts it to nix-store, and makes it available to the editor through environment variables. So it’s similar to the binary distributed software. Two most notable restrictions:

1. Nix is not aware of transient dependencies.
2. The plugin is not aware of the nix-store model.

So for plugins that don’t have external dependencies (or dependencies other than the “common” ones like python or sh that happen to be available), and that don’t interact with the filesystems, this approach would be fine, but the more complex ones would fail.

In your example, mason failed because of 1, home-manager wasn’t aware that the pip module is a transient dependency of this plugin; and treesitter failed because of 2, because it doesn’t know that nix-store is read-only and should be managed by nix.

There are no general solutions, but people may have nixified some plugins on a case-by-case basis. If you don’t want to spend a lot of time (and remember that it might be broken by the next plugin upgrade), as others have suggested, take the traditional plugin management approach. (Personally, I use LunarVim which uses Lazy.nvim and it’s been working fine.)

This, but unironically used as a marketing trick:

There was no v1 of Oracle Database, as co-founder Larry Ellison “knew no one would want to buy version 1”

That’s why the first Oracle database is v2.

https://en.m.wikipedia.org/wiki/Oracle_Database

Now all of China care about your privacy.

Don’t laugh, this is a serial question.

You mean before or after he’s appropriated by Alan Moore as an anarchist symbol?

There’s the GitHub product feedback repo, but as a closed source product (I know, the irony), you can’t point to the code for the problem and nothing other than blind luck can guarantee you a reply, let alone a fix.

On top of that, they are adding ads to the UI, even for paying customers, so there’s that.

Hey, put down that Lemmy.

According to this comment, it’s true.

Not just installing. When updating, sometimes it tries to reset the options and change my default browser to edge.

Try fzf. The default hooks will launch fuzzy finders for

• C-r: history search
• Alt-c: change directory
• C-t: fill in argument for a nested path

All seem pretty good for your use case.

It’s a “terminal multiplexer”, i.e. you can start multiple terminals in a single terminal.

You might ask, why not open a new terminal window or tab? Well, you can only do that in a desktop environment and that’s not always available. Even if you can, you might want the terminals to be side by side in a single screen, which might not be easy to do with window tiling.

The real power of tmux, though, is that it manages the session you created. To quote from the manual:

tmux may be detached from a screen and continue running in the background, then later reattached.

So, one use case would be saving your current terminal setup. Instead of exiting the terminal and navigating to the project and setting up the environment again next time, you can simply detach and re-attach.

When connecting to a remote server, this is especially useful:

Each session is persistent and will survive accidental disconnection (such as ssh(1) connection timeout) or intentional detaching

Suppose you want to execute a long running command on a remote server. If you just put it to foreground, when you exit the ssh session, the job is also killed. If you put it to the background, its output can’t be easily observed.

With tmux, you can simply run it in the foreground like normal and detach. When you reattach later, the job is running and you get all the output easily, as if you have been in that session all along.

Reproducibility is a blessing for both software development and daily use.

NixOS