From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117000: Untabify cl-macs.el
Date: Mon, 21 Apr 2014 00:13:29 -0700 [thread overview]
Message-ID: <5354C519.9090005@dancol.org> (raw)
In-Reply-To: <837g6jduo5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
On 04/21/2014 12:10 AM, Eli Zaretskii wrote:
>> Date: Sun, 20 Apr 2014 17:28:45 -0700
>> From: Daniel Colascione <dancol@dancol.org>
>>
>> On 04/20/2014 05:03 PM, Daniel Colascione wrote:
>>> ------------------------------------------------------------
>>> revno: 117000
>>> revision-id: dancol@dancol.org-20140421000344-9mcpbae1prbh1uql
>>> parent: dancol@dancol.org-20140420232404-fgxzomu1nqu3gi96
>>> committer: Daniel Colascione <dancol@dancol.org>
>>> branch nick: trunk
>>> timestamp: Sun 2014-04-20 17:03:44 -0700
>>> message:
>>> Untabify cl-macs.el
>>
>> On second thought, I've uncommited this change. It might make it hard to
>> move changes between emacs-24 and trunk. Let's wait until emacs-24
>> ships, then untabify everything once.
>
> Why untabify at all? Using tabs and spaces is the default GNU coding
> style, so why should we stray from that?
In Lisp code, using tabs makes no sense: code is frequently lined up
precisely, so you get a mixture of tabs and spaces anyway, making it
impossible to use a different tab-width. Why would you want to use tabs
at all?
> (It's an uphill battle you'll lose anyway, because many people, yours
> truly included, have indent-tabs-mode set non-nil,
Don't do that then.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2014-04-21 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Wc1iD-0005Z5-Tb@vcs.savannah.gnu.org>
2014-04-21 0:28 ` [Emacs-diffs] trunk r117000: Untabify cl-macs.el Daniel Colascione
2014-04-21 7:10 ` Eli Zaretskii
2014-04-21 7:13 ` Daniel Colascione [this message]
2014-04-21 8:03 ` Stephen J. Turnbull
2014-04-21 8:38 ` Eli Zaretskii
2014-04-21 8:40 ` Daniel Colascione
2014-04-21 8:48 ` Eli Zaretskii
2014-04-21 12:03 ` Juanma Barranquero
2014-04-21 16:28 ` Lars Magne Ingebrigtsen
2014-04-21 18:17 ` Josh
2014-04-21 18:22 ` Daniel Colascione
2014-04-21 21:27 ` Stefan Monnier
2014-04-21 12:49 ` 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=5354C519.9090005@dancol.org \
--to=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).