I ran something like this to do the conversion (in bash or zsh): find . -name "*.jl" | while read i; do sed -i -e 's/\bString\b/AbstractString/g' $i; done
Glen On Friday, September 25, 2015 at 9:22:44 AM UTC-4, Isaiah wrote: > > But still, i'd prefer error messages that have more content... > > > Yes, there are a number of open issues already about errors, warnings, and > backtraces. The situation should improve when we bump to a newer LLVM > version. > > On Fri, Sep 25, 2015 at 9:17 AM, Andreas Lobinger <[email protected] > <javascript:>> wrote: > >> >> >> On Friday, September 25, 2015 at 2:52:43 PM UTC+2, Yichao Yu wrote: >>> >>> On Fri, Sep 25, 2015 at 8:25 AM, Andreas Lobinger <[email protected]> >>> wrote: >>> > Hello colleagues, >>> > >>> > the warning is quite nice, but a location would be nicer. How can i >>> track >>> > down, which line triggered the warning? >>> >>> What I did was just `grep -R` >>> >> >> I did similar (find all in editor for the full package dir). But still, >> i'd prefer error messages that have more content... >> > >
