unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 22238@debbugs.gnu.org
Subject: bug#22238: 25.0.50; isearch symbol search can't find ,@symbol
Date: Mon, 05 Dec 2016 14:55:22 +0100	[thread overview]
Message-ID: <874m2ifpkl.fsf@web.de> (raw)
In-Reply-To: <567DBA1F.7030702@yandex.ru> (Dmitry Gutov's message of "Fri, 25 Dec 2015 23:50:23 +0200")

Dmitry Gutov <dgutov@yandex.ru> writes:

> Maybe that should just be reverted. A more proper fix would make Emacs
> not consider @ as a symbol constituent when it's the first
> character. The "p" in "_ p" apparently tries but fails to do that.

FWIW, there is a similar problem concerning the end of the symbol and
".".

The real-life use case is that I wanted to rename the argument of a
function like this:

(defun el-search--string-matcher (eregexp)
  "Return a compiled match predicate for EREGEXP.
That's a predicate returning non-nil when extended regexp EREGEXP ...

with isearch in symbol mode.  But symbol search doesn't find the
occurrence of "EREGEXP" at the end of the first sentence of the
docstring.  Again, strictly speaking the behavior is as documented I
think ("."  is a symbol constituent), but this also again foils the
purpose of symbol matching in "real-life".  And again, the situation can
be ambiguous in rare cases.


Michael.





  parent reply	other threads:[~2016-12-05 13:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-25 21:29 bug#22238: 25.0.50; isearch symbol search can't find ,@symbol Michael Heerdegen
2015-12-25 21:50 ` Dmitry Gutov
2015-12-25 21:58   ` Michael Heerdegen
2015-12-25 22:03     ` Dmitry Gutov
2015-12-25 22:06   ` Andreas Schwab
2015-12-25 22:09     ` Dmitry Gutov
2015-12-26 10:54       ` Andreas Schwab
2015-12-26 12:32         ` Dmitry Gutov
2016-12-05 13:55   ` Michael Heerdegen [this message]
2023-07-28  1:19 ` Michael Heerdegen
2023-07-28  8:05   ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-29  2:21     ` Michael Heerdegen

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=874m2ifpkl.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=22238@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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).