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.

Feature Requested

First, just want to say I really appreciate this plugin! I think it would be even better if you could: 1: select plugins to exclude in the settings menu (e.g. I'm confident that plugins like Git and Sliding Panes will pretty much never be a problem so I don't ever want to disable them) 2: use the same functionality available for plugins on CSS snippets in the appearance tab 3: back-track... meaning several things:

• I just found the problem plugin, I'd like to re-enable all of the plugins that were active when I started (users often have disabled plugins installed, it's a chore to figure out which one's weren't enabled)
• I'm several levels deep and the problem just went away. That means the problem is in the complement of the current set from the last set. I definitely wasn't keeping track of all the plugins that were just disabled so I need to enable just the ones that were just disabled

There's a few ways do do that, and I think a few commands could replace existing ones*

• save and recall commands.
  1. a simple implementation would be to just save the current state and recall that exact state, that could work ok with existing commands, but you run into the issue of either not being able to back-track, or back-tracking overwriting your original list of plugins
  2. Potentially you could instead have a stack of sets, with bisect/un-bisect commands
• The second method above is better in my opinion, as that would make it simple to have a "re-bisect" command which does n un-bisect followed by the inverse bisection

with those three commands, a user can: bisect, bisect (problem goes away), re-bisect (or inverse bisect, idk what it should be called), bisect, bisect (found problem), un-bisect, un-bisect, un-bisect, un-bisect

Things to note:

• un-bisecting the top level could either turn on all plugins (retaining history so re-bisecting goes back to the original list) or do nothing
• manually enabling/disabling plugins could either reset the history, or just add/remove that one plugin from the previous bisections

* Currently you can "disable half of enabled plugins", "enable half of disabled plugins", and "toggle all plugins" but those don't work well if I'm levels deep. I could have plugins [1,2,3,4,5,6], with [0,7,8] already disabled and 5 being the problem plugin. Disable half -> [1,2,3], problem goes away, toggle -> [0,4,5,6,7,8], disable -> [0,4,5], disable -> [0,4], problem goes away, toggle -> [1,2,3,5,6,7,8]... and that problem will repeat itself even if you use enable half instead of toggle. This is hard enough to keep track of on a small example and much harder with 50+ plugins.

Bisect, un-bisect, re-bisect replace those three commands, and also get rid of the need for "enable all plugins" as un-bisecting the top level would do the same thing. Personally I also don't think there's a need for "disable all plugins" considering you can just turn on safe mode, and I don't really understand the point of the "count" command.

Relevant Screenshot

No response

Checklist

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

@chrisgrieser I've added some UI buttons and colorization to the community plugins tab. I'll have to do some cleanup and make everything work with snippets but if you could just try out the functionality and let me know of any bugs you find it'd help

Bug Description

The new buttons added in the "Community Plugins" tab disappear after you "check for updates".

Relevant Screenshot

Initially:

Then:

To Reproduce

1. Open the "Community Plugins" tab with D&C enabled.
2. Hit "Check for Updates".
3. The new buttons added will disappear.

Obsidian Version

1.0.4

Which editor are you using?

• [X] New Editor
• [ ] Legacy Editor

Checklist

• [X] I updated to the latest version of the plugin.

followup from #2

Bisect, un-bisect, re-bisect replace those three commands, and also get rid of the need for "enable all plugins" as un-bisecting the top level would do the same thing. Personally I also don't think there's a need for "disable all plugins" considering you can just turn on safe mode, and I don't really understand the point of the "count" command.

@geoffreysflaminglasersword The purpose of disabling all instead of safe mode is that you can afterwards turn on a single plugin manually, to test things with all plugins except that one plugin disabled. Safe Mode doesn't help you here, since it turns of everything, and then recreates the previous state. that situation also makes enabling all plugins useful when you are finished.

However, with your new settings for filtering certain plugins, those two are probably obsolete and unnecessary now.

However, I think the counting of plugins should indeed be re-added. It's a minor thing, but it is useful to keep track of how many plugins are currently enabled/disabled, e.g. when you are interrupted while bisecting.

Feature Requested

Requesting a way to print currently enabled plugin list or mark plugins as safe, because you don't know which plugin you enabled is the buggy plugin?

I can disable all, enable half (and no bug) - then want to mark that half as safe plugins,

then continue on to enable half of disabled then if bug, mark that half as potential issues and only enable those - then narrow down by disabling them and switching between those

Relevant Screenshot

No response

Checklist

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

Feature Requested

Specific functions I'd like to see are:

• User can create presets that specify on/off/unchanged plugins;
• User can create a function to mass toggle user-specified plugins;
  • Mass toggle has options always toggle, toggle if on, toggle if off.

Something similar has been suggested in #2 and not implemented, but the issue was closed, so I'm bringing it up again (hope you don't mind it!).

Relevant Screenshot

No response

Checklist

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

Feature Requested

This will help you turn on the only ones that you want quicker

Relevant Screenshot

No response

Checklist

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

Bug Description

Hey, while I was debugging something, I saw that the "Toggle all snippets" command is wrongly named "Toggle all plugins" (see screenshot). :eyes: It has the correct description, so it's probably just left over from a copy/paste.

Thanks for making this plugin! It's helped me trace back some weird issues.

Relevant Screenshot

To Reproduce

1. Open command palette
2. Search for "divide conquer toggle"

Obsidian Version

0.14.6

Which editor are you using?

• [X] New Editor
• [ ] Legacy Editor

Checklist

• [X] I updated to the latest version of the plugin.

Feature Requested

Hi,

Having once again been bitten by Obsidian sometimes needing to re-open notes for changes to take effect, I wonder whether this might affect any users of this plugin?

I'm basing it on turning off the Backlinks plugin, but the backlinks not being removed - and that's a core plugin.

So I don't know if it affects any community plugins...

But just in case, I wanted to mention it here, in case it might save someone else time trying to test changes in behaviour, and their tests being invalided if they don't know the pitfall of needing to re-open notes sometimes.

Relevant Screenshot

No response

Checklist

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

On Linux, Obsidian does not hot reload css, so when bisecting css snippets, the Divide and Conquer should reload Obsidian after every command.

can be done by adding a if-condition using the Platform API form Obsidian.

Bug Description

When I run bisect, nothing happens.

I checked the console and this error appeared:

plugin:obsidian-divide-and-conquer:1297
Uncaught (in promise) TypeError: this.mode2Refresh.get(...) is not a function
at divideAndConquer.eval (plugin:obsidian-divide-and-conquer:1297:136)
eval @ plugin:obsidian-divide-and-conquer:1297

Relevant Screenshot

No response

To Reproduce

No response

Obsidian Version

1.1.8 (installer version 0.14.15)

Which editor are you using?

• [X] New Editor
• [ ] Legacy Editor

Checklist

• [X] I updated to the latest version of the plugin.

Feature Requested

I have no idea how to use this. The buttons don’t do what I expect them to do, and (on mobile) are unlabeled. Could you provide some instructions on how to use this plugin?

Relevant Screenshot

No response

Checklist

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

Bug Description

Button doesn't appear either in community plugin or CSS snippets, if Obsidian is set in another language than English.

Relevant Screenshot

To Reproduce

Note : Obsidian must be in any language different than english. For example, my bug appear in French.

1. Enable the plugin
2. Try to refresh
3. See console

Obsidian Version

1.0.3

Which editor are you using?

• [X] New Editor
• [ ] Legacy Editor

Checklist

• [X] I updated to the latest version of the plugin.