unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dan Anderson <dan@mathjunkies.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Cool and Useful LISP for the .emacs file
Date: Fri, 07 Nov 2003 11:54:55 -0500	[thread overview]
Message-ID: <1068224095.24924.9.camel@hades.syr-24-59-76-83.twcny.rr.com> (raw)
In-Reply-To: <e867ce6d.0311070327.4cd5decc@posting.google.com>

> Here's my cool tip:
> 
>    Delete your .emacs!
> 
> This means that you can go to a new machine, run Emacs on it, and it
> works just the same as on your old machine!  No more confusion over
> non-default keybindings, unusual settings for variables, bizarre mode
> hooks, etc.  And when you find a problem you know it's really to do with
> Emacs and not with some "cool" trick you copied out of someone else's
> .emacs without understanding it.

	Start emacs with -q when you have a problem.  It sets it to default
mode.  If you can only reproduce the problem when using your .emacs you
can go about debugging your .emacs file.  

	Of course, some people are probably saying "but debugging LISP is
hard!"  Well, fear not.  Remove the last thing you inserted.  It's
probably what's causing the screw up.  (Or restore the backup you made
of your .emacs from the last time you edited it.  Didn't make one?  Try
loading ~/.emacs~)

	I'd also like to point out that many of us who use Emacs and customize
it until we couldn't think of another feature to code use Emacs for
coding.  Learning LISP is not hard and we are certainly qualified to
make changes to the .emacs

	I'd also like to point out that your site administrator probably has
created a site lisp file similar to the .emacs to customize emacs for
your company or organization.  That or you've never needed to install a
single .el file.  (Come on, not everything is stock).

	Plus, if you've ever changed anything in Emacs and hit the save button
you probably /have/ created machine generated in your .emacs to save
your settings.  

-Dan

  parent reply	other threads:[~2003-11-07 16:54 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3343.1068146343.21628.help-gnu-emacs@gnu.org>
2003-11-06 23:45 ` Cool and Useful LISP for the .emacs file Kevin Rodgers
2003-11-07  4:10 ` Bruce Ingalls
2003-11-07  9:08 ` roodwriter
2003-11-07 16:58   ` Kevin Rodgers
2003-11-07 18:35     ` roodwriter
2003-11-08 18:01   ` roodwriter
2003-11-11 10:48     ` Oliver Scholz
2003-11-07 11:27 ` Gareth Rees
2003-11-07 14:06   ` Adam Hardy
     [not found]   ` <mailman.3403.1068214062.21628.help-gnu-emacs@gnu.org>
2003-11-07 14:28     ` David Kastrup
2003-11-07 16:54   ` Dan Anderson [this message]
2003-11-07 17:19   ` Rob Thorpe
     [not found]   ` <mailman.0.1068227823.2005.help-gnu-emacs@gnu.org>
2003-11-07 17:45     ` Jody M. Klymak
2003-11-07 18:20       ` Kevin Rodgers
2003-11-07 19:37       ` Dan Anderson
     [not found]       ` <mailman.11.1068237562.2005.help-gnu-emacs@gnu.org>
2003-11-07 22:17         ` Jody M. Klymak
2003-11-08  1:22           ` Jesper Harder
2003-11-08  3:23           ` Kin Cho
2003-11-08 10:34             ` Artur Hefczyc
2003-11-08 13:20               ` Thien-Thi Nguyen
2003-11-08 20:06               ` David Kastrup
2003-11-08 21:45                 ` Artur Hefczyc
2003-11-08 22:02                   ` Artur Hefczyc
2003-11-09  3:20               ` Kin Cho
2003-11-12  5:15               ` David Masterson
2003-11-12  8:12                 ` Matthew Kennedy
2003-11-12 18:21                 ` Pascal Bourguignon
2003-11-13 19:54                   ` Artur Hefczyc
2003-11-23  8:08               ` Tim X
2003-11-08 23:15           ` Joe Fineman
2003-11-10 15:59           ` Stefan Monnier
2003-11-10 20:58             ` Thien-Thi Nguyen
2003-11-10 21:00             ` Burton Samograd
2003-11-11 10:34               ` Alan Mackenzie
2003-11-11 14:32                 ` Jesper Harder
2003-11-11 17:00                   ` Burton Samograd
2003-11-11 17:00                 ` Burton Samograd
2003-11-11 20:04                   ` Alan Mackenzie
2003-11-08 10:15         ` Oliver Scholz
2003-11-08 12:03           ` Orm Finnendahl
2003-11-08  1:28       ` Thien-Thi Nguyen
2003-11-08 14:09       ` Ole Laursen
2003-11-23  8:02       ` Tim X
2003-12-07 15:56       ` Kai Grossjohann
2003-11-07 18:09 ` Reiner Steib
2003-11-07 18:37   ` lawrence mitchell
2003-11-08 17:06     ` Reiner Steib
2003-11-07 23:41 ` Edward Dodge
2003-11-10 16:04   ` Stefan Monnier
2003-11-10 21:17     ` kgold
2003-11-11 10:43       ` Alan Mackenzie
2003-11-11 15:39         ` Eli Zaretskii
2003-11-11 15:52         ` Stefan Monnier
2003-11-11 17:35           ` Thien-Thi Nguyen
2003-11-12  7:25             ` Lars Brinkhoff
     [not found]             ` <mailman.197.1068625639.2005.help-gnu-emacs@gnu.org>
2003-11-12 10:22               ` Colin Marquardt
2003-11-12 11:15                 ` David Kastrup
2003-11-12 13:47                   ` Stefan Monnier
     [not found] <E1AIRNX-0002YI-H9@monty-python.gnu.org>
2003-11-08 22:01 ` Joe Corneli
     [not found] <E1AI57v-00032q-9p@monty-python.gnu.org>
2003-11-07 14:31 ` Joe Corneli
2003-11-06 19:18 Dan Anderson

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=1068224095.24924.9.camel@hades.syr-24-59-76-83.twcny.rr.com \
    --to=dan@mathjunkies.com \
    --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).