Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Edgy.nvim to put Trouble and other things in a sidebar, and forced bottom. #1392

Open
greggh opened this issue Jan 7, 2025 · 8 comments · May be fixed by #1393
Open

Use Edgy.nvim to put Trouble and other things in a sidebar, and forced bottom. #1392

greggh opened this issue Jan 7, 2025 · 8 comments · May be fixed by #1393
Labels
enhancement New feature or request

Comments

@greggh
Copy link

greggh commented Jan 7, 2025

Feature description

I was looking over the docs for Trouble and saw the screenshot at the top of the page here:

https://github.com/folke/trouble.nvim

That config with a sidebar and bottom for the 3 Trouble windows that I use would be perfect. Folke says that this is the config he is using (in a thread there):

https://www.lazyvim.org/extras/ui/edgy

I tried to get this all going in the user folder and I am just failing to make it work. But then I noticed that nearly everything in that config is in your setup, other than Grug Far, so maybe this should be part of the main dotfiles and not in my user folder.

Thoughts?

My hope was to have one key bind that would let me bring up all 3 of those Trouble windows exactly like that screenshot, and also close them all when done again, like a toggle.

Additional information

No response

@greggh greggh added the enhancement New feature or request label Jan 7, 2025
@CharlesChiuGit
Copy link
Collaborator

maybe a PR would be nice?

@ayamir
Copy link
Owner

ayamir commented Jan 8, 2025

A useful plugin, IMO it's worthy to add it.

@greggh
Copy link
Author

greggh commented Jan 8, 2025

maybe a PR would be nice?

I 100% agree, I just know I am not at the level of this config and you two yet. This is my first true neovim config and not just using vanilla vim. If I made you a PR for this, I would probably break more than I fix. I am using this config and editing it to learn how to do this in neovim. I can try if thats what we all decide on.

@CharlesChiuGit
Copy link
Collaborator

ok then. I'll try to add this plugin when i got time. Currently working on my master thesis lol

BTW, we usually propose plugins at #494 and have some discussions over there.

@ayamir ayamir linked a pull request Jan 9, 2025 that will close this issue
@ayamir
Copy link
Owner

ayamir commented Jan 9, 2025

Work for it now. Besides, I want to use neo-tree.nvim to replace nvim-tree.lua b/c neotree is more powerful.

@CharlesChiuGit
Copy link
Collaborator

@ayamir have u tried oil.nvim before?

https://youtu.be/218PFRsvu2o

based on my understanding, oil.nvim let u "edit" the file explorer as if it's a plain text file, so we don't need to config lots of keymaps for file operations.

@ayamir
Copy link
Owner

ayamir commented Jan 10, 2025

based on my understanding, oil.nvim let u "edit" the file explorer as if it's a plain text file, so we don't need to config lots of keymaps for file operations.

@CharlesChiuGit Nice plugin, DO like its design concept and worthy to try. IMO we should keep usage habits consistent as much as possible if we want to replace nvim-tree.lua with oil.nvim. Have you already used it in your own config?

@CharlesChiuGit
Copy link
Collaborator

CharlesChiuGit commented Jan 10, 2025

IMO we should keep usage habits consistent as much as possible

agree.

Have you already used it in your own config?

I tried it before, but i didn't understand it's concept at that time so i removed it. After watching TJ's yt video, i think i should give it another try.
CharlesChiuGit/nvimdots.lua@7971d93
Here's my config back then, most of it are default settings if i remember it correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants