-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Auto-suggestion for markdown is kind of broken #569
Comments
You will have to be a little bit more specific here. The suggestions in place for markdown is the standard words-in-buffers markdown, and personally I find that useful as it will suggest common words in the recent buffers. What do you see as not helpful? |
Sure thing! My point is that suggesting currently used words is mainly helpful for programming languages because those words in the buffer are likely variables. In a regular message, only significant words would need this first class treatment. Maybe not even then. How often one tries to autocomplete words in google docs? I often don't. This problem becames even greater if you think about the option confirmation key used by howl "enter". Imagine I'm writting my markdown document and I need to break the line, because it just got too long for some reason. If howl, by itself, decide to show word options, instead of breaking the line, you will actually be changing a word that might already be complete. Therefore causing a ctrl-z + enter again. Example:
After typing "Mold" for the second time, howl will suggest me the word "mold", not capitalized. But if I finished typing "Mold", I'll try to break the line and this will change "Mold" with "mold", which is not what I want. So, possible solutions:
|
Just noticed while writting a markdown document word suggestion that is not helpful. Not sure which rules are used for auto-suggestion for markup documents, but they should probably be turned-off.
One useulf auto suggestion for documents in markdown, as an example, would be a explanation pop-up when using a markdown markup.
The text was updated successfully, but these errors were encountered: