Re: windows-like menu behavior in unix

>>>>> "marklar" == marklar  <[email protected]> writes:

    >> On Unix the compromise should be unnecessary as there should be
    >> no problem with having both a Meta and an Alt key defined.

    marklar> It may be unneccessary, but it seems better.  I don't
    marklar> want to have to relegate either ALT or META to ESC, which
    marklar> is a stretch for my home-position-using pinky.

If I must write the patch, "necessary" is going to be the criterion. :-)

    marklar> When I figure out the solution, I will be sure to post.
    marklar> I sure hope that it's not a windows-only hack.

Please post what you know already to [email protected] as a bug
report.  While some platform divergence is inevitable, we'd like to
minimize it.  Also CC: [email protected], as Ben is the author of that
code and would know both about platform divergences and how to make
them work the same if they don't already.  (Ben reads xemacs-beta
regularly, but he reads personal mail *frequently*.  The CC may save a
few days' lag.)

I can say it almost surely won't go into the 21.4 line if it requires
changes to the C code.

    marklar> Is that even possible in the xemacs code base?

Yes.  Console-handling code is pretty much completely divergent.

    marklar> Are there things in elisp that are non-portable?

In theory, any function that works only on Windows will have an
`mswindows-' prefix.  Just like any optional library support.  If you
find functions that don't have such a prefix, and are not documented
to work differently on different platforms, please report them.  It's
a bug either in the implementation or the documentation.

There are also functions that will either turn into no-ops or errors
if asked to handle values that don't make sense for the platform.

Keyboard handling is way below the level of elisp, though.

-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.