From: charles@aurox.ch (Charles A. Roelli)
To: Juri Linkov <juri@linkov.net>
Cc: 32990@debbugs.gnu.org
Subject: bug#32990: 26.1.50; isearch-forward + t-m-m/mark-active doc
Date: Sun, 18 Nov 2018 21:24:58 +0100 [thread overview]
Message-ID: <m25zwuyvz9.fsf@aurox.ch> (raw)
In-Reply-To: <87sgzzwisx.fsf@mail.linkov.net> (message from Juri Linkov on Sat, 17 Nov 2018 23:07:58 +0200)
> From: Juri Linkov <juri@linkov.net>
> Date: Sat, 17 Nov 2018 23:07:58 +0200
>
> > There's a first draft of a menu- and tool-bar for Isearch at the end
> > of this message (on branch master). Clicking the menu items and icons
> > should work okay with the mouse, but I haven't yet found a way to show
> > the menu with either "tmm-menubar" or TTY menus, since activating
> > these functions will normally exit Isearch.
>
> What do you think about adding also some menu to the mode-line
> indicator of Isearch.
Good idea, will add it in.
> Currently clicking on the word "Isearch "
> in the mode-line signals the error:
>
> Debugger entered--Lisp error: (error #("Cannot find minor mode for ‘ Isearch’" ...
> signal(error (#("Cannot find minor mode for ‘ Isearch’" ...
> error("Cannot find minor mode for `%s'" #(" Isearch" ...
> minor-mode-menu-from-indicator(#(" Isearch" ...
> mouse-minor-mode-menu((down-mouse-1 ...
> funcall-interactively(mouse-minor-mode-menu ...
> call-interactively(mouse-minor-mode-menu nil nil)
> command-execute(mouse-minor-mode-menu)
Maybe "debug-on-error" is on?
next prev parent reply other threads:[~2018-11-18 20:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 17:58 bug#32990: 26.1.50; isearch-forward + t-m-m/mark-active doc Charles A. Roelli
2018-10-08 20:07 ` Eli Zaretskii
2018-10-09 18:14 ` Charles A. Roelli
2018-10-09 18:21 ` Eli Zaretskii
2018-10-14 19:53 ` Charles A. Roelli
2018-10-15 15:02 ` Eli Zaretskii
2018-10-16 18:57 ` Charles A. Roelli
2018-10-20 9:59 ` Eli Zaretskii
2018-10-25 19:11 ` Charles A. Roelli
2018-10-28 10:06 ` Charles A. Roelli
2018-10-28 15:53 ` Eli Zaretskii
2018-10-28 17:09 ` Charles A. Roelli
2018-11-10 13:57 ` Charles A. Roelli
2018-11-10 14:05 ` Eli Zaretskii
2018-11-15 19:57 ` Charles A. Roelli
2018-11-15 20:07 ` Eli Zaretskii
2018-11-15 22:15 ` Juri Linkov
2018-11-16 8:53 ` martin rudalics
2018-11-16 16:00 ` Drew Adams
2018-11-17 9:29 ` martin rudalics
2018-11-17 21:32 ` Juri Linkov
2018-11-18 9:22 ` martin rudalics
2018-11-16 20:22 ` Charles A. Roelli
2018-11-17 21:01 ` Juri Linkov
2018-11-17 21:07 ` Juri Linkov
2018-11-18 1:49 ` Drew Adams
2018-11-18 20:24 ` Charles A. Roelli [this message]
2018-11-18 22:42 ` Juri Linkov
2018-11-19 20:14 ` Charles A. Roelli
2018-11-19 21:44 ` Juri Linkov
2018-11-20 19:49 ` Charles A. Roelli
2018-11-21 20:14 ` Charles A. Roelli
2018-11-21 22:31 ` Juri Linkov
2018-11-22 20:29 ` Charles A. Roelli
2018-11-22 21:59 ` Juri Linkov
2018-11-23 8:17 ` Eli Zaretskii
2018-11-24 11:25 ` Charles A. Roelli
2018-11-24 11:44 ` Eli Zaretskii
2018-11-24 12:51 ` Charles A. Roelli
2019-04-02 0:22 ` Noam Postavsky
2018-11-10 20:34 ` 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=m25zwuyvz9.fsf@aurox.ch \
--to=charles@aurox.ch \
--cc=32990@debbugs.gnu.org \
--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 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).