unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: gebser@ameritech.net
Cc: help-gnu-emacs@gnu.org
Subject: Re: Formatting Code
Date: Wed, 29 Jan 2003 19:51:35 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0301291940020.18426-100000@heidegger.mousecar.net> (raw)
In-Reply-To: <uvg07bidl.fsf@XXnetscape.net>


Another track:

Matt at 00:17 (UTC-0000) on Thu, 30 Jan 2003 said:

= Glenn Hancock <ghancock@localhost.localdomain> writes:
= 
= > I have been trying to figure out how  to get emacs to format my code the way 
= > I want it and now have it so screwed up it doesn't act right at all.  How 
= > do I reset it back to defaults to start over?
= 
= You can set everything back to defaults by wiping out your .emacs
= file. If you were using customize, you can click `Erase Customization'.

You could also rename your .emacs and .emacs~ files so as to get them 
back later if needed.

= 
= > Is this typical of using Emacs?  I want to program not spend all day 
= > learning an IDE.  Anyone have any tips to get me going quicker?
= 
= What type of code are you writing? Are you using a certain major mode?
= If not, you should. Have you tried customizing the settings for that
= particular mode? - i.e., for Perl mode try M-x customize-group RET
= perl RET

It's fairly easy to edit a lot of the formatting done by elisp.  I've
done a lot in about a half hour and know very little about elisp.  You 
can ask anyone here about that.  :)


= 
= If you want quick, my advice is just get used to it the way it is.

If it's about customizing key combos (aka chords... whatever), I'd 
agree.  But it's much more important to have your documents formatted 
the way you want.  That's what an editor's for.  It'd be a major pain in 
the patoot to have to go back and reformat them later when you finally 
figure out how.

Glenn, you should give us more specifics about what kind of file you're 
editing (shell or perl script, C code, html, etc.) and what style of 
formatting you want.  Your question is a little vague.  Vague questions 
get vague answers (at best).


hth,
ken


= 
= > Thanks,
= > 
= > 
= > Glenn.
= > 
= > P.S.  I have already read the entire tutorial but it doesn't cover 
= > formatting code issues...
= > 
= 
= There's also a Manual. I'm fairly new to emacs, but the time I've
= invested learning it has been well worth the effort.
= 
= Matt
= 

  reply	other threads:[~2003-01-30  0:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29  8:28 Formatting Code Glenn Hancock
2003-01-30  0:17 ` Matt
2003-01-30  0:51   ` gebser [this message]
2003-01-31  8:07     ` Lee Sau Dan
2003-01-31 11:06       ` gebser
     [not found]       ` <mailman.1235.1044011258.21513.help-gnu-emacs@gnu.org>
2003-02-03  7:49         ` Lee Sau Dan
2003-02-03 12:47           ` Kai Großjohann
2003-01-30  8:20 ` Kai Großjohann

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=Pine.LNX.4.44.0301291940020.18426-100000@heidegger.mousecar.net \
    --to=gebser@ameritech.net \
    --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).