Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
More explicit documentation and UI suggestions #376
I have been trying to use Ivy in Spacemacs and I must say, I quite like its interface. Good work
I'll list some questions and suggestions:
I think that would be nice to have something like
Some UI issues with the interface that shows up after pressing
Well, that's it. I hope my suggestions are useful to you. And thanks for creating Ivy, it's great.
Ivy does it in an Emacs-standard way - press C-h m or
They're just column descriptors meant to bring a bit more structure. The bindings under "Yes" column do stuff, while the bindings in the "No" column cancel stuff.
What you describe is true, don't see the point though.
Backspace does the same thing as o does. And C-o is a toggle.
Yes, I know, I used that. I prefer UIs that make things more discoverable, but I understand your point. Consider the Spacemacs case. Let's say that
Ops, sorry, I didn't know that. Sure, I'll discuss that there.
OK, I understand now. But it's hard to tell this from the words
Never mind, I was writing this issue and accidentally opened it before writing all the text. I updated it, by the way. That was just an annotation.
Sorry, same thing, this was just an annotation.
Thanks for your answer. Please read the updated post.
I updated my answer a bit too. Please read it on GitHub if you were using email.
Thanks for updating the README.
Please think about my suggestions for the options panel. I think some words are a bit confusing now - probably new users will agree with that more than people that are already used to it. That's why I tried to write down all my questions in the first time I used Ivy.
If you have concrete ideas, do share. So far, no one has complained about the options panel. I use it a bit and like the shortcuts. The descriptions are OK for me, as long as they keep the whole thing small. I wouldn't mind changing the descriptions to be more clear as long as they don't increase the size of the panel.
I mentioned a few in my first post. But I'll summarise them here.
Most issues are about bugs, because them can completely break one's workflow.
I'm not writing this to know what the keys do. Even if the word for some action were called "foo", I would be able to just use it and discover what it does.
Again, you have been using this since day one so of course you are used to the
Here are my suggestions:
These are mnemonic devices resulting from a limited set of single-key bindings. Being non-invasive and small is better in the long run than being overly descriptive.
I don't want to do it by default, perhaps you can get it in a spacemacs layer. However, I've added C-h m (