Nobody drinks Lipton in the UK

I recall that there is a USB GPIO dongle which gives you a bunch of pins to play with. You would have to hunt around to find it though.

It’s a fine distribution. I have it on my desktop and at least one laptop. But yes, a weird way to decide to distro hop 🤣

☠️

Top tip, if tired, replace the rm -f part of the command with something innocuous for a first run. Actually, is better to do this mistake once so that the two important lessons are learned… Backup (obviously, in your case it was backups, but the point still stands) and double check your command if it has potential for destruction 👍

csh FTW eh 🤣

You can have both python 2 and 3 on the system. It just depends upon which is the default as to how much you break it 👍 The symlink to /usr/bin/python is the important bit for most software. For deb-based at least, update-alternative is your friend.

Really? Do you have a source for that?

Not sure as I’m on mobile. But your terminal should have a font song you can change.

To be honest, I’ve never investigated seeing a font for a specific app inside a terminal, so that would be new ground.

I think lvim likes patched nerdfonts though? The docs may assist

In windows terminal or will, you go to top left, edit, defaults. You should install patched nerdfonts for best results. Search for zsh fonts wsl (or Lunarvim fonts wsl) for further instructions. Am on phone so can’t help further.

Re macros. If you are editing something and you need to repeat a pattern, eg. Remove every third line or whatever, you just get to your start point and press q<a character> in command mode to start recording into macro buffer <character>. Q to quit then you can reuse it and use it as a command with @<character> Re fonts. It’s your terminal which controls your font in windows. In wsl, eg. The font is controlled by the external windows terminal and not by wsl. It’s dependent upon your environment I’m afraid.

To use any editor with vim bindings takes time and effort. The learning curve is generally quite steep, so if you decide to go down that path, then to switch to a different flavour of vim isn’t too much effort, assuming you have already put the effort in to learn vi/vim/nvim. If you have yet to do that, I strongly suggest that you go dive into using vim for a month or three before you start worrying about which plugin set you prefer. The magic powers are really in the modes, macros and keybindings. For example, VSCode has a decent enough set of keybindings that it’s usable, but I still prefer console editing and on the fly macro creation.

Regarding Lunarvim, for me, it was the first vim ide I found which hit all my requirements, and wasn’t intellij, vs code, etc. But I had been using vanilla vim for nearly 30 years by then. The default plugins which come with lvim are pretty good, so I only add or modify with care. I really can’t afford to lose my ide in a work environment.

Speaking of which, lvim works in most terminal environments, but may require font tweaking on windows, wsl, etc. But then it’s always harder doing stuff in those environments…

I can’t speak for emacs, since I last tried it 20 years ago (although I didn’t like the complex key bindings at the time). I hear that once you commit to one of the two, it’s difficult to transition to the other, but ymmv 😁

I had become heavily into vim, but needed something easy to set up as I no longer have time for tinkering, and also wanted to replace so called ide’s with something in my terminals. Paired with byobu for terminal multiplexing, I rarely need to leave my terminal. As an aside, I am also toying with ollama in a byobu split as my sme/ man page wrangler for when I’m too busy to waste time looking for the exact syntax it library to do what I want. Working well so far

I use lunarvim almost exclusively. It’s fast, has great defaults and with the right lsp Plugins installed, it supports most languages. It’s based on the more recent versions of neovim, so e.g. standard debian version would require an upgrade.

Try Lunarvim, it’s neovim with a bunch of great Plugins and configuration settings out of the box.

No they were not setting standards. They were in fact breaking them. Their own standards were not disclosed, forcing competitors to actually have to reverse engineer them in order to try to have a chance at compatibility. The whole reason for the lack of uniformity was Microsoft fucking with the standards!

Secondly, the competitors did not have a significant market share. Thirdly, it’s funny that you mention in the context of a developer, given that they all complain mightily, even to this day, about having to support the festering pile of IE versions still around. Still, this won’t stop you telling, so you go do your thing elsewhere please.

No. I was just looking for an example of when Microsoft created standards for IE that other browsers could adopt, given that they were tied into IIS and undocumented in order to give them an uncompetitive advantage. Let’s also think about how they deliberately downgraded performance, or broke functionality on non Microsoft browsers, again for anti competitive behaviour.

They were called browser wars for a reason, and Microsoft is very well documented indeed regarding their fuckerry. But you go ahead trolling.

Microsoft standards?

Very good to know, thanks!

Thanks for sharing. I’ll have a read when I finally get back to my pc