From: "Alexandre François Garreau" <galex-713@galex-713.eu>
To: Emacs Developers <emacs-devel@gnu.org>
Cc: GNU Emacs Help <help-gnu-emacs@gnu.org>
Subject: Re: tab-indented project
Date: Thu, 10 Oct 2019 09:30:35 +0200 [thread overview]
Message-ID: <9142283.YEivGVfUA7@pc-713> (raw)
In-Reply-To: <2704501.DAA5g6XQLJ@pc-713>
Le jeudi 10 octobre 2019 08:48:25 CEST, vous avez écrit :
> To consistently hack a tab-indented project, I thought to “(standard-indent
> . tab-width)” as dir-local variable. Yet it doesn’t seem to eval
> variables, contrarily to file-local ones. Also is there a more canonical
> way of making indentation purely by tabs? Thank you ^^
I just noticed I should use `c-basic-offset' instead: what’s the use of a
separate variable for that, that complexify a such understandable and likely
user feature? if none, couldn’t it be replaced with `standard-indent'?
parent reply other threads:[~2019-10-10 7:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2704501.DAA5g6XQLJ@pc-713>]
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=9142283.YEivGVfUA7@pc-713 \
--to=galex-713@galex-713.eu \
--cc=emacs-devel@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).