From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: envvars not being inherited everywhere
Date: Fri, 20 Jun 2003 08:59:21 +0200 [thread overview]
Message-ID: <84r85p2q0m.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: mailman.8291.1056060536.21513.help-gnu-emacs@gnu.org
Arnaud Vandyck <arnaud.vandyck@ulg.ac.be> writes:
> Maybe help me to describe the problem with enough precision. I like the
> way Stefan points it:
I would say something like the following:
I put "export CVS_RSH=ssh" into the file ~/.foo. Then I log in
via kdm/gdm/xdm and start a shell. Typing "echo $CVS_RSH" into
that shell gives me ssh. Good. I invoke Emacs from that shell.
Typing M-: (getenv "CVS_RSH") RET into that Emacs gives me ssh.
Good. I invoke Emacs from the menu. Now typing M-: (getenv
"CVS_RSH") RET gives me nil. Bad.
--
This line is not blank.
parent reply other threads:[~2003-06-20 6:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.8291.1056060536.21513.help-gnu-emacs@gnu.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84r85p2q0m.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).