I just meant that it should affect actions which the Terminal plugin does not provide, so it might be ugly to have core support for it be part of the plugin. Depending on how powerful QS's plugins are that may not be an issue, and I certainly agree that from a UI standpoint having it sectioned off with the other Terminal stuff is probably a good idea.
Honestly I feel like it would ultimately make sense to split the plugin in two, with "Scripting Support" or something being analogous to the "Email Support" plugin, and then the Terminal (and iTerm) plugins only providing the actions and functionality that specifically interact with those applications. It seems in one sense silly to have to have the Terminal plugin installed when I only use iTerm. But that's another story. On Wednesday, April 9, 2014 10:45:39 AM UTC-4, Rob McBroom wrote: > > On 8 Apr 2014, at 22:47, Daniel wrote: > > > Not sure it's specific to the Terminal plugin, though, as detailed in > > the issue. > > Maybe not, but if you’re the sort of person that knows what > environment variables are and wants to customize them, you’re probably > the sort of person that has the Terminal plug-in installed. :-) > > And that lets us keep the main prefs a little cleaner for everyone else. > > -- > Rob McBroom > http://www.skurfer.com/ > -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/d/optout.
