all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Juri Linkov <juri@linkov.net>
Cc: Bastian Beischer <bastian.beischer@gmail.com>, 22589@debbugs.gnu.org
Subject: bug#22589: 25.0.90; First match found by isearch-forward-symbol is not necessarily a symbol.
Date: Mon, 08 Feb 2016 12:30:20 +0100	[thread overview]
Message-ID: <87mvrbo2wj.fsf@web.de> (raw)
In-Reply-To: <87d1s8kmyo.fsf@mail.linkov.net> (Juri Linkov's message of "Mon,  08 Feb 2016 02:54:39 +0200")

Juri Linkov <juri@linkov.net> writes:

> Please imagine that you need to search for the symbol "int" (or any
> other symbol longer than the single-character "i").  How then you
> would be able to type the whole symbol "int" if the search failed
> after typing the first character "i" (or moved to the first occurrence
> of the symbol "i" when you need to find the symbol "int")?

I agree that this is a useful feature.  Not having it would make
entering the search pattern confusing.

But I think it should be documented.  When does it occur, and what else
is matched (one or two sentences).

There could also be some indication when this first match is not a
"real" match - but that might be overkill.


Regards,

Michael.





  reply	other threads:[~2016-02-08 11:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 20:41 bug#22589: 25.0.90; First match found by isearch-forward-symbol is not necessarily a symbol Bastian Beischer
2016-02-08  0:09 ` Bastian Beischer
2016-02-08  0:54 ` Juri Linkov
2016-02-08 11:30   ` Michael Heerdegen [this message]
2016-02-10  0:55     ` Juri Linkov
2016-02-10 11:30       ` Michael Heerdegen
2016-02-08 11:34   ` Bastian Beischer
2016-02-10  0:54     ` Juri Linkov
2017-02-05 23:39       ` Juri Linkov
2017-02-06 11:10         ` Michael Heerdegen
2017-02-07  0:11           ` Juri Linkov
2017-02-07 19:19             ` 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

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

  git send-email \
    --in-reply-to=87mvrbo2wj.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=22589@debbugs.gnu.org \
    --cc=bastian.beischer@gmail.com \
    --cc=juri@linkov.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.