Ramel Eshed wrote: > In every Vim plugin that I've used (which are not too many though) > there was a protection on the general-purpose buffers (done by setting > and resetting 'modifiable'). > The concern, I guess, is not to prevent the user from changing the > buffer deliberately rather then to protect from stupid mistakes. Here, > when the buffer changed asynchronously it is even more dangerous. For > example: what if the user by mistake will press 'p' while the buffer > is being updated? -In other cases a simple undo will help but here it > is likely that before the user will press 'u' there will be many new > lines added by the job output so undo will delete them instead. > Is it possible to add an option to the job that will let it override > 'modifiable' just for the out_io?
If you try it out, you will see that currently there is an error message, but the lines are appended to the buffer anyway. Probably the worst that could happen. I'm a bit careful to just append lines to a nomodifiable buffer. Could cause trouble when picking the wrong buffer. We could add an option: 'modifiable': 0 -- How To Keep A Healthy Level Of Insanity: 5. Put decaf in the coffee maker for 3 weeks. Once everyone has gotten over their caffeine addictions, switch to espresso. /// Bram Moolenaar -- [email protected] -- 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 /// -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
