Fix start_application() doc about which shell is used
Patch status: merged
Patch by Tony Crisci
Long description:
Since this commit: f691a55923850a4d315450925fc98733d07b69c9 the shell that is used is the system's bourne shell (/bin/sh) and the env variable SHELL is not considered. No logic changes.
To apply this patch, use:
curl http://cr.i3wm.org/patch/695/raw.patch | git am
b/include/startup.h
| 22 |
@@ -21,8 +21,8 @@ |
| 23 |
* (immediately), the application is reparented to init (process-id 1), which |
| 24 |
* correctly handles childs, so we don’t have to do it :-). |
| 25 |
* |
| 26 |
- * The shell is determined by looking for the SHELL environment variable. If |
| 27 |
- * it does not exist, /bin/sh is used. |
| 28 |
+ * The shell used to start applications is the system's bourne shell (i.e., |
| 29 |
+ * /bin/sh). |
| 30 |
* |
| 31 |
* The no_startup_id flag determines whether a startup notification context |
| 32 |
* (and ID) should be created, which is the default and encouraged behavior. |
b/src/startup.c
| 37 |
@@ -123,8 +123,8 @@ void startup_sequence_delete(struct Startup_Sequence *sequence) {
|
| 38 |
* the application is reparented to init (process-id 1), which correctly handles |
| 39 |
* childs, so we don’t have to do it :-). |
| 40 |
* |
| 41 |
- * The shell is determined by looking for the SHELL environment variable. If it |
| 42 |
- * does not exist, /bin/sh is used. |
| 43 |
+ * The shell used to start applications is the system's bourne shell (i.e., |
| 44 |
+ * /bin/sh). |
| 45 |
* |
| 46 |
* The no_startup_id flag determines whether a startup notification context |
| 47 |
* (and ID) should be created, which is the default and encouraged behavior. |