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

Feature Request: Own window separator #45

Closed
Mariappan opened this issue Apr 1, 2019 · 22 comments
Closed

Feature Request: Own window separator #45

Mariappan opened this issue Apr 1, 2019 · 22 comments

Comments

@Mariappan
Copy link
Contributor

Since neovim supports external window management, do you have plans to add this support in gonvim ?

Also floating window support and virtual text support

@akiyosi
Copy link
Owner

akiyosi commented Apr 1, 2019

HI,

I plan to add the feature in v0.4.0.
But those features, the floating window and the virtual text should be work in the current version as well.

@Mariappan
Copy link
Contributor Author

May be not in the remote attachment ?

I tried to use git-p.nvim plugin which seems to work in terminal version. But with gonvim in remote attachment, it does not seems to work 🤔

@akiyosi
Copy link
Owner

akiyosi commented Apr 1, 2019

Umm..., I do not use those features in remote attachments. 🤔
I will check.

@akiyosi
Copy link
Owner

akiyosi commented Apr 1, 2019

In passing, is remote nvim using 0.4.0?

@Mariappan
Copy link
Contributor Author

Yes it is
NVIM v0.4.0-430-g8698830cb Build type: RelWithDebInfo LuaJIT 2.0.5

@akiyosi
Copy link
Owner

akiyosi commented Apr 2, 2019

I checked the feature; the floating window and the virtual text with the remote attachment and confirmed that it works.
I did not work well the git-p.nvim.
Instead I checked with Shougo/deol.nvim and w0rp/ale.

@Mariappan
Copy link
Contributor Author

@akiyosi I am seeing there are some checkins in the multi-grid branch.
Is it in workable condition?
Any chance I get a linux binary to test 😃

@akiyosi
Copy link
Owner

akiyosi commented May 11, 2019

@Mariappan
Yes, It is work with nvim v0.4.0.
But currentry, there is a bug. See neovim/neovim#9899

@Mariappan
Copy link
Contributor Author

Cool @akiyosi
Can you please share the linux zip then ?
I can start testing. I dont use tabs much so it wont impact me much

@akiyosi
Copy link
Owner

akiyosi commented May 12, 2019

Ummm,
Is it possible to build on your machine?
I think it is not at the stage that can share the binary yet.😥
There are still bugs in neovim's Multigrid UI, and the implementation policy on the GUI side has not been clearly obtained.

@Mariappan
Copy link
Contributor Author

@akiyosi
After some boring stuff, compiled successfully the multigrid branch.
And I found the reason for the window close problem too. Raised a PR to fix it.

#55

Once you verify this fix, you can close the neovim/neovim#9899

@Mariappan
Copy link
Contributor Author

This multigrid-branch is pretty much usable. I am using for half an hour and it looks fine.

One compelling thing needed urgently is to implement the window separators for horizontal and vertical split. It looks aweful

@akiyosi
Copy link
Owner

akiyosi commented May 14, 2019

@Mariappan
Thank you very much.
Perhaps it was added in the debugging of Multigrid UI events in old commit of nvim.😅

One compelling thing needed urgently is to implement the window separators for horizontal and vertical split. It looks aweful

I think the window separator is equivalent to the original vim at present, is it so aweful?

@Mariappan
Copy link
Contributor Author

Mariappan commented May 14, 2019

Screenshot 2019-05-15 at 12 49 51 AM

Please take a look 😢
In the above pic, there are two splits, one horizontal split and then one vertical split and three windows
But very difficult to distinguish between them

@akiyosi
Copy link
Owner

akiyosi commented May 14, 2019

Umm, ok.
I will consider 😁

@akiyosi
Copy link
Owner

akiyosi commented May 22, 2019

I made minimal changes to draw window separators now 31ad7c5
I want your opinion.

@Mariappan
Copy link
Contributor Author

Thanks @akiyosi. I have tried your changes and it looks fine.
In vertical separator, the file name is shown which has to be removed, which i believe, you will fix it in the further updates.

I have one doubt, are we not creating separate windows, for splits ?
Are we using same one window for all the splits and just drawing the line to create/visualise the splits.
Sorry I don't understand the design

@akiyosi
Copy link
Owner

akiyosi commented May 23, 2019

@Mariappan
Currently, gonvim creates a window-widget for each neovim window.
In the Multigrid UI, the window separator(and file name, ruler info in the statusline) is notified as an grid-event with a special grid ID 1, and the current separator implementation is drawing for window widget with a grid ID 1.

@Mariappan
Copy link
Contributor Author

Thanks @akiyosi I have tried the latest changes and it looks awesome.
This is my daily driver now. Thanks for addressing this in very short time 😄

There is one bug in gonvimfuzzyAg display which I am tracking now.
Will raise pull request once i found RC

@Mariappan
Copy link
Contributor Author

Hi @akiyosi There is some cursor bug in 0.4.0 branch currently
When you move the arrows using left and right arrow keys, I am seeing this .
Screenshot 2019-06-02 at 7 39 06 PM

Also cursor shape move from block to vertical

@Mariappan
Copy link
Contributor Author

Screenshot 2019-06-02 at 7 41 45 PM

@akiyosi
Copy link
Owner

akiyosi commented Jun 2, 2019

@Mariappan
Thank you for your testing!
I am very grateful.

Also cursor shape move from block to vertical

I think it is default guicursor value behavior.
You can confirm the same behavior in macvim.
If you want to change the behavior, you should set the guicursor option.
command-line Normal and command-line Insert are the targets of setting, especially for the behavior you pointed out🙂

By the way, I fixed the cursor position bug 0df8f9d

@akiyosi akiyosi closed this as completed Nov 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants