From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Xiao-Yong Jin <xj2106@columbia.edu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacsclient with emacs-23.0.60
Date: Mon, 29 Oct 2007 10:40:56 +0100 [thread overview]
Message-ID: <99BDC275-1B57-4F1D-A534-584E2B426F2C@Web.DE> (raw)
In-Reply-To: <871wbea9ym.fsf@columbia.edu>
Am 29.10.2007 um 04:14 schrieb Xiao-Yong Jin:
> Presumably, it's related to the handling of the environment variables?
When you work in a real X11 environment and not in GNUstep/OPENSTEP
or Mac OS X, then X11 should inherit from your login shell the whole
environment.
In most (all?) shells you can distinguish between interactive
($PROMPT present) and non-interactive ($PROMPT not present) use.
Additionally you can run shells as login shells, which makes them
read/load another resource script (~/.login etc.). So you can control
which environment variables will be valid in which situation.
Xterm can be launched with a login (-ls) and with a non-login shell
(+ls, default behaviour). See also loginShell X resource.
To compare the environment variables set: ``env | sort -o file1´´.
Then diff the files. (There are too many shells around and some, like
bash, are much too complicated in case of resource scripts.)
GNU Emacs saves the environment it inherits in the variable process-
environment (in a long unsorted list like ``"TERM=dumb"
"HOST=here.local" "GROUP=pete" "LOGNAME=pete" ...´´ in which getenv
searches). For debugging it can help when one augments the shell's RC
files (resource scripts) with statements to output messages (echo,
printf something like "Hi, it's me, RC file so-and-so starting", and
also when leaving) or to save them in files (in /tmp for example)
with unique names (using for example $$ in the resource script when
building the file name, or recent date). Anyway, it will pretty time
consuming. Another, sometimes faster option, is to use a "trace"
facility to watch a programme (or two: GNU and emacsclient) working.
The trace implementations can be set to filter particular "data
streams" (network io, disk io, dynamic/shared libraries, ...).
--
Greetings
Pete
Basic, n.:
A programming language. Related to certain social diseases in
that those who have it will not admit it in polite company.
next prev parent reply other threads:[~2007-10-29 9:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 9:43 emacsclient with emacs-23.0.60 Thierry Volpiatto
2007-10-28 10:51 ` Peter Dyballa
2007-10-28 11:27 ` Thierry Volpiatto
2007-10-28 22:53 ` Thierry Volpiatto
2007-10-28 23:31 ` Peter Dyballa
2007-10-29 3:14 ` Xiao-Yong Jin
2007-10-29 8:12 ` Thierry Volpiatto
2007-10-29 10:29 ` Peter Dyballa
2007-10-29 21:15 ` Thierry Volpiatto
2007-10-29 23:36 ` Peter Dyballa
2007-10-30 22:59 ` Thierry Volpiatto
2007-10-30 23:59 ` Peter Dyballa
2007-10-29 9:40 ` Peter Dyballa [this message]
2007-10-29 10:22 ` Thierry Volpiatto
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=99BDC275-1B57-4F1D-A534-584E2B426F2C@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=xj2106@columbia.edu \
/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).