69598Re: capture() function to get output of command
- May 13 1:02 PM
On 10-May-2013 04:09 +0200, mattn wrote:
I beg your pardon, but I find your entire argument weak and unconstructive.
> On Thursday, May 9, 2013 7:54:38 AM UTC+9, ZyX wrote:
> I don't hope that capture() contains highlight attributes. It should
> be plain text.
Both ZyX's and my recent messages have already shown cases where this
additional information is essential. If you don't need it, ignore the
information / don't request it (my suggestion makes this optional via a
> And I guess fixing redir nesting has problems.
Your intuitions and guesses aren't really helpful in this otherwise very
> 1. There are plugins that depend on original behavior. This break compatible.
I cannot think of a plugin that depends on having a nested :redir throw
an error. That's just bad coding practice, and it could easily be
corrected in the plugin. Do you have an actual example? As I've shown,
contrarily there are plugins that (when working together) are indeed
broken due to what I would call an implementation deficiency.
> [3 lines deleted]
Please take no offense, I value your opinion like every other, but
please support them with facts and concrete examples as much as
possible. Thank you.
-- regards, ingo
You received this message from the "vim_dev" 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
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe@....
For more options, visit https://groups.google.com/groups/opt_out.
- << Previous post in topic Next post in topic >>