Web Clipper Default Interpreter per Template

Feature archive
1

Use case or problem

I’ve updated to the newest Web Clipper version (0.10.1), and re-inserted my keys.
I was hoping that the next version of Web Clipper will allow us to set the default interpreter used within each template. That way, we could turn on the “Automatically Run” behavior, since the template had loaded the interpreter of choice.

For example, I have 2 Web clippings templates, each that works best with a different interpreter.

Proposed solution

Add a new “default interpreter” option in a single Template’s setting.
This new setting would looks similar to the Vault chooser, it could have a “Last Used”, and then it could list all the available interpreters added from the Interpreter options page.

Current workaround (optional)

  1. Turning off “Automatically run” for the Interpreter behavior.
  2. Choosing the interpreter for each template that has an interpreter.
  3. Interpret

Related feature requests (optional)

2

Issues and feature requests for the clipper go on the GitHub page:

Thanks.

1 Like
3

Alright, I moved it over there.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.