Feature Request: all plug-ins be closed

[chenxin0397]

Feature Requested

After the update, all plug-ins cannot be closed uniformly, and it becomes complicated to achieve this effect

Relevant Screenshot

No response

Checklist

• [X] The feature would be useful to more users than just me.

[nhan000]

Many new features are great but it's weird to see why the "disable all Plug-ins" function was taken away

[geoffreysflaminglasersword]

Feature Requested

After the update, all plug-ins cannot be closed uniformly, and it becomes complicated to achieve this effect

Relevant Screenshot

No response

Checklist

• [X] The feature would be useful to more users than just me.

You'll have to clarify what you mean by "closed uniformly"

Many new features are great but it's weird to see why the "disable all Plug-ins" function was taken away

Assuming that's also what the first comment was about, you can do that by disabling community plugins (entering "safe mode"), so I don't see the need for it.

If for some reason you desperately need safe mode disabled and all plugins disabled, either feel free to add it yourself, or you can do that pretty easily by clicking bisect a few times, then manually disabling the last plugin.

I have over 150 plugins and 7 bisections is the same as disabling all. In my mind that's pretty simple and makes it not worth cluttering things with another command.

[chenxin0397]

Please tell me, what plugin can I use to disable all plugins, I just need this one function

[chenxin0397]

Feature Requested

After the update, all plug-ins cannot be closed uniformly, and it becomes complicated to achieve this effect

Relevant Screenshot

No response

Checklist

• [x] The feature would be useful to more users than just me.

You'll have to clarify what you mean by "closed uniformly"

Many new features are great but it's weird to see why the "disable all Plug-ins" function was taken away

Assuming that's also what the first comment was about, you can do that by disabling community plugins (entering "safe mode"), so I don't see the need for it.

If for some reason you desperately need safe mode disabled and all plugins disabled, either feel free to add it yourself, or you can do that pretty easily by clicking bisect a few times, then manually disabling the last plugin.

I have over 150 plugins and 7 bisections is the same as disabling all. In my mind that's pretty simple and makes it not worth cluttering things with another command.

Please tell me, what plugin can I use to disable all plugins, I just need this one function

[nhan000]

disabling community plugins (entering "safe mode")

thank you @geoffreysflaminglasersword! That didn't come to my mind. I guess I was used to being able to disable all plugins using the command from the command panel instead of going into the settings.

[geoffreysflaminglasersword]

What is your use case?

[chenxin0397]

What is your use case?

I set up some manifests to manage my plugin startup differently. But when new plugins are added, plugins that are manually turned on or off are not called by manifests. So I need to close and then use the plug-in list, and start the part of the plug-in I want to start according to my needs

[geoffreysflaminglasersword]

What is your use case?

I set up some manifests to manage my plugin startup differently. But when new plugins are added, plugins that are manually turned on or off are not called by manifests. So I need to close and then use the plug-in list, and start the part of the plug-in I want to start according to my needs

I'm not quite understanding, but that sounds very specific to you. Again, feel free to make a pull request, but it sounds like you'd just as well make calls directly to obsidian from whatever startup process you've set up rather than relying on a third party plugin.

[chenxin0397]

What is your use case?

I set up some manifests to manage my plugin startup differently. But when new plugins are added, plugins that are manually turned on or off are not called by manifests. So I need to close and then use the plug-in list, and start the part of the plug-in I want to start according to my needs

I'm not quite understanding, but that sounds very specific to you. Again, feel free to make a pull request, but it sounds like you'd just as well make calls directly to obsidian from whatever startup process you've set up rather than relying on a third party plugin.

Because too many plug-ins opened will affect the speed of starting OB, so I used the method in the following URL. https://tfthacker.medium.com/improve-obsidian-startup-time-on-older-devices-with-the-faststart-script-70a6c590309f

Even so, some plug-ins will still be turned on manually. If you don’t remember to turn them off, it will affect the turn-on time at the next startup

[chenxin0397]

Or, it can be like this, please separate the plug-in functions of the old version, as long as the functions of version 0.4.0 can be kept and not automatically updated to 1.0.0, my needs can also be met.

[ooker777]

feel free to add it yourself

Do you mean to allow contribution to this plugin, or do you mean who need it need to fork their own version?

In my mind that's pretty simple and makes it not worth cluttering things with another command

So is it correct to say you're your use case has more priority than others' use case? It's nothing wrong on that, I just want to know. If that's not the case, how do you know that most people find that it's cluttering with another command? (I presume the bisect one)

My use case: I want to test one plugin. I need the safe mode to be disabled, and disable all plugins. Then I enable that one plugin, and gradually enable other plugins.