search

chadliu23 / mozc

Automatically exported from code.google.com/p/mozc
0 stars 0 forks source link

mozc.el: candidates in overlay style are displayed sideways if header-line-format is non-nil #196

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set "mozc-candidate-style" to 'overlay
2. Set "header-line-format" to non-nil value
3. Type something and display candidates

Sample configuration is below.
(require 'mozc)
(setq default-input-method "japanese-mozc")
(setq mozc-candidate-style 'overlay)
(setq header-line-format "")

What is the expected output?
Candidates are displayed below. But all candidates are displayed sideways.
(Please see attached file)

What version of the product are you using? On what operating system?
I use r163 and I use Ubuntu 13.04 and Emacs 24.2. This problem is not
occured with Emacs 23.

Please provide any additional information below.
I think this issue is related to problem of following thread.

http://lists.gnu.org/archive/html/emacs-devel/2013-05/msg00068.html

Original issue reported on code.google.com by syo...@gmail.com on 13 Aug 2013 at 8:31

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by yukawa@google.com on 20 Sep 2013 at 10:11

GoogleCodeExporter commented 9 years ago 
From my investigation, the root cause was as follows.

On Emacs 24 with non-nil header-line-format, y offset returned by 
`posn-at-point' is relative to the text area not including the header line.  
However, `posn-at-x-y' takes y offset relative to the buffer area including the 
header line.

Before Emacs 24, both of `posn-at-point' and `posn-at-x-y' are relative to the 
buffer area including the header line.

Original comment by yukishi...@google.com on 1 Nov 2013 at 3:06

GoogleCodeExporter commented 9 years ago 
I confirmed with GNU Emacs team that the asymmetry between `posn-at-point' and 
`posn-at-x-y' is by design.

Original comment by yukishi...@google.com on 3 Nov 2013 at 6:03

GoogleCodeExporter commented 9 years ago

Original comment by yukishi...@google.com on 8 Jan 2014 at 5:26

GoogleCodeExporter commented 9 years ago 
Should be fixed in r192.

Original comment by yukawa@google.com on 16 May 2014 at 1:24