From: despen@verizon.net
To: help-gnu-emacs@gnu.org
Subject: Re: Indenting with 2 spaces
Date: Thu, 04 Nov 2010 17:05:14 -0400 [thread overview]
Message-ID: <icaaloiyut.fsf@verizon.net> (raw)
In-Reply-To: jwvwrosvroy.fsf-monnier+gnu.emacs.help@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Thanks! That seems like a big limitation of Emacs that there is no way
>> to specify all modes at once.
>
> Yes and no:
> - it's an inconvenience that many aspects of major modes are not
> sufficiently standardized for there to be a central place where the
> default can be changed once and for all modes.
> - favorite indentation steps tend to depend on the language because
> different styles of syntaxes lend themselves more or less well to
> shallow/deep indentation steps. Furthermore, most projects impose
> a particular indentation style (and indentation's basic step is part
> of it), so it's fairly common to have to use different basic steps in
> different files, even for the same language, if you work on more than
> a single project.
> So while I generally agree with you, in the specific case of basic
> indentation step, I don't think it's nearly as bad as you say.
Other issues:
1. Makefiles have a specific indentation and attempts to mess with
it would not work.
Whether there are other languages like that, I don't know.
I use my own BAL mode for mainframe Assembler that wouldn't tolerate
being adjusted.
2. Setting up a wrapper for a couple dozen common modes wouldn't be
all that hard as long as all you were worried about is basic indentation
but indentation rules are more complex than just width and spaces
vs. tabs.
prev parent reply other threads:[~2010-11-04 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <afc2d1bd-05a2-4068-bfd7-3793f40f9a96@j18g2000yqd.googlegroups.com>
[not found] ` <xeiafwviv6td.fsf@kobe.laptop>
2010-11-03 22:21 ` Indenting with 2 spaces Philip
[not found] ` <jwvwrosvroy.fsf-monnier+gnu.emacs.help@gnu.org>
2010-11-04 21:05 ` despen [this message]
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=icaaloiyut.fsf@verizon.net \
--to=despen@verizon.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.
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.