From 5930a6e3510f2bd052771601581aa410728d68e3 Mon Sep 17 00:00:00 2001
From: Stephen Blott
Date: Sat, 30 May 2015 06:16:24 +0100
Subject: Use the term "options" instead of "flags" for command options.

"Flags" implies binary toggles.  The term "options" seems more
consistent with what's actually going on here.
---
 content_scripts/vomnibar.coffee | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'content_scripts')

diff --git a/content_scripts/vomnibar.coffee b/content_scripts/vomnibar.coffee
index 06b546a6..4bd8e8fd 100644
--- a/content_scripts/vomnibar.coffee
+++ b/content_scripts/vomnibar.coffee
@@ -6,20 +6,20 @@ Vomnibar =
 
   # Parse any additional options from the command's registry entry.  Currently, this only includes a flag of
   # the form "keyword=X", for direct activation of a custom search engine.
-  parseRegistryEntry: (registryEntry = { extras: [] }, callback = null) ->
+  parseRegistryEntry: (registryEntry = { options: [] }, callback = null) ->
     options = {}
     searchEngines = settings.get("searchEngines") ? ""
     SearchEngines.refreshAndUse searchEngines, (engines) ->
-      for extra in registryEntry.extras
-        [ key, value ] = extra.split "="
+      for option in registryEntry.options
+        [ key, value ] = option.split "="
         switch key
           when "keyword"
             if value? and engines[value]?
               options.keyword = value
             else
-              console.log "Vimium configuration error: no such custom search engine: #{extra}."
+              console.log "Vimium configuration error: no such custom search engine: #{option}."
           else
-              console.log "Vimium configuration error: unused flag: #{extra}."
+              console.log "Vimium configuration error: unused flag: #{option}."
 
       callback? options
 
-- 
cgit v1.2.3