72286Re: [request] Events for some internal function calls
- Jul 17, 2013On Wednesday, July 17, 2013 10:06:26 PM UTC+8, Bram Moolenaar wrote:
> Curist wrote:Is there any way to work around it?
> > Say, delete(), mkdir(), writefile(), and other functions that will
> > alter file system state I'm not aware of.
> > Emitting ShellCmdPost or even a new event would makes life easier.
> This will cause a chicken-egg problem. These functions are supposed to
> be "low level", and not have any side effects. If autocommands trigger
> for these you might mess up the plugin that's using them. Handling side
> effects of autocommands is already too complicated.
> Female engineers become irresistible at the age of consent and remain that
> way until about thirty minutes after their clinical death. Longer if it's a
> warm day.
> (Scott Adams - The Dilbert principle)
> /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
> /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\ an exciting new programming language -- http://www.Zimbu.org ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
Previously the 'extend' bug can override built-in functions,
which can alter things at higher level.
(see here: https://groups.google.com/forum/#!topic/vim_dev/3d-hgadlqvQ )
And for the autocmd messing plugin part, invent another event will do it, right?
That may be a bit hackish, error-prone, complicate things unnecessary.
Okay, guess that's not a good idea.
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