Another problem: executing search-next seems to exit search-mode: after clicking the item for the first time, it is again greyed out. The solution is to call instead search-button-next which is just a wrapper foredit_replace_rep::search_button_next() which in turn sets the input mode and performs a edit_replace_rep::search_next(). A direct call in scheme to search-next would end the search after one step. Why the mode is reset, I have no idea. ________________ Miguel de Benito.
On Fri, Jul 15, 2011 at 22:30, Miguel de Benito Delgado < [email protected]> wrote: > Hi, > > working on bug 33131 <https://savannah.gnu.org/bugs/index.php?33131>, > I've added a "Find next match" item to the "Edit" menu. By default it's > greyed out and it's enabled while searching in the document. The scheme > function called is search-next, using code like this in edit-menu.scm: > > (when (search-mode?) > ("Find next match" (search-next))) > > The shortcut for search-next is assigned in generic-kbd.scm, once per > profile. Under MacOS the relevant code is: > > ("search macos g" (search-next)) > > which apparently means that the shortcut is only made available when in > search mode (see prefix-kbd.scm for some of the keys). The problem is that > this seems to mess up with the way the menus automagically display the > configured shortcuts. Only after deleting the "search" in "search macos g", > do I see the shortcut in the menu, which obviously sucks. > > Any ideas? > ________________ > Miguel de Benito. >
_______________________________________________ Texmacs-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/texmacs-dev
