properly interpret initial_command as cmdsequence

This ensures the default initial command as given by the
`initial_command` config option will be interpreted as
command*line* as expected, and not as single command.
As a result, one can now use e.g.
  initial_command = search A ; search B

issue: #698

1 files changed, 4 insertions, 4 deletions

diff --git a/alot/ui.py b/alot/ui.py
index cc578725..e9624e54 100644
--- a/alot/ui.py
+++ b/alot/ui.py
@@ -24,11 +24,11 @@ class UI(object):
     responsible for opening, closing and focussing buffers.
     """
 
-    def __init__(self, dbman, initialcmd):
+    def __init__(self, dbman, initialcmdline):
         """
         :param dbman: :class:`~alot.db.DBManager`
-        :param initialcmd: commandline applied after setting up interface
-        :type initialcmd: str
+        :param initialcmdline: commandline applied after setting up interface
+        :type initialcmdline: str
         :param colourmode: determines which theme to chose
         :type colourmode: int in [1,16,256]
         """
@@ -81,7 +81,7 @@ class UI(object):
         self.mainloop.screen.set_terminal_properties(colors=colourmode)
 
         logging.debug('fire first command')
-        self.apply_command(initialcmd)
+        self.apply_commandline(initialcmdline)
 
         # start urwids mainloop
         self.mainloop.run()