From: "François Pinard" <pinard@iro.umontreal.ca>
Subject: Re: Adding MIME viewer to variable instead of .mailcap
Date: 14 Mar 2000 18:21:25 -0500 [thread overview]
Message-ID: <oqln3l5ea2.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Jonas Steverud's message of "10 Mar 2000 23:43:47 +0100"
Jonas Steverud <d4jonas@dtek.chalmers.se> écrit:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > Ah. The easiest solution seems to be to put (setenv "EMACS_RUNNING"
> > "1") in the ~/.emacs file and then test this environment variable.
> Maybe thats the easiest, but I was looking for this variable. I know it
> exists becourse someone here adviced me to use it in a discussion here
> on the list last autumn. If it does not exists anymore, then I will use
> RFC 1524, but until then... Doesn't *anyone* know if such a variable
> exists or not?
This is only mildly related to your question, but I think Emacs defines
the environment variable EMACS to `t' at least within the shell spawn
through `M-x shell'. I'm using EMACS from login to hold the path to the
Emacs executable I want, and Emacs was overriding the value with `t',
breaking some later scripts called from within Emacs. After I reported
the problem, Richard told me he was to leave the variable undisturbed if
it already existed (if I remember correctly, this was a while ago).
--
François Pinard http://www.iro.umontreal.ca/~pinard
next prev parent reply other threads:[~2000-03-14 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <wtnem9lhd4v.fsf@licia.dtek.chalmers.se>
2000-03-08 12:20 ` Peter Makholm
2000-03-08 12:56 ` Kai Großjohann
2000-03-09 13:14 ` Steinar Bang
2000-03-09 14:08 ` Kai Großjohann
[not found] ` <wtnog8m1m58.fsf@lameth.dtek.chalmers.se>
2000-03-10 23:31 ` Kai Großjohann
[not found] ` <wtnog8lg53l.fsf@licia.dtek.chalmers.se>
2000-03-11 11:25 ` Kai Großjohann
2000-03-14 23:21 ` François Pinard [this message]
2000-03-09 18:09 ` Jake Colman
2000-04-20 19:26 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=oqln3l5ea2.fsf@titan.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
/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 NNTP newsgroup(s).