Closed GoogleCodeExporter closed 8 years ago
This is off in the latest dev version and there is an option to turn it on too.
Original comment by habamax
on 12 Jan 2012 at 7:33
Well, most files I have take dozen to several dozen seconds to convert to HTML,
and I do not think I am alone. It is a bad idea to not indicate to the user
that the program is blocked because of some unfinished operation. Every
sensibly designed program uses some sort of indication of "busy" for longer
blocking operations, and we are talking longer longer longer operations here.
The problem with having to press enter: that is very annoying indeed, and is
due to the way vim works, unfortunately. However, it does not normally happen
with short status messages like those displayed when converting to HTML.
I suspect that either you work in an extremely narrow window, or you have a
customized "statusline" option which puts a lot of information on the
statusline (some people have fileencoding and the char under cursor and other
things showing), which unfortunately causes conflicts/prompts to press enter.
Can you try to see if you can adjust your settings ("statusline" or
"laststatus") to solve the issue rather than demanding that the short status
info from vimwiki be turned off for everyone?
Original comment by tpospi...@gmail.com
on 13 Jan 2012 at 3:39
Please read my request. I asked for the ability to turn it off, not to have it
removed.
habamax further stated that a toggle is already available in dev version.
Original comment by eydai...@gmail.com
on 13 Jan 2012 at 5:02
I did read your request. My comment is not very cheerful, but that is not
because you filed the issue, it is because I found out the status has been
turned off by default (which in practice means it won't be available to new
users, who are most likely to be puzzled by the apparent freezing).
Also, this whole issue gets swept under carpet, with you contributing no
information that would help to shed light onto the underlying cause (which
would be very useful for other people who may be affected because they use
similar configuration to the one you have).
Original comment by tpospi...@gmail.com
on 13 Jan 2012 at 9:35
Original issue reported on code.google.com by
eydai...@gmail.com
on 12 Jan 2012 at 6:26