unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dan Harms <Dan.Harms@xrtrading.com>
Cc: 32051@debbugs.gnu.org
Subject: bug#32051: 26.1; grep-regexp-alist on windows
Date: Wed, 04 Jul 2018 19:26:27 +0300	[thread overview]
Message-ID: <83in5vnf0s.fsf@gnu.org> (raw)
In-Reply-To: <65653506844b4308957893b429dea091@chihq-post2.XRTRADING.LOCAL> (message from Dan Harms on Wed, 4 Jul 2018 12:14:41 +0000)

> From: Dan Harms <Dan.Harms@xrtrading.com>
> Date: Wed, 4 Jul 2018 12:14:41 +0000
> 
> Starting in emacsc 26.1, the grep-regexp-alist stopped matching grep
> hits that have a colon in them, which breaks on windows for me, since
> the file paths always have a drive letter prepended.
>  
> For example,
>  
> the grep hit:
>  
> c:/Users/my.name/src/project\src\kbhit.hpp:29:#include <termios.h>
>  
> used to be matched by prior versions of emacs, but as of 26.1, the
> colon in the second character prevents this from being recognized as a
> grep match.

I don't think I can reproduce this.  I've just ran a Grep command
whose hits look like this:

  d:/gnu/emacs/branch/src/callproc.c:214:#ifdef DOS_NT

and they seem to exhibit all the traits of a Grep hit.

What exactly do you mean by "prevents from being recognized as a grep
match"?  What doesn't happen that you expected to happen and that was
happening with prior versions of Emacs?  Also, does the problem go
away if you invoke Emacs as "emacs -Q"?





  reply	other threads:[~2018-07-04 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04 12:14 bug#32051: 26.1; grep-regexp-alist on windows Dan Harms
2018-07-04 16:26 ` Eli Zaretskii [this message]
2018-07-04 19:57   ` Noam Postavsky
2018-07-06  8:51     ` Eli Zaretskii
2018-07-09 21:08       ` Noam Postavsky
2018-07-10 15:57         ` Eli Zaretskii
2018-07-13  1:51           ` Noam Postavsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83in5vnf0s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32051@debbugs.gnu.org \
    --cc=Dan.Harms@xrtrading.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).