On Fri, 25 Oct 2024, Arsen Arsenović wrote:
> Maybe we should go the other way around? Compressing eight spaces into
> a tab leads to strange artifacts in diffs (where lines appear
> misindented because some were aligned by tabs and some by spaces), and
I also agree that spaces are preferable (g
Sam James writes:
> IMO these (already-committed other) whitespace changes mean we should
> already consider a .git-blame-ignore-revs file at the root of the repo.
>
> We would list any large whitespace changes in there.
>
> Users would have to run 'git config blame.ignoreRevsFile
> .git-blame-ig
Jakub Jelinek writes:
> On Fri, Oct 25, 2024 at 01:25:25PM +0200, Arsen Arsenović wrote:
>> Maybe we should go the other way around? Compressing eight spaces into
>> a tab leads to strange artifacts in diffs (where lines appear
>> misindented because some were aligned by tabs and some by spaces)
Jonathan Wakely writes:
> On Fri, 25 Oct 2024 at 12:54, Jakub Jelinek wrote:
>>
>> On Fri, Oct 25, 2024 at 01:25:25PM +0200, Arsen Arsenović wrote:
>> > Maybe we should go the other way around? Compressing eight spaces into
>> > a tab leads to strange artifacts in diffs (where lines appear
>> >
Arsen Arsenović writes:
> Hi!
>
> Jakub Jelinek writes:
>
>> Hi!
>>
>> On top of the previously posted leading whitespace patch, this change
>> just replaces 8 consecutive spaces in leading whitespace by tab.
>> The patch is too large (1MB xz -9e compressed), so I'm not even trying to
>> split it
Jakub Jelinek writes:
> On Fri, Oct 25, 2024 at 01:25:25PM +0200, Arsen Arsenović wrote:
>> Maybe we should go the other way around? Compressing eight spaces into
>> a tab leads to strange artifacts in diffs (where lines appear
>> misindented because some were aligned by tabs and some by spaces)
On Fri, 25 Oct 2024 at 12:17, Jakub Jelinek wrote:
>
> Hi!
>
> On top of the previously posted leading whitespace patch, this change
> just replaces 8 consecutive spaces in leading whitespace by tab.
> The patch is too large (1MB xz -9e compressed), so I'm not even trying to
> split it up into 4+
On Fri, Oct 25, 2024 at 7:54 AM Jakub Jelinek wrote:
>
> On Fri, Oct 25, 2024 at 01:25:25PM +0200, Arsen Arsenović wrote:
> > Maybe we should go the other way around? Compressing eight spaces into
> > a tab leads to strange artifacts in diffs (where lines appear
> > misindented because some were
On Fri, Oct 25, 2024 at 01:12:15PM +0100, Jonathan Wakely wrote:
> So everything except:
>
> include/pstl/*
> src/c++17/ryu/*
> src/c++17/fast_float/*
Thanks, changed in my copy.
grep 'pstl\|ryu\|fast_float' Q624
is now empty.
Jakub
On Fri, 25 Oct 2024 at 12:54, Jakub Jelinek wrote:
>
> On Fri, Oct 25, 2024 at 01:25:25PM +0200, Arsen Arsenović wrote:
> > Maybe we should go the other way around? Compressing eight spaces into
> > a tab leads to strange artifacts in diffs (where lines appear
> > misindented because some were al
On Fri, Oct 25, 2024 at 01:25:25PM +0200, Arsen Arsenović wrote:
> Maybe we should go the other way around? Compressing eight spaces into
> a tab leads to strange artifacts in diffs (where lines appear
> misindented because some were aligned by tabs and some by spaces), and
> nowadays editor autho
Hi!
Jakub Jelinek writes:
> Hi!
>
> On top of the previously posted leading whitespace patch, this change
> just replaces 8 consecutive spaces in leading whitespace by tab.
> The patch is too large (1MB xz -9e compressed), so I'm not even trying to
> split it up into 4+ pieces to fit under the m
Hi!
On top of the previously posted leading whitespace patch, this change
just replaces 8 consecutive spaces in leading whitespace by tab.
The patch is too large (1MB xz -9e compressed), so I'm not even trying to
split it up into 4+ pieces to fit under the mailing list limits.
But the change was d
13 matches
Mail list logo
