AK wrote:
On 01/12/2012 04:53 PM, Erik Falor wrote:
On Thu, Jan 12, 2012 at 08:17:06PM +0100, Marc Weber wrote:
I don't want to offend anybody. Just trying to understand whether
having JS support would change anything. So please consider this thread
as being a test whether such a change would pay off in the long run for
the community.
I'm getting lost in this discussion. Are we discussing the addition
of a JavaScript interface, or the wholesale replacement of VimL with
JavaScript?
===
Look, I didn't say anything about making vim 'not vim' -- I just wanted
a /p syntax like GREP added, -P, to use perl syntax... that doesn't mean
getting rid of any other stuff... let's be reasonable!
perl was a text and pattern processing language from the start. it was
designed to do text manipulation and filtering. That's not true of Ruby,
javascript or python.
The other languages would HURT vim scripting -- in so much that MANY
tasks can be done in a 'one-liner' (in vim as well, just very
different)...that would be impossible in javascript, python or ruby.
They are not concise languages.
To me, better perl integration would be matching text processing
with text
editing... that's not the case for the other languages -- not that the
re incapable of doing such things, just that perl has been designed for
20+ years to automate large chunks of what one might do by hand in vim,
or write a macro for -- it's just that having used vim for well over 15
years, I still don't have
a good grasp on the scripting or the replacement syntax.
And Lest anyone think I'm alone or uniq?!?
I found a bug in the perl.vim file recently where the author didn't know the
exact stuff I was complaining about being hard to learn -- all the RE
exceptions.
I knew the same bug was in Javascript syntax (.. I scanned the other vim
files for the same pattern.
64 of the files in the syntax dir have the same problem pattern (over
1/10th)
of vim authors don't know or remember it's syntax, despite having enough
expertise to write syntax plugins.
That's the problem I'm talking about...But an editing macro language is
going to be a big unique -- it's doing a specialized function. That
doesn' mean it's
search & replace have to _*exclusive*_ be uniq...
Linda
--
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
