From: "Arvid Grøtting" <arvidg@netfonds.no>
Subject: Re: Wrong default indents in message.el
Date: Thu, 09 Aug 2001 16:27:40 +0200 [thread overview]
Message-ID: <l8r8ulwboj.fsf@gorgon.netfonds.no> (raw)
In-Reply-To: <l8hevhy2a5.fsf@gorgon.netfonds.no>
"Arvid Grøtting" <arvidg@netfonds.no> writes:
> I suspect this must have been a typo:
Hmm. My fix, too, might have been a bit too quick. Although it does
make message-mode usable again[1], TAB no longer works in any
sane fashion. Oh well.
I guess setting indent-line-function is the canonical right thing to
do for a major mode, but indent-relative is just the wrong default
choice. tab-to-tab-stop or indent-relative-maybe come to mind. Any
other suggestions?
[1] it's unusable with auto-fill-mode turned on in the current CVS
version, as this message demonstrates. Yes, this footnote gets
all nice and shiny, but the main text doesn't.
--
Arvid
next prev parent reply other threads:[~2001-08-09 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 10:07 Arvid Grøtting
2001-08-09 14:27 ` Arvid Grøtting [this message]
2001-08-09 16:36 ` Kai Großjohann
2001-08-09 17:57 ` ShengHuo ZHU
2001-08-09 21:09 ` Karl Eichwalder
2001-08-09 21:55 ` Kai Großjohann
2001-08-10 4:56 ` Karl Eichwalder
2001-08-10 7:26 ` Daniel Pittman
2001-08-10 13:16 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=l8r8ulwboj.fsf@gorgon.netfonds.no \
--to=arvidg@netfonds.no \
/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 NNTP newsgroup(s).