[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#17246: grep-2.19 planning

From: Paul Eggert
Subject: bug#17246: grep-2.19 planning
Date: Tue, 13 May 2014 09:51:38 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

On 05/13/2014 08:43 AM, Paolo Bonzini wrote:
No, it had not resulted in a bug. Paul thought there was a bug, but there was none.

Yes, that's correct. Although the change simplified maintenance it didn't fix a bug (I thought it did, but I was wrong).

Windows?  It has PowerShell, not POSIX shell.

Not if we're talking Windows Vista or Windows Server 2008; PowerShell is an unbundled add-own for those systems, so we can't assume it.

However, it shouldn't hurt to port GNU grep to the PowerShell environment, if it's easy to maintain the port. What is the usual strategy for PowerShell users of other GNU applications (Emacs, coreutils, etc.)? My vague impression is that they use aliases. Perhaps we could suggest as part of the installation instructions that they'Set-Alias fgrep grep -F' while they're also doing 'Set-Alias grep ... whatever ...'. That should be simple and easily separable from the rest of the 'grep' distribution.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]