From e586c7ff11c9e7a6f8dc9614e307d165c5ceb35d Mon Sep 17 00:00:00 2001
From: Jekyll Wu <adaptee@gmail.com>
Date: Sun, 23 Oct 2011 14:41:06 +0800
Subject: [PATCH] Add explanation on how the -e option works in konsole.

Konsole treats all arguments after the -e option as one commnd
and runs it directly, instead of parsing it and dividing it into
sub-commands for execution. This is different from xterm.

CCBUG:170867
---
 doc/manual/index.docbook | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/manual/index.docbook b/doc/manual/index.docbook
index 87bd6e43..587f4169 100644
--- a/doc/manual/index.docbook
+++ b/doc/manual/index.docbook
@@ -1091,6 +1091,25 @@ In KDE3, each tab had its own process ID.  However, in KDE4, all the tabs use th
 This is most noticeable when a command that connects to an external device or system (ssh, nfs) has issues.
 </para></listitem>
 
+<listitem><para>
+&konsole; treats arguments after the <option>-e</option> option as one command and runs it directly, instead  of parsing it and possibly dividing it into sub-commands for execution. This is different from xterm.
+</para>
+
+<para>
+    <itemizedlist mark='opencircle'>
+
+    <listitem><para>
+<command>konsole -e "command1 ; command2"</command> does not work
+    </para></listitem>
+
+    <listitem><para>
+<command>konsole -e $SHELL -c "command1 ; command2"</command> works
+    </para></listitem>
+
+    </itemizedlist>
+</para>
+</listitem>
+
 </itemizedlist>
 
 </sect1>