all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Subject: emacs XIM question
Date: 08 Jan 2003 18:25:00 +0900	[thread overview]
Message-ID: <buo4r8kxac3.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)

I'm trying out the `kinput2' input server with emacs.  It generally
seems to work pretty well, but there's one glitch I'm wondering about:

kinput2 displays its not-yet-sent-to-the-application text with an
underline, and the text it displays is shifted upwards compared to
subsequent client display by one pixel, which is the same as the
thickness of the underline.

What I'm wondering is, is this a bug with kinput2 -- should it locating
its display window one pixel down to account for the underline
thickness -- or is this an off-by-one error in the coordinates emacs
sends to kinput2.

The coordinates emacs sends as the `spot location' to kinput2 are the
x,y coordinates of the top of the cursor + the default font's ascent
added to the y coordinate (this looks pretty bad if your inputing in a
location with non-default fonts, incidentally; perhaps there's a
better way to calculate the font baseline to send to the input manager).

Here's a simple picture:

   -- displayed by emacs -- -- kinput2 text --
                            #   #        # #
    #   #        # #        #   #   ###  # #  ###
    #   #   ###  # #  ###   #####  #   # # # #   #
    #####  #   # # # #   #  #   #  ####  # # #   #
    #   #  ####  # # #   #  #   #  #     # # #   #
    #   #  #     # # #   #  #   #   #### # #  ###
    #   #   #### # #  ###   #######################

after kinput2 sends the text to emacs, it's of course displayed properly.

Thanks,

-Miles
--
自らを空にして、心を開く時、道は開かれる

             reply	other threads:[~2003-01-08  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08  9:25 Miles Bader [this message]
2003-01-15 12:38 ` emacs XIM question Kenichi Handa
2003-01-23  4:35   ` Miles Bader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=buo4r8kxac3.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=miles@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.