From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb@sourceware.org
Subject: Re: Two quick questions
Date: Tue, 29 Nov 2011 04:34:00 -0000 [thread overview]
Message-ID: <CAHQ1cqEVdX_c=oCb6jbrbnncjh2TvTXd0rD_TPNs7yAX07Aedw@mail.gmail.com> (raw)
In-Reply-To: <4ED45AF9.9000009@earthlink.net>
On Tue, Nov 29, 2011 at 11:09 AM, Stan Shebs <stanshebs@earthlink.net> wrote:
> On 11/28/11 7:25 PM, Andrey Smirnov wrote:
>>
>> I was asking exactly because I wanted avoid generated unnecessary
>> "junk" in the patches just because I idly hit the tab on some line
>> in the code an my editor re-indented it differently(for example
>> with all spaces, which is default for me now) while writing a
>> patch. It is just that I've already seen one such occurrence in one
>> of my patches and I would like to avoid having them in further
>> ones. So, just to be clear, I'm neither planning nor thinking about
>> planning to re-indent the code. Andrey Smirnov
>
>
> 99+% of the code has been indented with Emacs using its old standard
> of 8-space tabs. So if you use that setting, the surprises will be
> fewest in number. :-)
So, what you're saying is
(setq tab-width 8)
(setq indent-tabs-mode t)
is the way of fewer surprises. Got it. :-)
Andrey Smirnov
next prev parent reply other threads:[~2011-11-29 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 8:47 Andrey Smirnov
2011-11-28 15:38 ` Joel Brobecker
2011-11-28 22:09 ` Christopher Faylor
2011-11-29 3:33 ` Andrey Smirnov
2011-11-29 20:56 ` Christopher Faylor
2011-11-29 3:25 ` Andrey Smirnov
2011-11-29 4:10 ` Stan Shebs
2011-11-29 4:34 ` Andrey Smirnov [this message]
2011-11-29 4:43 ` Eli Zaretskii
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='CAHQ1cqEVdX_c=oCb6jbrbnncjh2TvTXd0rD_TPNs7yAX07Aedw@mail.gmail.com' \
--to=andrew.smirnov@gmail.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).