<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 23 Aug 2019, at 20:33, Umberto Cerrato wrote:</p>
</div>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">About the fact that these fields are more for other bundle items: you are right, those settings are quite always there, but I think they have to have a functionality. Otherwise why not removing them? (e.g. Language Grammars has different/more fields. (Although those one are always there…)).</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">We prefer to keep things general because they <em>can</em> be used, and some users do find creative ways to do things.</p>
<p dir="auto">In the case of the scope selector, this limits the scope in which the key equivalent or tab trigger has an effect.</p>
<p dir="auto">So for example in the case of themes, let’s imagine we have two themes, theme A and theme B. We could assign both of these themes a key equivalent of ⌘1 but different scope selectors, e.g. <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">source.c</code> and <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">text.html</code>.</p>
<p dir="auto">What this would allow is to press ⌘1 in a <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">source.c</code> file and switch to theme A, yet in <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">text.html</code> the same key would switch to theme B.</p>
<p dir="auto">If someone would actually find this useful, I do not know, but knowing that all bundle items can (more or less) be treated the same, I think has value in itself.</p>
</div>
</div>
</body>
</html>