From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Ebuild and emacs enough is enough
Date: Sun, 05 Feb 2006 20:10:59 -0600 [thread overview]
Message-ID: <87hd7d8cek.fsf@newsguy.com> (raw)
I'm not sure where to log this complaint, its not a real bug.
I've had about 6 or 7 emerges like emerge -v -u -D world break in the
middle somewhere because emacs has been called to byte compile or
whatever, however whoever is writing this stuff is calling emacs
WITHOUT taking the normal precations used by savvy emacs users.
That is, to call emacs with `emacs -q --no-site-file CMDS'. This is
starndard practice to use when calling emacs during builds.
But on a 6-7 occassions, the last in the middle of emerge -v -u -D
--newuse world'
Not something you are likeley to set and watch for something like
this. So you come back in hour and half to find its errored out in
the middle because emacs wasn't called with simple protective flags
like -q --no-site-file.
-q (don't use an .emacs init file) --no-site-file (don't load any
site-start.el files)
People might have code in either of those places that will cause emacs
to give unexpected output during build.
site-start.el is a tradition older than gentoo.
Gentoo installs don't have it but many long term emacs users use this
file to set code for system wide stuff. That is what it is for.
Emacs will load it before anything else (except `default.el') if it is
found in the path. That is why it is wise to use --no-site-file when
calling emacs to bytecompile.
In my site-start.el I have code that causes emacs to tell me what it
is loading anytime a library or file is loaded. That output can be
quite handy when debugging things emacs, but it breaks an emerge.
So unless I realize this particular emerge will call emacs and move
site-start.el out of the path it will be loaded and break the emerge
becasue someone didn't have sense enough to call emacs the standard
way: emacs -q --no-site-file WHATEVER
Where do I need to take this complaint?
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-02-06 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 2:10 Harry Putnam [this message]
2006-02-06 5:38 ` [gentoo-user] Ebuild and emacs enough is enough Stroller
2006-02-06 5:57 ` [gentoo-user] " Francesco Talamona
2006-02-06 14:12 ` Harry Putnam
2006-02-07 6:33 ` Francesco Talamona
2006-02-06 14:23 ` Harry Putnam
2006-02-06 14:35 ` [gentoo-user] " Alexander Skwar
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=87hd7d8cek.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@lists.gentoo.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