Hi Bram, On Tue, Aug 23, 2022 at 11:55 AM Bram Moolenaar <[email protected]> wrote:
> > It is unlikely someone wants to get all variables and functions of all > scripts. This adds a lot of overhead to the return value of > getscriptinfo(). > > The "version" item seems useful. I will create a separate PR to add the "version" item. > The "functions" and "variables" are > better obtained for a function that does this for one script. I do > wonder what the use of it is. What would justify adding this > functionality? Making the script-local items accessible can be used for > hacks, the writer of the script may not want to make it so easy to > access them. > > All the script-local functions can be already listed by using the ":function" command without any arguments. This change just makes it easier to get it as a List. Getting the list of script-local variables and their values is useful for debugging plugin issues (without modifying the plugin). It is useful for plugin developers. I will create a PR to filter the results by a particular script name. Regards, Yegappan -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3Dv%2Bemj%2Bq8r0ELEwfXnphoa%2B9A%3DDpVwDLbbxViCw8w6eg%40mail.gmail.com.
