unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: winows emacs - portable app
Date: Wed, 19 Apr 2006 20:47:42 +0300	[thread overview]
Message-ID: <uu08pwj7l.fsf@gnu.org> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICEEPJDEAA.drew.adams@oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Wed, 19 Apr 2006 08:08:36 -0700
> 
>     > M-x load-file
> 
>     But note that this will not always have the same effect as loading
>     .emacs as an init file, because Emacs loads the init file half way
>     through its startup procedure, precisely in time to customize certain
>     aspects of the appearance before they are set to default.  For
>     example, if your .emacs is setting parameters of the initial frame,
>     those settings will not work if you load .emacs after startup.
> 
> I'm not an expert here, and I don't know how you happen to launch Emacs, but
> if you do it from (the equivalent of) a command line, and you use the "-l"
> option to load a file, then the same processing that Eli described for
> .emacs will take place for that file. At least that's what I find wrt the
> initial frame, standalone minibuffer frame etc.

Loading .emacs from the command line is similar, but not identical to
loading it automatically from the user's home directory.  For example,
the after-init-hook is run _before_ any files mentioned on the command
line are loaded.

  reply	other threads:[~2006-04-19 17:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.554.1145413305.9609.help-gnu-emacs@gnu.org>
2006-04-19  6:17 ` winows emacs - portable app Jason Rumney
2006-04-19  8:31   ` Eli Zaretskii
2006-04-19 15:08     ` Drew Adams
2006-04-19 17:47       ` Eli Zaretskii [this message]
2006-04-19 17:47 Ryan Moszynski
2006-04-19 17:58 ` Eli Zaretskii
2006-04-19 20:48 ` Rasmus Pank Roulund
  -- strict thread matches above, loose matches on Subject: below --
2006-04-19 12:10 Ryan Moszynski
2006-04-19 16:27 ` Kevin Rodgers
2006-04-19 17:32 ` Eli Zaretskii
2006-04-19  2:21 Ryan Moszynski

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uu08pwj7l.fsf@gnu.org \
    --to=eliz@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).