tkil-sdpm at scrye.com
Wed Jan 23 16:04:45 CST 2002
[Sorry if anyone gets this multiple times, I'm having issues with
>>>>> "Anthony" == Anthony Kilna <anthony at zoovy.com> writes:
Anthony> I forget the name of the emacs guru present at the meeting on
Hm. I'm not sure I qualify as an emacs "guru", but it was probably
Anthony> I'm still interested in any links to (or commands I can run)
Anthony> to get more info on how to use emacs in general (with an
Anthony> emphasis on cheat-sheets and mnemonics)
There's always the tutorial, which is a big help (C-h t). There's the
info file(s), available under C-h i. As for "cheat sheet", I would
imagine that there's an O'Reilly book with a tear-out quick ref
sheet. There' probably also some quick-reference sheets just lying
around on the web.
(Finally, for those who just want a dump of all commands that are
readily available, you can do "C-h b" to describe all the "bindings"
currently in effect. You can also use "apropos" to look up commands
Anthony> and specifically how to specify new syntax highlighting.
If you rummage around in:
You can take a look at two different files that implement syntax
highlighting with varying degrees of grace and success:
Those should be enough to get you started. As I mentioned at the
meeting, you can also get lots of information from the built-in
documentation on "font-lock-keywords", available by typing:
C-h v font-lock-keywords
in your default configuration. (If you have backspace issues with
control+h, you can also do:
ESC x describe-variable RET font-lock-keywords RET
I mostly use this in cperl-mode, where Ilya "helpfully" overrode
standard bindings. Sigh.)
Anthony> Also, I'm interested in changing some behaviors that I find
Anthony> frustrating (line wrapping with the \ at the end, for
Which issue are you referring to? When you're typing new text, if it
doesn't wrap, you need to turn on "auto-fill-mode". When you're
viewing existing text (e.g., a nice wide log file output), you can
have emacs either wrap the text (the default), or have it "truncate"
the lines (by setting the variable "truncate-lines" to "t"). If you
get the horizontal scroll bar, that's great; otherwise, you need to
use "C-x >" and "C-x <" to move left or right.
Anthony> the tendency for it to use spaces instead of tabs for
Take a look at the variable "indent-tabs-mode":
| `indent-tabs-mode' is a built-in boolean variable.
| Value: nil
| This value is specific to the current buffer.
| *Indentation can insert tabs if this is non-nil.
| Setting this variable automatically makes it local to the current buffer.
That last blurb at the bottom means that, if you want to use tabs
whenever possible, you have to do something a bit fancy in your
(setq-default indent-tabs-mode t)
(Normally, you can just use "setq"; since that makes the value change
only in that buffer, it means that your .emacs buffer has that change,
but everywhere else that variable is still "nil".)
Added in this version of the e-mail: Here's a link to a nice roundup
of the arguments for and against tabs vs. spaces, as well as some
emacs-lisp configuration bits for controlling it.
The posting address is: san-diego-pm-list at hfb.pm.org
List requests should be sent to: majordomo at hfb.pm.org
If you ever want to remove yourself from this mailing list,
you can send mail to <majordomo at happyfunball.pm.org> with the following
command in the body of your email message:
If you ever need to get in contact with the owner of the list,
(if you have trouble unsubscribing, or have questions about the
list itself) send email to <owner-san-diego-pm-list at happyfunball.pm.org> .
This is the general rule for most mailing lists when you need
to contact a human.
More information about the San-Diego-pm