unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Kenichi Handa <handa@m17n.org>
Cc: 5275@debbugs.gnu.org
Subject: bug#5275: Malayalam file names not rendered correctly (conjuncts	are not formed) in message window and buffer title
Date: Fri, 15 Jan 2010 11:54:31 +0900	[thread overview]
Message-ID: <wlpr5culg8.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <tl7fx68qfdf.fsf@m17n.org>

[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]

>>>>> On Fri, 15 Jan 2010 11:19:24 +0900, Kenichi Handa <handa@m17n.org> said:

>> Though this is not reliably reproducible, mode-line display seems
>> to become unstable occasionally when the buffer name containing
>> composition is short and requires trailing padding spaces.

> I tried various buffer names but couldn't reproduce it.  What does
> "unstable" mean exactly?  When you reproduce it, please let me know
> the buffer name and which font is used for it.

Unfortunately, I couldn't reproduce it on GNU/Linux.  But the
following examples spontaneously fail with the X11 build on Mac OS X
10.5.

  (switch-to-buffer-other-window (string ?e 769))
  (switch-to-buffer-other-window (string ?e 769 ?e 769))
  (switch-to-buffer-other-window (string ?e 769 ?e 769 ?e 769))
  (switch-to-buffer-other-window (string ?e 769 ?e 769 ?e 769 ?e 769))
  (switch-to-buffer-other-window (string ?e 769 ?e 769 ?e 769 ?e 769 ?e 769))

  ;; The following one always succeeds.
  (switch-to-buffer-other-window (string ?e 769 ?e 769 ?e 769 ?e 769 ?e 769 ?e 769))

Sometimes the buffer name is rendered incorrectly (see the
attachment), and sometimes the mode line is not updated.  The latter
case often leads to crash afterwards.

The font used for the buffer name in the modeline is

  xft:-bitstream-Bank Gothic-normal-normal-normal-*-16-*-*-*-*-0-iso10646-1

I can see similar phenomena on the Mac port and also with ideographic
variation sequences.  So I don't think fonts or libotf is related to
this issue.

I suspect the problematic case is that `charpos + field_width' in
reseat_to_string exceeds the length of the given string.  The value of
`field_width' is 12 by default when displaying buffer names.

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp

[-- Attachment #2: modeline.png --]
[-- Type: image/png, Size: 3923 bytes --]

  reply	other threads:[~2010-01-15  2:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 11:30 bug#5275: Malayalam file names not rendered correctly (conjuncts are not formed) in message window and buffer title Praveen A
2010-01-08 12:58 ` Kenichi Handa
2010-01-14  4:06   ` Kenichi Handa
2010-01-14  8:50     ` YAMAMOTO Mitsuharu
2010-01-15  2:19       ` Kenichi Handa
2010-01-15  2:54         ` YAMAMOTO Mitsuharu [this message]
2010-01-15  5:29           ` Kenichi Handa
2010-01-15  5:51             ` YAMAMOTO Mitsuharu

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=wlpr5culg8.wl%mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=5275@debbugs.gnu.org \
    --cc=handa@m17n.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).