From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: Please why ORDER of .emacs lines here matters.....
Date: 05 Aug 2003 04:42:45 -0400 [thread overview]
Message-ID: <7g4r0wmr5m.fsf@gnufans.net> (raw)
In-Reply-To: bf23f78f.0307312136.9385194@posting.google.com
seberino@spawar.navy.mil (Christian Seberino) writes:
> If it is better in general for some reason then I'll do it.
a hook is a nook where the normal flow looks.
a surrounding-style rewrite is a whole 'nother book.
when the Programmer friendlily documents this tether
it's better to avoid xor and instead ior together.
otherwise, setq-default is the violent last resort;
probably indicates someone should file a bug report.
thi
next prev parent reply other threads:[~2003-08-05 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 20:14 Please why ORDER of .emacs lines here matters Christian Seberino
2003-07-31 21:53 ` Kevin Rodgers
2003-08-01 5:36 ` Christian Seberino
2003-08-01 16:13 ` Kevin Rodgers
2003-08-01 20:50 ` Alan Mackenzie
2003-08-05 8:42 ` Thien-Thi Nguyen [this message]
2003-08-08 8:42 ` Alan Mackenzie
2003-08-01 20:48 ` Kai Großjohann
2003-08-10 17:43 ` Stefan Monnier
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=7g4r0wmr5m.fsf@gnufans.net \
--to=ttn@glug.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).