On Tue, Mar 15, 2016 at 5:48 PM, Linus Torvalds <torva...@linux-foundation.org> wrote: > On Tue, Mar 15, 2016 at 5:45 PM, Junio C Hamano <gits...@pobox.com> wrote: >> >> Wouldn't it be nicer to do this kind of thing at the output side? A >> stupid way would be to have an option to indent the log text with a >> tab instead of 4-spaces, but a more sensible way would be to keep >> the visual 4-space-indent and do the expand-tab for each line of >> text. > > Yes, that would certainly work for me too. It's just the "ascii boxes > don't line up" that is problematic..
I would also rather side to correct the display side rather than the applying side. [I still want to send and apply patches with git written in the white space language ;] 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... such that it looks like an indented terminal. That way we would also preserve the tabs in case you'd want to copy the message as is. Thanks, Stefan > > (Also people including example source code etc, where the first tab > looks wildly different from the second one) > > Linus > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
