From: Miles Bader <miles.bader@necel.com>
Cc: Klaus Zeitler <kzeitler@lucent.com>, emacs-devel@gnu.org
Subject: Re: indent-tabs-mode
Date: Thu, 10 Aug 2006 14:27:03 +0900 [thread overview]
Message-ID: <buoy7tx9n4o.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <u8xlxes8y.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Aug 2006 20:25:17 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Right. So, if we are to change anything in the related defaults (and
> I'm not saying that we necessarily should), at most we should reset
> indent-tabs-mode to nil when the user customizes tab-width to a
> non-default value.
I think that would be a bad idea too.
The most common use of tab-widths other than 8 that I know of is by vi
users.
As far as I understand the typical vi practice, typically they:
(1) Use _only_ tabs for indenting, e.g. C code.
(2) Set their tab-width to be their preferred "level offset" (the amount
by which e.g. C statements are indented relative to the beginning
brace of their enclosing block).
The claimed advantage of this is that someone who likes a different
"level offset" can easily just change their tab-width and all the C code
they view instantly changes (assuming that all the code they view
follows this convention of course :-).
In Emacs, you can easily use this convention by simply making sure
tab-width and c-basic-offset are the same. If you do this, c-mode
always insert tabs for indentation, one per level of indentation.
C-mode doesn't have to do anything special for this to work, it just
naturally falls out of the way Emacs indentation primitives work.
But of course it only does the right thing if indent-tabs-mode is t.
-Miles
--
`Suppose Korea goes to the World Cup final against Japan and wins,' Moon said.
`All the past could be forgiven.' [NYT]
next prev parent reply other threads:[~2006-08-10 5:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 0:19 indent-tabs-mode Nick Roberts
2006-08-09 0:34 ` indent-tabs-mode Giorgos Keramidas
2006-08-09 2:40 ` indent-tabs-mode Miles Bader
2006-08-09 3:45 ` indent-tabs-mode Nick Roberts
2006-08-09 4:58 ` indent-tabs-mode Miles Bader
2006-08-09 5:11 ` indent-tabs-mode Nick Roberts
2006-08-09 5:34 ` indent-tabs-mode Miles Bader
2006-08-09 6:13 ` indent-tabs-mode Nick Roberts
2006-08-09 7:13 ` indent-tabs-mode Miles Bader
2006-08-09 11:09 ` indent-tabs-mode Klaus Zeitler
2006-08-09 17:25 ` indent-tabs-mode Eli Zaretskii
2006-08-10 5:27 ` Miles Bader [this message]
2006-08-10 15:11 ` indent-tabs-mode Stefan Monnier
2006-08-10 15:22 ` indent-tabs-mode Aidan Kehoe
2006-08-09 19:15 ` indent-tabs-mode Richard Stallman
2006-08-09 22:29 ` indent-tabs-mode Bill Wohler
2006-08-10 2:51 ` indent-tabs-mode Stefan Monnier
2006-08-10 5:30 ` indent-tabs-mode Miles Bader
2006-08-10 16:27 ` indent-tabs-mode Richard Stallman
2006-08-10 16:45 ` indent-tabs-mode Bill Wohler
-- strict thread matches above, loose matches on Subject: below --
2006-08-09 13:06 indent-tabs-mode Robert Thorpe
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=buoy7tx9n4o.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=emacs-devel@gnu.org \
--cc=kzeitler@lucent.com \
--cc=miles@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.