vimr VS NSWindowStyles

For the commenters here: do we have something like VimR [1] for OSes other than the Mac that provides a file explorer sidebar with smaller font size (probably sans)?

[1]: https://github.com/qvacua/vimr

I'm loading sessions at BufReadPost (also tried BufReadPre, which didn't work) instead of VimEnter because I couldn't find a way to find out the "true" CWD at VimEnter. I use VimR, which seems to launch nvim without any arguments even when I launch it from the command line like vimr path/to/file.ext or opening a file in macOS Finder, and set the CWD to $HOME instead of path/to. So at VimEnter, I'm only able to restore a session saved for $HOME, but not my project directory.

https://github.com/qvacua/vimr and https://github.com/qvacua/neovim/tree/5f8dd8c4a33203277cf6058f559383626411693d are good places to start

I've never tried a GUI version of Neovim, and this is the first I've heard of MacVim. Are you referring to VimR? If so, it seems like the problem could have been with the third party GUI software instead of the core Neovim software.

You’ll need an NSWindow (I.e., use an app delegate instead of the “SwiftUI life cycle”) and then you can customize it however you like: https://github.com/lukakerr/NSWindowStyles

> how does the wrapper handle different UI/UX guidelines?

Most of it is automatically handled by the native interface of the OS when it renders the UI, some rare cases have to be dealt by the wrapper library developer, and some of it has to be done by the developer creating the app using the wrapper library.

For example, a Window usually has the default UI elements of a Title Bar, the title text, Max-minimize buttons, window resize handlers etc. In Windows, this is rendered with the Max-minimise buttons on the top-right corner, and the title left aligned in the title bar (if I remember right). On macOS, the same Window will be rendered with the max-minimise button on the top-left corner and the title centered in the title bar.

When you create a window on MS Windows OS using the Win32 API for it - http://www.winprog.org/tutorial/simple_window.html - the rendered window will be, by default, according to Microsoft UI / UX guidelines. Similarly, when you create a window using the cocoa faramework on macOS, the window will be rendered by default according to the UI / UX guidelines of Apple - https://github.com/lukakerr/NSWindowStyles .

This highlights how some UI / UX guidelines are baked into the native frameworks.

But if the wrapper library developer wants to create a custom UI component, they will have to ensure that the component is compliant with UI / UX guidelines of the OS they are rendered in.