Loading ...
Sorry, an error occurred while loading the content.

Re: [jasspa] ME under Mac OS X

Expand Messages
  • Jon Green
    ... Not sure what to expect with console version. The X-Windows version should behave correctly (will need to install the Apple X Server found on the
    Message 1 of 2 , Aug 22, 2005
      s wrote:
      > hello
      > has anybbody succeeded in running ME under Mac OS X (in Terminal) and
      > entering non-Western chars (i.e. Cyrillic, Baltic, etc)?
      > are there any hints / suggestions?
      > would be very grateful, thank you.

      Not sure what to expect with console version. The X-Windows version should behave correctly
      (will need to install the Apple X Server found on the installation disk).

      You need to set up the keyboard (M-x user-setup) and select the required keyboard +
      language. After that then you need to determine the keys that do not work and map them in.

      Follows are some notes on the keyboard translation.


      -------- Previous Question ---------------

      We do have keyboard translations for Windows but have
      none for UNIX and I cannot recall there ever being
      a problem (that was reported) - You do not say what
      window manager you are using.

      Fix one key at a time, first find out what the
      key is to find out the key code and then use
      translate-key to fix it. The standard key board
      translations that we do are in the file "keyboard.emf"
      so you can use this as an example of how to
      translate a key i.e.

      translate-key "<from codes>" "<to codes>"

      If you want to get rid of a key then use

      global-bind-key void "<duff key>"

      Add the translations and global bindings
      to your <user>.emf file so they are run
      at startup. If you use a single common
      <user>.emf across all platforms then
      use the $platform variable
      to determine the platform and decide
      what translations to apply similar to

      -------- Previous Question ---------------

      > Jeremy Cowgar wrote:
      >>> On Wed, 2004-01-14 at 14:42, Jon Green wrote:
      >>>>>If you do not want it then globally bind it to "void"
      >>>>>global-bind-key void "<key code>"
      >>> Any idea how I can tell what Key Code it is? Sorry for the simple
      >>> question, but I don't know.
      > M-x describe-key
      > Then hit the key giving you a problem.
      > Will display the key code that it received.
      > If there are multiple keys being sent in then
      > use:
      > M-x list-variables
      > and find the variable $recent-keys this
      > will show you all of the keys that
      > have come in recently. Trouble with
      > $recent-keys is that you have to type
      > keys to get to it. What I normally is
      > temporarily bind list variables to
      > a key i.e.
      > M-x global-bind-key<CR>
      > global bind:list-variables<CR>
      > to:<f9>
      > The binding should now be set up, now enter
      > the following sequence of keys.
      > <f9> - should get variable list with new binding.
      > <duff key> - strike duff key once
      > <f9> - should update the variable list
      > Your duff key codes will be between the two f9's
      > in the variable $recent-keys.
      > If there are multiple characters received then
      > use translate-key to turn them into nothing or
      > somethiong else. Could also use translate-key
      > to turn a single key into nothing - I think this
      > works - if it does translate key is better than
      > the void binding to get rid of the key.
      > Jon.
    Your message has been successfully submitted and would be delivered to recipients shortly.