crafted-emacs VS toggleterm.nvim

Keep an eye on Crafted Emacs which has a v2Beta release branch. It's been evolving. The v2Beta is a rewrite. It aims to provide a minimalist leg up on vanilla Emacs for new Emacs users. It's goal is to take you from first steps to a point where you have learned a great deal and built your configuration. Then you may be comfortable ditching the Crafted Emacs boilerplate configuration entirely. Think of it as a starter kit. Follow SystemCrafters on YouTube (live stream mostly) & Matrix (they are leaving Discord). Despite the live stream being lengthy, there is much to be learned as you bear witness to David figuring things out. Over time, you pickup on those techniques such as looking up a variable state, reviewing functions, evaluating snippets of Elisp in real time, etc. Also recommend, Mastering Emacs as a fantastic ebook with free updates. Once 29.1 ships, no doubt, there will be a free update to the ebook.

I'd recommend you have a look at crafted-emacs. It's an example of how far Emacs can actually go without third-party packages. Then you can add minimal packages (completion and specific tool integrations) to further enhance the experience.

For me it's quite stable except some issues I had with vertico. Anyways, I first started to rewrite my doom config into plain vanilla emacs (with org mode literate configs), and then I discovered crafted which allowed me to remove some code with commonly set sane defaults, e.g. stuff from https://github.com/SystemCrafters/crafted-emacs/blob/master/modules/crafted-defaults.el.

I have been surprised at how many people have so ardently defended only using built-ins and raw package.el and their own janky ensure methods when use-package was available and did it all better. And, it even lets you configure Emacs itself (not just packages), as well as seamlessly letting you try different package management tools like straight.el. Getting it into Emacs itself hopefully makes this a more prevalent way of showing users how to craft their own config.

If you need a staring point for configuring there's some nice light ones like emacs-bedrock and crafted-emacs, and also some fully pre-configured Emacs distributions that you can choose from (though those look harder to configure to one's personal needs to me, but I haven't tried them so wouldn't know).

I'll second https://github.com/SystemCrafters/crafted-emacs

And if you find yourself between the two extremes, perhaps https://github.com/SystemCrafters/crafted-emacs

As a data point, I'd like to chime in here. I have been a 15 year user of tmux (and screen before that) and never thought I'd change my development habits. Over the holidays I decided I would do one of those once-every-five-years upgrades to my vim setup as I had accrued dozens of vendored plugins in normal vim and wanted to see what the big deal with neovim was.

I bit the bullet and evaluated some of the "distributions" (AstroNvim and kickstarter) and played around with all the new lua plugins that I had never thought I needed (why use telescope when FZF-vim worked so well?).

Anyways, after a month of tweaking and absorbing, I found myself running Neovide only, and doing something I never thought I'd see, running tmux from within neovim/neovide. I think this only works (for me) because of session management (there are half a dozen plugins for handling quickly changing 'workspaces') and because the built-in terminal (with a very useful plugin called toggleterm: https://github.com/akinsho/toggleterm.nvim) works so well.

I have not stopped using tmux and layouts, and it sits in another fullscreen iterm2 workspace, but I find that I now spend 90% of my time using a fullscreen neovide and summoning/toggling tmux momentarily for running commands.

Of course, the caveat here is that my preferred mode of operation is being fullscreen as often as possible. I think if your preferred mode of operation is to always see splits then running neovim from the terminal within tmux is still the way to go.

As for why I like neovide? I find the animations, when tweaked to be less 'cool' are extremely useful to see where the cursor jumps to. I am also a huge fan of the fact that I can finally use 'linespace' to put some space between my lines of code -- it is an aesthetic I didn't realize I wanted.

For splitting the terminal you could try either toggleterm or tmux. If you want to send things from one tmux pane to another, then you can use slime. For a toggle-able filetree, you can use nvim tree.

I just found toggleterm which feels awesome. Pretty much exactly what I was looking for to use with Alacritty but even better since its integrated into the rest of my Neovim workflow.

I saw this plugin that tells me how to do it, however I got confused after I added "require("toggleterm").setup({})" in the lazy.lua file and installed the package as well using the Lazy command

I tried toggleterm but I wasn't successful.

And I never really got into Gitsigns or vim-fugitive. Lots of people love them, so I'm sure they're great, but I'm happy opening a floating terminal with Toggleterm and using Lazygit.

I agree with u/Bamseg, but you can get what you want using toggleterm.nvim BUT NOT IN FLOAT.

I use gitsigns for linewise operations (blame, reset, etc), and a floating terminal (toggleterm) for everything else. flatten.nvim also helps with nested nvim instances.

but I ended up finding a good enough workaround by using Lazygit through Toggleterm.

Perhaps you want something like https://github.com/akinsho/toggleterm.nvim and make a custom profile? Remapping a key for each extension seems fine as well, just remap it per-buffer inside of on_attach