Lee, I tested out your approach - and it did not work.
I tested the newest version (release candidate - October 28, 2014).
I have attached a keymap test (Test_16 - *.e) - that shows the attempts
and results (of trying out your suggestion).
I also attached screen shots of the keymap options - to show that the
testcase loads OK - but the keymap simply does not work in Grep mode
(as defined in Test_16 attached).
In a nutshell - the Grep mode (search pane) edit behaviour - can NOT be
configured to behave like the main edit window (as per the attached
testcase Test_16).
The differences were spotty - in the sense that
[1] [Grep mode - search pane] keybindings - that are unmapped - should simply default to [Default mode - main edit window pane] behavior.
[2] [Grep mode - search pane] unmapped keys - do NOT conform to ALL default behavior (but SOME do).
You can see some examples - at the bottom of the attached testcase
(..Test_16..).
If I could just get my : 'C-M'= bottom_of_buffer : behavior going - I
would be a happy camper :-)
For now, however, I'll just leave it to the SE dev team - so they are
aware of the issue - regarding keymap conformance between - (1) main edit
windows and (2) search results windows.
Final note - There is the Left Click - Context Menu - Open as editor
window - alternative to this issue.
Even so, SE is the fastest editor on the planet - because its focused on
minimal effort to get something done.
As always, I hope I have not missed something simple or fundamental - in
the attached testcase code.
It would be nice, long term - to have (A) search pane results - adopt
default edit window behavor - as well as (B) - the ability to remap
default Grep mode behavior - to match SE user keymaps for the main edit
windows.
Lee : Thanks so much for your advice, however, since I learned more about
SE keymap modality and keybinding behavior in the various SE window
groups :-)
PS. I just loaded the testcase via Macros -> Load Module.
I don't think it matters - relative to a command line load
of a module (SE Batch file) - or a normal SE module load
- using the GUI module load method.