From: michael@cadilhac.name (Michaël Cadilhac)
To: emacs-devel@gnu.org
Subject: unhighlight-regexp displays awful things.
Date: Mon, 20 Aug 2007 18:57:56 +0200 [thread overview]
Message-ID: <87wsvqdtyj.fsf@lrde.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 498 bytes --]
Hi guys !
Well, I don't know if the following is on purpose, but it is very
strange : highlight something with highlight-regexp, then try
unhighlighting it with M-x unhighlight-regexp, and you'll end-up with no
less than a POPUP MENU !
Gosh... So many years of fighting popups in our web browsers, and here
they are, in the middle of the almighty Emacs. Curse you damned popping
stuff !
It may be due, however, to a change in (this-command-keys)...
What about the following :
[-- Attachment #1.1.2: hi-lock.patch --]
[-- Type: text/x-patch, Size: 1398 bytes --]
Index: hi-lock.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/hi-lock.el,v
retrieving revision 1.46
diff -B -w -c -r1.46 hi-lock.el
*** hi-lock.el 26 Jul 2007 05:26:25 -0000 1.46
--- hi-lock.el 20 Aug 2007 16:58:03 -0000
***************
*** 462,468 ****
\\<minibuffer-local-must-match-map>Use \\[minibuffer-complete] to complete a partially typed regexp.
\(See info node `Minibuffer History'.\)"
(interactive
! (if (and (display-popup-menus-p) (vectorp (this-command-keys)))
(catch 'snafu
(or
(x-popup-menu
--- 462,468 ----
\\<minibuffer-local-must-match-map>Use \\[minibuffer-complete] to complete a partially typed regexp.
\(See info node `Minibuffer History'.\)"
(interactive
! (if (and (display-popup-menus-p) (not last-nonmenu-event))
(catch 'snafu
(or
(x-popup-menu
Index: ChangeLog
===================================================================
RCS file: /sources/emacs/emacs/lisp/ChangeLog,v
retrieving revision 1.11583
diff -C 0 -r1.11583 ChangeLog
*** ChangeLog 20 Aug 2007 15:53:07 -0000 1.11583
--- ChangeLog 20 Aug 2007 16:58:08 -0000
***************
*** 0 ****
--- 1,5 ----
+ 2007-08-20 Michaël Cadilhac <michael@cadilhac.name>
+
+ * hi-lock.el (hi-lock-unface-buffer): Show a x-menu only if the
+ mouse was used.
+
[-- Attachment #1.1.3: Type: text/plain, Size: 335 bytes --]
TIA!
--
| Michaël `Micha' Cadilhac | The second-degree, |
| http://michael.cadilhac.name | is kind of |
| JID/MSN: | the semantic back slang. |
`---- michael.cadilhac@gmail.com | - --'
[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2007-08-20 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 16:57 Michaël Cadilhac [this message]
2007-08-21 14:46 ` unhighlight-regexp displays awful things Richard Stallman
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=87wsvqdtyj.fsf@lrde.org \
--to=michael@cadilhac.name \
--cc=emacs-devel@gnu.org \
/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).