https://llvm.org/bugs/show_bug.cgi?id=29189
Bug ID: 29189
Summary: Call 1888.811.4532 Skype support chat
Product: lldb
Version: 3.9
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priori
https://llvm.org/bugs/show_bug.cgi?id=29188
Bug ID: 29188
Summary: skype is not working? Call 1888.811.4532
Product: lldb
Version: 3.9
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Pri
https://llvm.org/bugs/show_bug.cgi?id=29178
Bug ID: 29178
Summary: how to reset skype
Product: lldb
Version: 3.9
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Comp
You can grep for " {$". With this regex I
see no false positives and 272 case with 40 or more leading spaces
On Sun, 28 Aug 2016, 17:59 Zachary Turner via lldb-dev, <
lldb-dev@lists.llvm.org> wrote:
> Here it is
>
>
> grep -n '^ \+' . -r -o | awk '{t=length($0);su
Here it is
grep -n '^ \+' . -r -o | awk '{t=length($0);sub(" *$","");printf("%s%d\n",
$0, t-length($0));}' | sort -t: -n -k 3 -r | awk 'BEGIN { FS = ":" } ; { if
($3 >= 50) print $0 }'
On Sun, Aug 28, 2016 at 9:54 AM Zachary Turner wrote:
> I tried that, but most of the results (and there are a
I tried that, but most of the results (and there are a ton to wade through)
are function parameters that wrapped and align with the opening paren on
the next line.
Earlier in the thread (i think it was this thread anyway) i posted a bash
incantation that will grep the source tree and return all li
Can you just grep for “^“ or something? That
seems like a straight-forward way to find lines that have a ton of leading
indentation.
-Chris
> On Aug 27, 2016, at 9:28 AM, Zachary Turner wrote:
>
> It will probably be hard to find all the cases. Unfortunately
