unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19347@debbugs.gnu.org, rms@gnu.org
Subject: bug#19347: 24.4.50; Display of bengali text
Date: Wed, 17 Dec 2014 21:02:53 +0100	[thread overview]
Message-ID: <87mw6m6o42.fsf@igel.home> (raw)
In-Reply-To: <83sigeuldc.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 17 Dec 2014 21:28:15 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Wed, 17 Dec 2014 10:44:24 -0500
>> From: Richard Stallman <rms@gnu.org>
>> CC: schwab@suse.de, 19347@debbugs.gnu.org
>> 
>> The 6 characters fill 7 columns with the blob that indicates a character
>> that can't be displayed.  This causes anomalies in cursor motion
>> within the line.
>> 
>> If the line is almost 80 characters, it overflows
>> the line on the terminal, causing vertical positioning anomalies too.
>> 
>> These consequences typically occur when text sent to the terminal
>> occupies more columns than Emacs expects it to occupy.
>
> Right.  Does it help to disable compositions?
>
>   M-x auto-composition-mode RET

Composition mode has no effect in a termcap frame.  I can see a similar
effect in emacs -nw running in Kconsole, because Konsole is apparently
doing composition on its own, causing the (uncomposed) characters no
longer occupy exactly one column.  Moving over such a composed (by the
terminal) character temporarily breaks up the composition.

But on the Linux console I'm only seeing replacement characters without
any display glitches.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





  reply	other threads:[~2014-12-17 20:02 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 12:56 bug#19347: 24.4.50; Display of bengali text Richard Stallman
2014-12-11 13:29 ` Andreas Schwab
2014-12-11 16:27   ` Eli Zaretskii
2014-12-12 16:41     ` Richard Stallman
2014-12-12 19:08       ` Eli Zaretskii
2014-12-13 12:46         ` Richard Stallman
2014-12-15  9:12 ` Andreas Schwab
2014-12-16  5:20   ` Richard Stallman
2014-12-16  8:35     ` Andreas Schwab
2014-12-16 14:10       ` Stefan Monnier
2014-12-17 15:44         ` Richard Stallman
2014-12-17 21:40           ` Stefan Monnier
2014-12-18  3:42             ` Eli Zaretskii
2014-12-18 14:27               ` Stefan Monnier
2014-12-18 15:57                 ` Wolfgang Jenkner
2014-12-19  7:18             ` Richard Stallman
2014-12-19 11:21               ` Andreas Schwab
2014-12-20  7:55                 ` Richard Stallman
2015-01-12  9:52                   ` Andreas Schwab
2014-12-17  3:31       ` Richard Stallman
2014-12-17  8:26         ` Andreas Schwab
2014-12-17 15:45           ` Richard Stallman
2014-12-17 16:04             ` Andreas Schwab
2014-12-16 15:35     ` Eli Zaretskii
2014-12-17 15:44       ` Richard Stallman
2014-12-17 16:03         ` Andreas Schwab
2014-12-18 11:24           ` Richard Stallman
2014-12-17 19:28         ` Eli Zaretskii
2014-12-17 20:02           ` Andreas Schwab [this message]
2014-12-18  3:43             ` Eli Zaretskii
2014-12-18 11:25           ` Richard Stallman
2014-12-18 16:19             ` Eli Zaretskii
2014-12-27 10:57             ` Eli Zaretskii
2014-12-27 22:55               ` Richard Stallman
2014-12-29 19:00                 ` Eli Zaretskii
2022-04-28 11:37                   ` Lars Ingebrigtsen

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=87mw6m6o42.fsf@igel.home \
    --to=schwab@suse.de \
    --cc=19347@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rms@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 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).