From: Juri Linkov <juri@jurta.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 13687@debbugs.gnu.org
Subject: bug#13687: 24.3.50; `read-regexp' should provide regex for symbol at point as defaults
Date: Tue, 12 Feb 2013 19:50:29 +0200 [thread overview]
Message-ID: <87bobpxvyy.fsf@mail.jurta.org> (raw)
In-Reply-To: <87r4kn5ppo.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 11 Feb 2013 11:58:35 +0530")
> Spun from
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11095
Thanks for creating a separate request.
What I mostly meant in http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11095#20
is that currently `isearch-highlight-regexp' doesn't propagate
the search string to hi-lock as a symbol-matching regexp correctly.
I proposed to relegate this problem to hi-lock by creating a new
command `highlight-symbol' that would turn its plain string argument
into a symbol-matching regexp.
> `read-regexp' should provide regex for symbol at point as one of the
> defaults. This should be the first of defaults while in any of the
> progmodes.
>
> I provided a patch which can be seen here:
> http://debbugs.gnu.org/cgi/bugreport.cgi?msg=32;filename=bug11095-r110503.diff;att=4;bug=11095
>
> The key thing to note is this:
>
> 1. `find-tag-default' (when find-tag-default-function is nil) will pick
> up the symbol at point.
>
> 2. When tag is picked as above, surround it with beginning/end-of-symbol
> regexp delimiters and add it to defaults.
The advantage of your proposal is that when the user doesn't
need symbol delimiters, it's easy to delete them. This is easier
than to add symbol delimiters in case when the user needs them.
next prev parent reply other threads:[~2013-02-12 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 6:28 bug#13687: 24.3.50; `read-regexp' should provide regex for symbol at point as defaults Jambunathan K
2013-02-12 17:50 ` Juri Linkov [this message]
2013-02-15 15:41 ` Stefan Monnier
2013-02-16 9:31 ` Jambunathan K
2013-02-16 14:28 ` Stefan Monnier
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=87bobpxvyy.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=13687@debbugs.gnu.org \
--cc=kjambunathan@gmail.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 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.