unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: .emacs and other config file questions
Date: Tue, 16 Nov 2010 21:13:24 -0500	[thread overview]
Message-ID: <jwv8w0siu3d.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.0.1289683517.943.help-gnu-emacs@gnu.org

> 1. "customize" versus Do It Yourself?
> =====================================
> Is there a general view as to the pros and cons of using customize
> versus just writing the lisp yourself? Although I know very little lisp,
> I'm inclined towards the latter -- primarily so I'm forced to
> learn. Customize is cool and easy and simple, but I worry it leaves me
> dependent on it. Make sense, or am I just trying to punch nails in with
> my fist when even the cool kids these days use the customize nailgun?
> Found a few items on this, including
> http://article.gmane.org/gmane.emacs.help/25218 which references
> something back in 1999 that I couldn't locate.

If you can, I recommend to write the Lisp yourself in your .emacs rather
than let Customize do it for you.  The only exception is for faces,
where doing it by hand without using Customize is rather painful and
poorly supported.

> 2. Why .gnus (and no, for example, .org)?
> ========================================
> Gnus seems unusual among the many packages in that convention seems
> to dictate we do most of its setup in .gnus, rather than in
> .emacs. Why is that?

No fundamental reason.

> Or is there some stuff that *must* go in .gnus because it makes no
> sense until Gnus is actually run? 

Not that I know, no.

> I'm running primarily on a desktop iMac, but would like to run also from
> a MacBook Pro Laptop. I have DropBox. I also have iDisk (MobileMe). And
> in the past I've used unison. Anyone care to share how they handle their
> config setup (i.e. their use of .emacs, customization, .gnus, and so on)
> where they want the same setup mirrored across multiple machines?

I use a revision control system (Bazaar in my case) to version those
files with a central repository on some Internet-connected host.
That gives you all the features you need for syncing stuff between any
number of machines.


        Stefan


      parent reply	other threads:[~2010-11-17  2:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 23:02 Bug in display-buffer Андрей Парамонов
2010-11-13  0:50 ` Drew Adams
2010-11-13 13:47   ` .emacs and other config file questions Tommy Kelly
2010-11-15 15:04     ` Deniz Dogan
2010-11-16  8:16       ` Tassilo Horn
     [not found]   ` <mailman.0.1289683517.943.help-gnu-emacs@gnu.org>
2010-11-15  4:25     ` Tim X
2010-11-17  2:13     ` Stefan Monnier [this message]

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=jwv8w0siu3d.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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).