From: hobbes@poukram.net (Rémi Letot)
To: ding@gnus.org
Subject: Re: make[1]: *** [gnus-load.el] Erreur 2
Date: Mon, 04 Oct 2010 22:43:41 +0200 [thread overview]
Message-ID: <87zkutpu2q.fsf@sphax.lybrafox.lan> (raw)
In-Reply-To: <878w2dpumx.fsf@elegiac.orebokech.com>
Romain Francoise <romain@orebokech.com> writes:
> hobbes@poukram.net (Rémi Letot) writes:
>
>> I don't set it myself, this is automatically detected by
>> configure. Maybe my emacs setup is borked by the last upgrade, I
>> don't know and I don't understand configure scripts so I can't
>> say.
>
> You ran configure inside M-x term, which sets EMACS in the shell's
> environment. There's some intelligence in configure.in to detect the
> M-x shell case (where EMACS=t), perhaps that should also detect the
> term case.
No, I ran it in an xterm, out of emacs, but indeed :
echo $EMACS
24.0.50.1 (term:0.96)
That's in a fresh xterm launched from my gnome-panel... wow...
I think I understand what happened, but I'll restart my X session and
check to see if I'm right.
> Or maybe it should use EMACS_PROG instead of EMACS.
>
> (It's amazing how people *always* think it's the snapshot's fault.)
absolutely not :-)
Lars suggested that gnus per se was not at fault, and I remembered
having seen emacs-snapshot recently in my list of upgrades, that was
just brain dumping to try to get a lead.
Thanks,
--
Rémi
next prev parent reply other threads:[~2010-10-04 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 18:53 Rémi Letot
2010-10-04 19:06 ` Lars Magne Ingebrigtsen
2010-10-04 19:23 ` Rémi Letot
2010-10-04 19:28 ` Lars Magne Ingebrigtsen
2010-10-04 19:38 ` Rémi Letot
2010-10-04 20:01 ` Adam Sjøgren
2010-10-04 20:20 ` Rémi Letot
2010-10-04 20:35 ` Adam Sjøgren
2010-10-04 20:31 ` Romain Francoise
2010-10-04 20:43 ` Rémi Letot [this message]
2010-10-04 20:57 ` Rémi Letot
2010-10-04 20:56 ` Andreas Schwab
2010-10-04 20:27 ` Ted Zlatanov
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=87zkutpu2q.fsf@sphax.lybrafox.lan \
--to=hobbes@poukram.net \
--cc=ding@gnus.org \
/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).