Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

savannah: Environment variables in a subshell #47

Open
mc-butler opened this issue Dec 25, 2008 · 5 comments
Open

savannah: Environment variables in a subshell #47

mc-butler opened this issue Dec 25, 2008 · 5 comments
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/47
Reporter phd (@phdru)
Mentions iav@….lv

Original: http://savannah.gnu.org/bugs/?16757

Submitted by:Oleg Broytmann <phd>Submitted on:Tue 06 Jun 2006 06:43:30 AM UTC
Category:SubshellSeverity:3 - Normal
Status:NonePrivacy:Public
Assigned to:NoneOpen/Closed:Open
Release:4.6.1Operating System:GNU/Linux

Original submission:

I have a lot of different environments (Python, Java, Postgres and 
so on), and I source a config file when I want to change the 
environment; for example running "include svn" runs

. $HOME/lib/config/svn

that adds SVN directories to PATH, LD_LIBRARY_PATH and MANPATH. 
When I do this under Midnight Commander I have a minor problem with 
subshell (at least I think the problem is in the subshell). When I 
run a program in the mc command line (type "./a_script", press 
[Enter]) mc (subshell?) passes the modified env vars to the 
program. But if I just press [Enter] on the program mc passes an 
old environment as if I didn't source any config file; it seems 
after pressing [Enter] on a program mc passes its own original 
environment, not the subshell's environment. I think that's a bug; 
I'd like mc to pass the modified environment to all programs 
regardless of the way I start them.

Debian GNU/Linux 3.1, mc 4.6.1-pre3.
@mc-butler
Copy link
Author

Changed by guanx (guanx.bac@….com) on Jan 28, 2009 at 21:07 UTC (comment 1)

It's already been fixed in the 2008-08-28 version of mc shipped with Slackware Linux 12.2. However, running a program using Alt-! still uses the old environment.

@mc-butler
Copy link
Author

Changed by styx (@styx) on May 25, 2009 at 6:50 UTC (comment 2)

  • Milestone set to future releases

@mc-butler
Copy link
Author

Changed by ossi (@ossilator) on Jan 5, 2014 at 13:38 UTC (comment 1.3)

  • Branch state set to no branch

Replying to guanx:

running a program using Alt-! still uses the old environment.

that's because the filter is not run through the subshell.
i'm not sure that should be considered a bug as such, but see #3141.

@mc-butler
Copy link
Author

Changed by ossi (@ossilator) on Jan 11, 2014 at 16:43 UTC (comment 4)

  • Description edited
  • Reporter changed from slavazanko to phd

@mc-butler
Copy link
Author

Changed by iav (iav@….lv) on Feb 5, 2014 at 23:07 UTC (comment 5)

  • Cc set to iav@….lv

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress
Development

No branches or pull requests

1 participant