Is there some general mechanism missing in text mode consoles but present in GUI terminals that I can enable for mouse-supporting applications? By "general" I mean not per-application (not application-specific). For example, aptitude, finch, w3m, etc. understand clicks in GUI terminals but not in Linux consoles with GPM. They seem to share the same problem.
Since aptitude (etc.) does include mouse support (it's just inactive in text mode consoles for some reason), the aptitude case should not be seen as "magically adding a feature that an application doesn't support". I have mouse support in Aptitude in a GUI terminal; I have GPM running on a Linux console; how do I get mouse support in Aptitude in the console?
I think there is a switch between GUI terminals and consoles (a feature that makes the difference). I guess we've all encountered a few more of those GUI/console "switches" (and I have a few more of these questions). A "switch" may affect many applications, thus becoming a broader, system-wide issue, yet the issue itself can be specific, which I hope may validate my question.
If not, for simplicity, we could make this question about aptitude and gpm. Any answer may still be a useful lead. At least it helps me learn more about getting the TTY as mouse-aware as it can get.
My purpose was to make console editing more "natural-feeling", with a special focus on nano and readline. Nano and mc were not a good lead; they are just isolated console workaround cases, not mouse support vs no support cases. Readline turned out to be a more complicated case, so it wasn't as representative as I'd hoped. However, after one gets it to work, it probably hits the same "switch". Mouse reporting events seem to be encoded differently in the console.