Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
On Mon, 26 Sep 2016 22:19:27 +0100
Brian <ad44@cityscape.co.uk> wrote:
> On Sun 25 Sep 2016 at 18:55:03 +0100, Brian wrote:
>
> > The existence of ~/.xessionrc appears to cause more problems than it
> > purportedly solves.
>
> And it still won't lie down and die. It is determined to take over the
> traditional role of ~/.xsession and prove its worth. However, kudos for
> the editing of
>
> https://wiki.debian.org/Xsession
>
> to help Debian users.
[Thread fork...]
A semantic observation (probably unrelated to the aforementioned editing):
"... dot in ..." might be more clearly stated as "... source ( or '.') in ..." because the action is to source the script into the current shell (thus retaining the defined vars), as opposed to executing the script in another shell or in a subshell (thus the var definitions are lost when the shell or subshell exits).
Reply to:
- References:
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Anthony Baldwin <baldwinlinguas@gmx.com>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: David Wright <deblis@lionunicorn.co.uk>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Greg Wooledge <wooledg@eeg.ccf.org>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Tixy <tixy@yxit.co.uk>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Greg Wooledge <wooledg@eeg.ccf.org>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Darac Marjal <mailinglist@darac.org.uk>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Greg Wooledge <wooledg@eeg.ccf.org>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Brian <ad44@cityscape.co.uk>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Brian <ad44@cityscape.co.uk>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Brian <ad44@cityscape.co.uk>
- Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- From: Brian <ad44@cityscape.co.uk>
- Prev by Date:
Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- Next by Date:
Re: Building Debian Package From Upstream Source
- Previous by thread:
Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- Next by thread:
Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
- Index(es):