You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way this is written, reports are either a result of plugin loading; plugin load reports stick around, and there can only be one debug report at a time. I'd like to be able to save debug reports for later. The exact use case I am thinking of:
Right now, in my dotfiles, I have a separate plugin that calls compinit because I want to be able to see a report on what compinit does. If there was support for saving a debug report under a name for later, I could just do something like this:
and then it would show up as part of all-reports. All-reports currently is hardcoded to output all the plugins, and the global debug report. I could just hack _local/compinit into the global plugin structure, since it's not a real plugin, that might have weird consequences.
The text was updated successfully, but these errors were encountered:
The way this is written, reports are either a result of plugin loading; plugin load reports stick around, and there can only be one debug report at a time. I'd like to be able to save debug reports for later. The exact use case I am thinking of:
Right now, in my dotfiles, I have a separate plugin that calls compinit because I want to be able to see a report on what compinit does. If there was support for saving a debug report under a name for later, I could just do something like this:
and then it would show up as part of all-reports. All-reports currently is hardcoded to output all the plugins, and the global debug report. I could just hack _local/compinit into the global plugin structure, since it's not a real plugin, that might have weird consequences.
The text was updated successfully, but these errors were encountered: