On Thu 03 Apr 2014 at 00:19:50 +0100, Brian wrote:
The interesting aspect is that ~/.xsessionrc is sourced by Xsession
before 50x11-common_determine-startup is sourced. I'd interpret that as
having the environment set up before X starts.
As to why we have 40x11-common_xsessionrc; it started
On Wed 02 Apr 2014 at 02:16:59 +0300, Andrei POPESCU wrote:
On Ma, 01 apr 14, 20:37:40, Brian wrote:
$HOME/.bashrc is executed when you log into X. Then its contents are
sourced once agiain in your .xsessionrc. A double invocation seems a
trifle inelegant.
Could you please provide a
I'll back down on that. ~/.profile tests for $BASH_VERSION, which is
empty. Therefore $HOME/.bashrc isn't sourced through ~/.xsessionrc.
Is this because dash is the shell being used, I wonder?
echo $BASH_VERSION
4.2.37(1)-release
So it's not empty.
--
To UNSUBSCRIBE, email to
On Wed 02 Apr 2014 at 23:30:10 +0530, Anubhav Yadav wrote:
I'll back down on that. ~/.profile tests for $BASH_VERSION, which is
empty. Therefore $HOME/.bashrc isn't sourced through ~/.xsessionrc.
Is this because dash is the shell being used, I wonder?
echo $BASH_VERSION
On Mi, 02 apr 14, 17:26:04, Brian wrote:
It's possible you may want different paths on the console and in
X.
And it's also possible one might not ;)
It's something to be aware of though.
Sure, otherwise I might end with different paths on the console and in X
and I don't want
On Thu, Apr 3, 2014 at 12:03 AM, Brian a...@cityscape.co.uk wrote:
On Wed 02 Apr 2014 at 23:30:10 +0530, Anubhav Yadav wrote:
I'll back down on that. ~/.profile tests for $BASH_VERSION, which is
empty. Therefore $HOME/.bashrc isn't sourced through ~/.xsessionrc.
Is this because dash is the
On Wed 02 Apr 2014 at 22:59:18 +0300, Andrei POPESCU wrote:
As far as I know there is no canonical way, method, etc. Personally I'm
using ~/.xsessionrc to source ~/.profile because:
* the DM is not doing it
* I don't want to duplicate what ~/.profile already does
The interesting aspect
On Thu 03 Apr 2014 at 02:12:25 +0530, Anubhav Yadav wrote:
No I got no problems with your solution, I only wanted to ask you that
should I let this part:
# set PATH so it includes user's private bin if it exists
if [ -d $HOME/bin ] ; then
PATH=$HOME/bin:$PATH
fi
Still be in
Leave it. Do not delete it.
Thanks! Mission accomplished.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On Tue 01 Apr 2014 at 01:45:59 +0530, Anubhav Yadav wrote:
Lightdm also uses /etc/X11/Xsession, which does a lot more than starting
a window manager. However, it does source ~/.xsession.
I created an .xsession and the contents were as follows:
#!/bin/bash
# Set PATH
The basic problem is that lightdm in Debian hard-codes the path
https://launchpadlibrarian.net/94971962/01_set-default-path.patch
Yes now I know why this is happening. Thanks!
and there appears to be no system-wide way to alter it from within
lightdm. It doesn't matter what WM is used - a
On Tue 01 Apr 2014 at 17:53:38 +0530, Anubhav Yadav wrote:
I used my ~/.profile to export path variable. Here are the contents of
my ~/.profile:
# if running bash
if [ -n $BASH_VERSION ]; then
# include .bashrc if it exists
if [ -f $HOME/.bashrc ]; then
. $HOME/.bashrc
$HOME/.bashrc is executed when you log into X. Then its contents are
sourced once agiain in your .xsessionrc. A double invocation seems a
trifle inelegant.
# set PATH so it includes user's private bin if it exists
if [ -d $HOME/bin ] ; then
PATH=$HOME/bin:$PATH
fi
On Wed 02 Apr 2014 at 03:30:20 +0530, Anubhav Yadav wrote:
Is your entry a locale or an environment variable?
My entry is an environment variable. So you suggest that I should
It is neither. Environment variables look like this
SOMETHING=
use .xsessionrc to export my $PATH by not my
Solution No. 1: Source ~/.profile in ~/.xsessionrc.
Solution No. 2: Put 'export PATH=$HOME/bin:$PATH' in ~/.xsessionrc.
The first solution gives a path including ~/bin. It also reloads an
already loaded file, which is a waste of time, and loads other things
which may or not be wanted. It
On Ma, 01 apr 14, 20:37:40, Brian wrote:
$HOME/.bashrc is executed when you log into X. Then its contents are
sourced once agiain in your .xsessionrc. A double invocation seems a
trifle inelegant.
Could you please provide a reference for the double invocation? As far
as I remember this is
Okay, I got you.
First of all, if you want your i3wm to have the right PATH variable, you
should set it before him to run, i.e. in ~/.xsession file. Here's my
Right now I have lightdm installed. In my lightdm.conf file I have this
setting:
user-session: i3
And lightdm starts my i3.
So If I
Anubhav Yadav anubhav1...@gmail.com writes:
Okay, I got you.
First of all, if you want your i3wm to have the right PATH variable, you
should set it before him to run, i.e. in ~/.xsession file. Here's my
Right now I have lightdm installed. In my lightdm.conf file I have this
setting:
On Mon 31 Mar 2014 at 13:56:35 +0400, Dmitrii Kashin wrote:
Anubhav Yadav anubhav1...@gmail.com writes:
Right now I have lightdm installed. In my lightdm.conf file I have this
setting:
user-session: i3
And lightdm starts my i3.
So If I make a .~/.xsession will it clash with my
Lightdm also uses /etc/X11/Xsession, which does a lot more than starting
a window manager. However, it does source ~/.xsession.
I created an .xsession and the contents were as follows:
#!/bin/bash
# Set PATH
PATH=$HOME/bin:$PATH
Yet I am not able to call my i3exit script ( which I have stored
That's my configuration. I suppose it can be useful.
~/.i3/config
# power-mode
mode power {
bindsym s exec sudo /usr/sbin/pm-suspend
bindsym h exec sudo /usr/sbin/pm-hibernate
# back to normal: Enter or Escape
bindsym
On Sun, Mar 30, 2014 at 10:34 PM, Dmitrii Kashin free...@freehck.ru wrote:
That's my configuration. I suppose it can be useful.
~/.i3/config
# power-mode
mode power {
bindsym s exec sudo /usr/sbin/pm-suspend
bindsym h exec sudo
Anubhav Yadav anubhav1...@gmail.com writes:
So I think I need to setup my PATH variable properly so that it i3
can also access it?
Okay, I got you.
First of all, if you want your i3wm to have the right PATH variable, you
should set it before him to run, i.e. in ~/.xsession file. Here's my
On 03/24/2014 03:07 AM, Anubhav Yadav wrote:
I'm using i3 on debian sid i686.
Simply I use a shortchut to show the system
power dailog by i3-nagbar and use mouse to choose the button.
Beacuse of systemd, when poweroff/suspend the machine, there is no need
to enter password for a normal user.
What do you mean with systemd is only implemented completely?
As far as I can tell, systemd is available in Debian Wheezy (stable):
[ 0] MAEM ~$ apt-cache policy systemd
systemd:
Installed: (none)
Candidate: 44-11+deb7u4
Version table:
44-11+deb7u4 0
500
On 03/23/2014 02:44 PM, Anubhav Yadav wrote:
Hi, I am using debian 64 bit. I use lightdm to start i3. I am trying
to get the reboot/suspend script work from i3 control mode as follows.
I have created a script called i3exit , and placed it in ~/bin/
directory, this directory is my PATH.
[...]
Am 25.03.2014 21:43, schrieb Anubhav Yadav:
What do you mean with systemd is only implemented completely?
As far as I can tell, systemd is available in Debian Wheezy (stable):
[ 0] MAEM ~$ apt-cache policy systemd
systemd:
Installed: (none)
Candidate: 44-11+deb7u4
Version table:
δΊ Sun, 23 Mar 2014 19:14:13 +0530
Anubhav Yadav anubhav1...@gmail.com ει:
Hi, I am using debian 64 bit. I use lightdm to start i3. I am trying
to get the reboot/suspend script work from i3 control mode as follows.
I have created a script called i3exit , and placed it in ~/bin/
directory, this
I'm using i3 on debian sid i686.
Simply I use a shortchut to show the system
power dailog by i3-nagbar and use mouse to choose the button.
Beacuse of systemd, when poweroff/suspend the machine, there is no need
to enter password for a normal user.
That works for me.
Hi thanks for replying
29 matches
Mail list logo
