Tiny Core Base > TCB Talk

will rxvt have pseudo transparency?

<< < (2/4) > >>

jpeters:

--- Quote from: mikshaw on April 05, 2009, 08:57:29 AM ---
One thing (apart from the transparency) that I think really puts aterm over rxvt is what I think is a bug in rxvt.  It would not properly read an environment variable exported from .bash_profile unless it was launched as a login shell.  I tested this out to make sure that aterm wasn't being run as login by issuing a command from .bash_profile.  Neither term registered the command, as it should be unless run as a login shell.  However, exporting a variable from .bash_profile should affect all subsequent shells, login or not, but rxvt did not accept it until I exported that variable from one shell and then launched rxvt from the same shell.  Aterm had no trouble reading the variable.
--- End quote ---

Bash interactive login shell invokes:  (edited)

/etc/profile
~/.bash_profile
~/.bash_login
~/.profile

Non-login interactive shell invokes:

~/.bashrc

mikshaw:
Yes, that's true.  What I was getting at, though, is that if you export a variable from .bash_profile, it should be available in subshells of that login session.  When you login, .bash_profile is run, then your window manager is run, then you open rxvt.  That's all one line, starting with .bash_profile, so the variable exported from .bash_profile should still be available in rxvt, but is not (or at least was not in DSL...don't know if it's different now in TC).  If you do this in xterm or aterm, it works properly.

jpeters:
I don't think that's rxvt.....maybe it wasn't set up correctly?  Puppy uses rxvt.  It doesn't have .bash_profile, but if I add an alias to /etc/profile it works both with login and non-login newuser
shells ( 'login user' or 'su - user').   

mikshaw:
I still don't think you're following what I'm saying, but I'll need to check out the new TC to make sure I'm not wasting everyone's time.
Basically what I had a problem with in rxvt in the pre-aterm DSL was this:
1) Add export VARIABLE=value in .bash_profile (assuming bash is your shell, which in TC would require the addition of the bash extension)
2) logout and then login
3) startx if you've removed the auto-startx
4) run rxvt and echo $VARIABLE
echo $VARIABLE should still return "value", regardless of whether or not rxvt was a login shell, because the variable was exported from the same login shell that spawned the X session and subsequently rxvt.  But my experience said this doesn't work in rxvt.

jpeters:
again.....you can login or non-login repeatedly into whatever subsidiary shell you want all day,
and echo $variable still works, assuming /etc/profile works like .bash_profile (supposedly, both are read by bash).  I haven't tested the latest RC  release. (puppy is using rxvt v2.6.4)

Navigation

[0] Message Index

[#] Next page

[*] Previous page