From: Marc Branchaud <marcnarc@xiplink.com>
To: Stefan Beller <sbeller@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Tabs in commit messages - de-tabify option in strbuf_stripspace()?
Date: Wed, 16 Mar 2016 10:27:45 -0400 [thread overview]
Message-ID: <56E96D61.6060007@xiplink.com> (raw)
In-Reply-To: <CAGZ79kZtAm1M=9CGDGxPdecXEuNEQcbpQb3FNj9=Py0VE2UrKQ@mail.gmail.com>
On 16-03-15 09:02 PM, Stefan Beller wrote:
> On Tue, Mar 15, 2016 at 6:00 PM, Stefan Beller <sbeller@google.com> wrote:
>>
>> Instead of converting to whitespaces in Git, we could make use of the
>> set_tabs capability for ttys and setup the terminal for having tabs align
>> to 12,+8,+8,+8...
>
> Or rather read in the existing tabs configuration and shift it by a constant.
Could this also help with diff output, where the leading + or - mars the
indentation in a similar way?
That opens a bit of a deeper problem, because not all the files in a single
repo necessarily use the same tab size.
M.
next prev parent reply other threads:[~2016-03-16 14:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 0:16 Tabs in commit messages - de-tabify option in strbuf_stripspace()? Linus Torvalds
2016-03-16 0:23 ` Stefan Beller
2016-03-16 0:45 ` Linus Torvalds
2016-03-16 0:34 ` Randall S. Becker
2016-03-16 0:45 ` Junio C Hamano
2016-03-16 0:48 ` Linus Torvalds
2016-03-16 1:00 ` Stefan Beller
2016-03-16 1:02 ` Stefan Beller
2016-03-16 14:27 ` Marc Branchaud [this message]
2016-03-16 14:50 ` Duy Nguyen
2016-03-16 16:15 ` Linus Torvalds
2016-03-16 16:47 ` Junio C Hamano
2016-03-20 13:29 ` Matthieu Moy
2016-03-16 4:05 ` Linus Torvalds
2016-03-16 4:46 ` Junio C Hamano
2016-03-16 4:57 ` Linus Torvalds
2016-03-16 5:17 ` Jeff King
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=56E96D61.6060007@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.com \
--cc=torvalds@linux-foundation.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.
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 NNTP newsgroup(s).