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 Thu 22 Sep 2016 at 16:10:01 +0100, Darac Marjal wrote:
> On Thu, Sep 22, 2016 at 10:56:49AM -0400, Greg Wooledge wrote:
> >On Thu, Sep 22, 2016 at 03:15:40PM +0100, Tixy wrote:
> >>I edit ~/.xsessionrc to have a single line:
> >>
> >> . /home/tixy/.profile
> >
> >Which program reads ~/.xsessionrc and how did you learn about it?
> >Which man page describes it? Does its existence merely "add on" to some
> >system-wide default script, or does it fully replace a system-wide script?
>
> Apparently, this is the "New Method" as detailed in the Debian Reference
> Manual: https://www.debian.org/doc/manuals/debian-reference/ch07.en.html#_customizing_the_x_session_new_method
"Customizing the X session (new method)" should be seen as describing
additional customisation features rather than a hint to do without
~/.xsession. The intention of ~/.xsessionrc is to source environment
variables but it can be (ab)used for other purposes.
For example, it could start a terminal:
gnome-terminal &
The advantage over ~/.xsession is that the window manager or desktop
session would be started from the alternatives system whereas
~/.xsession also has to start a window manager or desktop session. You
would have to have
gnome-terminal &
exec gnome-session
--
Brian.
Reply to:
- References:
- 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: Tony Baldwin <tonybaldwin@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: 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: Tony Baldwin <tonybaldwin@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: 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: 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>