Leon Fischer writes:
> If you run xrdb(1) then ~/.Xdefaults won't be evaluated.
Well that's interesting and good to know, thanks! That doesn't seem
obvious from looking at mentions of "Xdefaults" in either the X(7) or
xrdb(1) man pages, unless it's implied in this from xdrb(1):
Xrdb does
> Date: Tue, 27 Apr 2021 14:54:48 -0400
> From: Allan Streib
>
> Stuart Henderson writes:
>
> > Seems that your terminal in X is not configured to run a login shell.
> > By default that is done for xterm via .Xdefaults in a new user's profile
> > directory (copied from /etc/skel) but if you use
On Wed, 2021-04-28 at 06:20 +, David Dahlberg wrote:
> I noticed the effect that the OP described ($PWD and $HOME/.profile
> being ignored) too
After some testing of different WM/DE (Xenodm to FVWM, CWM, Xfce,
Lumina, Mate) and terminal emulators, I have to conclude, that the
effect seems to
Hi David,
On Wed, Apr 28, 2021 at 07:09:09AM +, David Dahlberg wrote:
> On Wed, 2021-04-28 at 06:20 +, David Dahlberg wrote:
> > I noticed the effect that the OP described ($PWD and $HOME/.profile
> > being ignored) too
>
> After some testing of different WM/DE (Xenodm to FVWM, CWM,
On Tue, 2021-04-27 at 09:37 +0200, Alexandre Ratchov wrote:
> If you're using a display manager (xenodm or whatever), you've to
> include your .profile in your session login script (X equivalent of
> shell's ~/.profile concept), so the envoronment (and other global
> login settings) from your
Stuart Henderson writes:
> Seems that your terminal in X is not configured to run a login shell.
> By default that is done for xterm via .Xdefaults in a new user's profile
> directory (copied from /etc/skel) but if you use a different terminal
> or have modified these files, that won't be used.
On Tue, Apr 27, 2021 at 09:37:05AM +0200, Alexandre Ratchov wrote:
If you're using a display manager (xenodm or whatever), you've to
include your .profile in your session login script (X equivalent of
shell's ~/.profile concept), so the envoronment (and other global
login settings) from your
On Tue, Apr 27, 2021 at 08:04:32AM +0300, Pierre-Philipp Braun wrote:
Could also just source your profile in your .xsession. That's what I'm in the
habit of doing.
I believe there's no need for neither login-shells nor those X-level
tricks. To load the interactive environment into xterms or
On Mon, Apr 26, 2021 at 05:46:14PM -0400, Allan Streib wrote:
"tetrahe...@danwin1210.me" writes:
It looks like the custom $PATH is not being passed from the login shell
on downwards, since ~/.profile is only read by a login shell.
I just was looking into the same thing last night. The ksh
On Tue, Apr 27, 2021 at 12:17:55PM +, tetrahe...@danwin1210.me wrote:
> On Tue, Apr 27, 2021 at 08:04:32AM +0300, Pierre-Philipp Braun wrote:
> > I believe there's no need for neither login-shells nor those X-level
> > tricks. To load the interactive environment into xterms or screen, I
> >
On Tue, Apr 27, 2021 at 12:19:36PM +, tetrahe...@danwin1210.me wrote:
> On Tue, Apr 27, 2021 at 09:37:05AM +0200, Alexandre Ratchov wrote:
> > If you're using a display manager (xenodm or whatever), you've to
> > include your .profile in your session login script (X equivalent of
> > shell's
On 2021-04-26, tetrahe...@danwin1210.me wrote:
> I have some custom additions to my $PATH. They're defined in ~/.profile
> and they are correctly loaded when I log in from a text console.
>
> When I log in to X (cwm) and open a terminal window, $PATH does not
> contain the entries.
>
> I tried
On Mon, Apr 26, 2021 at 09:26:19PM +, tetrahe...@danwin1210.me wrote:
> I have some custom additions to my $PATH. They're defined in ~/.profile and
> they are correctly loaded when I log in from a text console.
>
> When I log in to X (cwm) and open a terminal window, $PATH does not contain
>
Could also just source your profile in your .xsession. That's what I'm in the
habit of doing.
I believe there's no need for neither login-shells nor those X-level
tricks. To load the interactive environment into xterms or screen, I
usually to define ENV accordingly in /etc/profile or
On Mon, Apr 26, 2021 at 11:31:33PM +0200, Jan Vlach wrote:
>
> Hi,
>
> you need:
>
> xterm*loginShell: true
>
> in ~/.xresources and something like xrdb ~/.Xresources in ~/.xsession
>
> JV
>
> On Mon, Apr 26, 2021 at 09:26:19PM +, tetrahe...@danwin1210.me wrote:
> > I have some custom
"tetrahe...@danwin1210.me" writes:
> It looks like the custom $PATH is not being passed from the login shell
> on downwards, since ~/.profile is only read by a login shell.
I just was looking into the same thing last night. The ksh shell in the
xterm didn't seem to be processing my .profile.
Hi,
you need:
xterm*loginShell: true
in ~/.xresources and something like xrdb ~/.Xresources in ~/.xsession
JV
On Mon, Apr 26, 2021 at 09:26:19PM +, tetrahe...@danwin1210.me wrote:
> I have some custom additions to my $PATH. They're defined in ~/.profile and
> they are correctly loaded
17 matches
Mail list logo
