all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Le Wang" <l26wang@gmail.com>
Subject: Re: configuring emacs as a programmer's editor
Date: 30 Jun 2006 01:02:40 -0700	[thread overview]
Message-ID: <1151654560.583352.48720@x69g2000cwx.googlegroups.com> (raw)
In-Reply-To: <e82idl$gio$1@online.de>


Andreas Roehler wrote:
> Ted wrote:
>
>
> Probably you will or should use two different init
> files: If you are in windows the .emacs from Linux will
> not be known there. Also the windows Emacs is a
> different machine as such AFAIU.
>
> (Basically its possible the have a combined init file at
> the windows part and read it in from Linux, but that
> will complicate the task.)

No.  Emacs does a good job of providing the glue that makes it OS
agnostic.  See Google groups to address specific problems you come
across.  There is no reason to maintain two init files.  Worst comes to
worst:

(if (string-match "win" (prin1-to-string system-type))
    ;; windows form
  ;; unix forms
)


<snip>

> What's with the auto-mode-alist.
>
> Usually it's defined by files.el and
> should be OK. Are there reasons to redefine it?

No.  This is a bad BAD idea.

--
Le

  reply	other threads:[~2006-06-30  8:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-30  0:38 configuring emacs as a programmer's editor Ted
2006-06-30  7:03 ` David Kastrup
2006-06-30  7:04 ` Andreas Roehler
2006-06-30  8:02   ` Le Wang [this message]
2006-06-30 12:13     ` Eli Zaretskii
     [not found]     ` <mailman.3562.1151669638.9609.help-gnu-emacs@gnu.org>
2006-07-01  4:20       ` Le Wang
2006-06-30  7:37 ` Le Wang
2006-06-30 16:14   ` Ted
2006-07-01 23:19     ` Le Wang
2006-07-02  3:46     ` B. T. Raven
2006-07-02  8:32       ` Tim X
2006-07-03 20:15     ` Ted
2006-07-04  8:34       ` Tim X
2006-07-03 22:09 ` Jason Rumney

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=1151654560.583352.48720@x69g2000cwx.googlegroups.com \
    --to=l26wang@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.