unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 63272@debbugs.gnu.org
Subject: bug#63272: 29.0.90; xref fails on long lines
Date: Mon, 08 May 2023 18:41:13 +0300	[thread overview]
Message-ID: <868rdzw9ra.fsf@mail.linkov.net> (raw)
In-Reply-To: <599c01ab-f23c-b27a-6035-cd141770a415@gutov.dev> (Dmitry Gutov's message of "Fri, 5 May 2023 23:49:14 +0300")

>> In the real case the prefix and suffix were unique, so I didn't expect
>> that in a generated file there was a very long distance between prefix
>> and suffix.  To limit the distance between prefix and suffix I tried:
>>    C-x p g prefix.{0,100}suffix
>
> Try escaping { and }:
>
>   C-x p g prefix.\{0,100\}suffix

Thanks, this works.

> The regexp needs to use the syntax that Emacs can understand.
>
> Just the subset of it that can be translated to command like, so that Grep
> and Ripgrep can work with it too.
>
>> but xref that uses ripgrep fails to find matches.
>> So needed to fall back to ripgrep-based rgrep in this case:
>>    M-x rgrep prefix.{0,100}suffix
>> that works successfully.
>> It seems the problem is because of different regexp syntax
>> used by ripgrep and re-search-forward in xref--collect-matches-1.
>
> The conversion is performed by xref--regexp-to-extended.

Shouldn't the conversion also escape { and } ?





  reply	other threads:[~2023-05-08 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 15:07 bug#63272: 29.0.90; xref fails on long lines Juri Linkov
2023-05-04 15:33 ` Dmitry Gutov
2023-05-05 17:50   ` Juri Linkov
2023-05-05 20:49     ` Dmitry Gutov
2023-05-08 15:41       ` Juri Linkov [this message]
2023-05-08 18:59         ` Dmitry Gutov
2023-05-04 15:58 ` Gregory Heytings
2023-05-05  9:13   ` Gregory Heytings
2023-05-05 17:39     ` Juri Linkov

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=868rdzw9ra.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=63272@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    /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).