Design Discussions

[kylechui]

One of my personal goals is for you to feel like nvim-surround is working for you, instead of the other way around. I want things to feel intuitive and to "just work", to minimize mental overhead. Thus I think feedback from the community is very important, to better understand everybody's wants/needs and to see what balance I can strike to make this work for as many people as possible. Furthermore, hopefully this would let me make better-informed decisions about what to do moving forwards, and reduce the number of posts in #77.

Every time some UI design choice is made available to me when I'm fixing a bug, introducing a new feature, or just refactoring the codebase, I'll make a post here with a link to a related discussions post. The idea is that discussion posts aren't great by themselves, since people aren't usually notified when new ones pop up. Thus I hope that people will subscribe to this issue and get notified of when new discussions about the future of the project are ongoing.

You don't need to write long, detailed responses to everything; even something as simple as reacting with 👍 or 👎 helps me gauge which ideas are/aren't popular. Thanks for taking the time to read this!

[kylechui]

First post about how to modify custom selections can be found here.

[kylechui]

Discussion on how documentation should be split/coordinated between the built-in help docs and wiki can be found here.

[kylechui]

Discussion on how filetype-specific default configurations should be exposed to the user can be found here.

[kylechui]

Discussion on new "end" and "sticky" keys for move_cursor can be found here.