all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Splash screen problems
Date: Mon, 09 Apr 2007 09:00:30 +0300	[thread overview]
Message-ID: <utzvqm6ip.fsf@gnu.org> (raw)
In-Reply-To: <20070408230118.GB1395@muc.de> (message from Alan Mackenzie on 8 Apr 2007 23:41:56 +0200)

> Date: 8 Apr 2007 23:41:56 +0200
> Date: Mon, 9 Apr 2007 00:01:19 +0100
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> > What a bizarre thing to do in site-start.el!!  Why don't have mercy on
> > the other poor users of your system?
> 
> The other users are me and me.  ;-)  I don't think that's that unusual
> for users of PCs nowadays.

Then there's no real reason to have site-init.el, IMO.

> > root can have a .emacs file as well, you know.
> 
> Yes, but copying and pasting between them isn't a very good idea, because
> there are bugs even in my .emacs, my other .emacs and my third .emacs.
> So things that I want for all "users", I put in site-start.el, so that
> they only need debugging once.

Doesn't look to me like a reason not to have a .emacs for root.

> Did you look at my patches?

Yes, of course.  While I'm always for ``more documentation'', I'm not
sure this is a very good idea in this case, because there are many
other customizations that will not work in site-init.el.

  parent reply	other threads:[~2007-04-09  6:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-08 13:19 Splash screen problems Alan Mackenzie
2007-04-08 21:10 ` Eli Zaretskii
2007-04-08 21:41   ` Alan Mackenzie
2007-04-08 21:56     ` Kim F. Storm
2007-04-09  3:57       ` Stephen J. Turnbull
2007-04-08 22:14     ` Lennart Borgman (gmail)
2007-04-09  6:00     ` Eli Zaretskii [this message]
2007-04-09 15:41 ` Richard Stallman
2007-04-09 17:09   ` Alan Mackenzie

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=utzvqm6ip.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.