--*path can be confusing when adding a single plugin, since it may be understood to represent the path to the plugin itself vs to the folder containing the plugin. On the other hand, I like the analogy to PATH variable, and we discussed earlier the equivalent compiler arguments (say -I for gcc) and those are also referred to as "search path". Naming is hard, lets go shopping?
On Wed, Jan 8, 2014 at 8:21 PM, Josh Soref <[email protected]> wrote: > --path > --pluginpath > > I'd probably pick the former. The latter avoids the spelling error but > does nothing to help people's fingers. > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from > your system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. >
