[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17246: grep-2.19 planning
From: |
Eli Zaretskii |
Subject: |
bug#17246: grep-2.19 planning |
Date: |
Wed, 14 May 2014 21:35:06 +0300 |
> Date: Thu, 15 May 2014 01:04:52 +0900
> From: Norihiro Tanaka <address@hidden>
> Cc: Paolo Bonzini <address@hidden>, Paul Eggert <address@hidden>
>
> I submit a fix of the previous patch.
Thank you.
> By the way, however, I can't understand why you adhere to keep using
> egrep and/or fgrep instead of `grep -E' or `grep -F' on minor platforms
> as MinGW.
Muscle memory. There are those who work on both Windows and Posix
platforms, and who started using these programs long ago, before there
were GNU Grep with these switches. My fingers type "fgrep" before I
even realize what I need to do.
> Even if egrep and/or fgrep are shell scripts, they aren't troubled for
> me. Even if troubled, I will replace them to `grep -E' and/or `grep -F'.
Replace how? On Windows, there are no way to do that without hitting
some limitation, even on the latest versions of Windows.
- bug#17246: grep-2.19 planning, (continued)
- bug#17246: grep-2.19 planning, Jim Meyering, 2014/05/14
- bug#17246: grep-2.19 planning, arnold, 2014/05/14
- bug#17246: grep-2.19 planning, Eli Zaretskii, 2014/05/14
- bug#17246: grep-2.19 planning, Norihiro Tanaka, 2014/05/15
- bug#17246: grep-2.19 planning, Paolo Bonzini, 2014/05/15
- bug#17246: grep-2.19 planning, Jim Meyering, 2014/05/14
- bug#17246: grep-2.19 planning, Norihiro Tanaka, 2014/05/14
- bug#17246: grep-2.19 planning,
Eli Zaretskii <=
- bug#17246: grep-2.19 planning, Paul Eggert, 2014/05/14
- bug#17246: grep-2.19 planning, Eli Zaretskii, 2014/05/14
- bug#17246: grep-2.19 planning, Paul Eggert, 2014/05/14
- bug#17246: grep-2.19 planning, Eli Zaretskii, 2014/05/14
- bug#17246: grep-2.19 planning, Paul Eggert, 2014/05/13