all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Milliken <peter.milliken@gmail.com>
To: Jason Rumney <jasonrumney@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs 23.1.1 Windoze doesn't locate/run site-lisp.el/default.el anymore (bug??)
Date: Tue, 4 Aug 2009 14:14:50 +1000	[thread overview]
Message-ID: <791153ba0908032114n291e0627o130019a2d9775e60@mail.gmail.com> (raw)
In-Reply-To: <ce6b3a17-7ee3-4670-80a9-7a3dc95b91c3@x5g2000prf.googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

It was the pretest emacs (the very last one before the official release I
believe) - which is when I was first faced with the tool-bar sticking me in
the face. So I read up on how to get rid of it and was forced to put the
code in site-start.el - which I naturally put in the same directory as my
.emacs - not reading the manual carefully enough to realise it should not
find it there - but it did.
So I guess something changed since the last pretest and the official release
- because it was certainly working from ~! :-)

I may abandon using the Windows release of Emacs though as the road seems to
be for more and more Windows/mouse interaction being built in as "default".
It is annoying having to research how to turn the stuff off. I think I'll
have a closer look at the cygwin Emacs distrib.

Thanks anyway
Peter

On Tue, Aug 4, 2009 at 11:55 AM, Jason Rumney <jasonrumney@gmail.com> wrote:

> On Aug 3, 6:50 am, Peter Milliken <peter.milli...@gmail.com> wrote:
> > Just loaded Emacs 23.1.1 for Windoze and now my site-lisp.el file
> nolonger
> > seems to run.
>
> > Just for the hell of it, I copied the default.el into c:/emacs/site-lisp
> -
> > and Emacs appears to run it from that location - which is NOT where I
> want
> > my personal customisations to reside!
> >
> > Nothing else has changed i.e. my HOME directory prior to starting Emacs
> is
> > still pointing to where the site-start.el/default.el files are located.
>
> Emacs has never automatically run site-lisp.el and default.el files
> from the HOME directory,  unless your HOME directory happens to be
> called site-lisp and is in the parent directory of your previous Emacs
> installation, I don't see how this could have worked without
> customizations in .emacs
>

[-- Attachment #2: Type: text/html, Size: 2250 bytes --]

  reply	other threads:[~2009-08-04  4:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3722.1249253431.2239.help-gnu-emacs@gnu.org>
2009-08-04  0:24 ` Emacs 23.1.1 Windoze doesn't locate/run site-lisp.el/default.el anymore (bug??) Xah Lee
2009-08-04  1:55 ` Jason Rumney
2009-08-04  4:14   ` Peter Milliken [this message]
2009-08-04  4:23     ` Lennart Borgman
     [not found]   ` <mailman.3816.1249359299.2239.help-gnu-emacs@gnu.org>
2009-08-05  3:39     ` B. T. Raven
2009-08-02 22:50 Peter Milliken

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=791153ba0908032114n291e0627o130019a2d9775e60@mail.gmail.com \
    --to=peter.milliken@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jasonrumney@gmail.com \
    /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.