[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacsclient with emacs-23.0.60

From: Thierry Volpiatto
Subject: Re: emacsclient with emacs-23.0.60
Date: Mon, 29 Oct 2007 11:22:48 +0100
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (gnu/linux)

Peter Dyballa <address@hidden> writes:

> 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, ...).

Thanks Peter for help,
i keep trying to see what's wrong,
checking what's different from one emacs version to the other.

A + Thierry

reply via email to

[Prev in Thread] Current Thread [Next in Thread]