bug#31182: Grep Not Matching with Caret in First Line of File

[Benno Schulenberg]

Budin, Clay wrote:
> It seems like grep isn't matching with a caret (start-of-line) on the first 
> line of a file.
Most likely you have a BOM (Byte Order Mark) on the first line.

(It would be cool, though, if grep could ignore that mark.)

Benno

bug#31182: Grep Not Matching with Caret in First Line of File

[Jim Meyering]

tags 31182 notabug
close 31182
stop

On Sat, Apr 21, 2018 at 1:56 PM, Paul Eggert  wrote:
> I don't observe the problem in upstream grep, so quite possibly this is a
> packaging issue in Git for Windows. I suggest reporting the bug there.

Thanks, and by the above, I'm closing this and marking it as "notabug"
in our tracker. However, you're welcome to continue any discussion
here.

bug#31182: Grep Not Matching with Caret in First Line of File

[Paul Eggert]

I don't observe the problem in upstream grep, so quite possibly this is a 
packaging issue in Git for Windows. I suggest reporting the bug there.

bug#31182: Grep Not Matching with Caret in First Line of File

[Budin, Clay]

Hi,


Running "grep (GNU grep) 3.0" as part of Git for Windows (Git-2.16.2-64-bit.exe)

in bash shell.


It seems like grep isn't matching with a caret (start-of-line) on the first 
line of a file.


> head 

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnitySpeechToText.Utilities;

namespace UnitySpeechToText.Services
{
/// 
/// Base class for streaming speech-to-text SDK.
/// 



> grep "^using" 

using System.Collections.Generic;
using UnityEngine;
using UnitySpeechToText.Utilities;

> grep "using" 
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnitySpeechToText.Utilities;


Thanks,


Clay Budin

Principal Engineer - Content

MSG Ventures



This message may contain confidential, privileged or proprietary information of 
the Madison Square Garden Company or its affiliates. If you have received this 
message in error, please inform the sender by email and kindly delete the 
message.