xmonad VS yode-nvim

The official guide and the archwiki do say that it's okay to just install it via pacman, but I've also found some issues on the official repo that strongly suggest against installing via pacman and to use stack instead, as sometimes pacman breaks dependencies.

Especially Haskell tools often live in proximity to nix as well, e.g., pandoc or xmonad.

Hey everyone 👋 ! I'm currently working on a rust library for building and configuring your own shell! It's inspired by projects like xmonad and penrose where the configuration of the program is done in code. This means that for example, instead of using Bash's arcane syntax for configuring the prompt, it can be configured instead using a rust builder pattern! The project itself is still at a very young stage, so there are plenty of bugs and unimplemented features. However, some things that are (partially) implemented are:

Daily, because xmonad

If the problem is as described in the reply linked below, then this isn't a fundamental issue, but just a matter of how sendMessage is written. In fact, the fix already exists in xmonad/432:2fff2a0.

There are a few other things I could mention, but there are more like side issues, and not relevant to my actual LaTeX setup. First and foremost—and thus perhaps noteworthy after all—is bibliography management with arxiv-citation (see here for more words). This is integrated very well with the XMonad window manager, which makes it even more of a joy to use.

The tl;dr is that this is a bug in steam, see https://github.com/xmonad/xmonad/issues/423

And here is my Xmonad configuration

Perhaps https://github.com/hoschi/yode-nvim

The plugin is https://github.com/hoschi/yode-nvim . I've submitted an issue related to this. I just wanted a workaround for the meantime.

It gets brought up a lot in vim discussions. It's missing a few major things for me;

1. Tabs (like in vim). I've found only vim and emacs have tabs in a way that makes sense to me. Kakoune also has a cool model, where I can use my window manager (or tmux) to recreate tabs.

2. Code folding, I like to fold everything as soon as I open a file to get an "overview" and then slowly unfold as look into the details. Wasn't in Helix last time I checked.

3. Narrowing. Emacs has it built in, (neo)vim requires a plugin [0]. Similar to code folding, when I'm working on a large function, I want to pretend it's the entirety of my buffer.

[0] https://github.com/hoschi/yode-nvim

Hi, great work releasing this! Trying to explain vim concisely is always an interesting challenge and I had a great time reading your attempt in this book. I always find it really interesting on how people try to group certain vim functions in a way that makes sense to people that don't use vim.

Whenever I try to explain vim to other people, I always start super abstract, i.e 'vim grammar is all (count)? verb then object. Learn actions and then the movements to apply the action where you want'. I think you cover that idea pretty well in your 'Vim philosophy and features' section whilst not making it overly abstract and keeping it relatable.

Some things I noticed, you mention registers in the insert mode section before explaining what they are. It seemed odd to me that you used the word before explaining what it meant, but maybe it is unavoidable?

I also noticed you completely left out folds (z, :help fold). Personally, I aggressively fold code I'm not working on so I think they are super important :D. There was a plugin posted recently thats a cool alternative to folding though (similar to emacs narrow) [0] [1].

[0] https://github.com/hoschi/yode-nvim

Show HN: Yode-Nvim – Focused Code Editing for Neovim\ (3 comments)

found it, check this issue: https://github.com/hoschi/yode-nvim/issues/5