> and a patched version of vim though.
Found it, looks very interesting!
>
> You could use external tools that display a dialog and return some
> kind of value you could work with. Those are often named Xdialog,
> where X is the name of the toolkit being used. Or just "dialog" if
> you're on the terminal.
>
> If you have python/ruby/perl support compiled in, there might be other
> options.
Yes, I will consider that as the last option, as I understand it will
be a platform specific solution only. Gtk and Tk dialogs with
python/ruby/perl are possible under Linux, I don't know about the same
in Windows 'cause since recently I use vim also in there.
> You could also think of presenting the users a buffer with a form that
> can be easily parsed and set nomodifiable via CursorMoved(I) if the
> cursor is over a field tag. I use that approach in one plugin and it
> works well for me.
Could you please share the link to the plugin, if it's public.
> IMHO in many cases good command-line completion is the better solution
> though.
In most cases yes, but sometimes checking a checkbox is faster then
typing an extra long pattern in command line.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
To unsubscribe, reply using "remove me" as the subject.
No comments:
Post a Comment