On Oct 17, 9:50 am, Ben Fritz <fritzophre...@gmail.com> wrote: > > I've seen at least these suggestions: > > 1. Have an "envpush" and "envpop" command (or similar) which would > create a restorable state of all options which could be pushed and > popped at will by script authors. Authors would do "envpush" at the > beginning of each script, and at the beginning of each function, then > "set all&", then "envpop" and the end of the script/function. > 2. Have script-local options similar to buffer/window/tab/script-local > variables and buffer/window/tab-local options. This would introduce > commands like "setscript" and a new pattern similar to :set cpo& > or :set cpo< which currently set the option to the default or to the > global value, to set a script-local option to the current local/global > value. Any options set local to the script would retain their value in > mappings and autocmds, similar to how script-local variables work. > Authors would probably ":setscript all&" at the beginning of the > script, and individually set options which ought to use the user > settings to do so. > 3. Leave things as-is, and rely on script authors to find and account > for problem settings. There are plugins to help with this, I think Dr. > Chip has one on his site. >
Some discussion in the past: http://groups.google.com/group/vim_dev/browse_thread/thread/86c5e0338f3f2a35 http://groups.google.com/group/vim_dev/browse_thread/thread/92bce4a37ae9858f/07cda2bd46fc62b4?lnk=gst&q=option+stack#07cda2bd46fc62b4 -- 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
