perspective-el VS toggleterm.nvim

I opened a ticket https://github.com/nex3/perspective-el/issues/198 but can’t promise to get around to it soon.

I have tried to get this behaviour for a while. The closest I have gotten is using perspective.el, but it ended up being a bit clunky when I tried it like 4 years ago and now I just used bookmark+ which can save/load desktop files as bookmarks.

perspective for named workspaces.

persp-mode?

To scratch a personal itch, I created a little package that integrates perspective-el into the built-in tab-bar.

But I'm rethinking about my approach, as tab-bar-mode would give me nice visual help (#3), and it seems difficult to recover a perspective using perspective, and persp-mode may be a better fit in that sense (#4). The Treemacs integration isn't working for me either, and I get the same list of file trees for all perspectives -- I'm pretty sure I'm doing something stupid, but this was handled nicely with Doom Emacs's workspace support (#5). But perspective seems to work best for segregated buffer list (#1).

I think perspective.el is about what I’m looking for. If you had a list of org-ids, theses could be brought up in indirect buffers, and then those buffers added to the perspective group.

As for why this broke: this change went into Perspective a few weeks after Emacs 28 shipped. You either updated your packages recently after not updating for a while, or you switched to Emacs 28 (or later). Full discussion surrounding this change: https://github.com/nex3/perspective-el/issues/180

It sounds a bit like you want „perspective.el“ (1). It allows you to define „virtual workspaces“ of buffers with individual window layouts. On each virtual desktop the standard buffer list is replaced with a shorter showing only buffers belonging to the current context. I use it every day to keep „code“ buffers separate from my „test“ buffers.

(1) https://github.com/nex3/perspective-el

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