[awesome bugs] #1105 - Replace shell instead of spawning another one when restarting

[awesome]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Victor Engmark (l0b0) 


Attached to Project - awesome
Summary - Replace shell instead of spawning another one when restarting
Task Type - Feature Request
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - Linux

Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - Based on a question posted on Stack Exchange 
:

I have a PS1 which shows the SHLVL if it's not 1 to quickly see if I'm in a 
subshell. This works as expected when using GNOME, but when I spawn a new 
terminal in Awesome (Mod4+Return) it always starts with SHLVL=2 or higher. Is 
this normal?

Looks like this is directly related to the number of times I have restarted 
Awesome (Mod4+Ctrl+r, pkill -HUP awesome). Is there some way to avoid spawning 
new shells when restarting?

Looks like it's related to 

 and 
,
 which end up running something like $SHELL -c ..., but I don't know enough C to fix it.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1105

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.

[awesome bugs] #1105 - Replace shell instead of spawning another one when restarting

[awesome]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1105 - Replace shell instead of spawning another one when restarting
User who did this - Victor Engmark (l0b0)

--
Using awesome v3.4.11 (Pickapart) on Ubuntu 12.04.
--

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1105#comment3435

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.

[awesome bugs] #1105 - Replace shell instead of spawning another one when restarting

[awesome]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1105 - Replace shell instead of spawning another one when restarting
User who did this - Uli Schlachter (psychon)

--
The SHLVL increase during restarts definitely is the pointless use of a shell 
here. However, this does not explain why SHLEVEL starts at 1. How are you 
starting awesome? Could something like your ~/.xsession cause the SHLVL 
increase?
--

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1105#comment3436

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.

[awesome bugs] #1105 - Replace shell instead of spawning another one when restarting

[awesome]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1105 - Replace shell instead of spawning another one when restarting
User who did this - Victor Engmark (l0b0)

--
I think I might have opened the first shell after restarting awesome once (I am 
just getting started with it), because after a reboot it's down to 1. Sorry for 
the confusion.
--

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1105#comment3437

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.