From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#5080: indic text is not displayed correctly in emacs shell Date: Wed, 18 Nov 2020 18:52:02 -0800 Message-ID: References: <3f2beab60911300543l2436ff3ar8e5b5124db9db218@mail.gmail.com> <4B149E53.7060106@redhat.com> <4B14AC18.6070308@redhat.com> <3f2beab60912010132s2fee9301k4aad7f151b195629@mail.gmail.com> <4B14FB8B.1040801@redhat.com> <4B176B1C.4040507@redhat.com> <3f2beab60912030407o5609514bidc65538848064e4@mail.gmail.com> <3f2beab60912120741n7651670as1c532d3865efbc23@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3306"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Praveen A , psatpute@redhat.com, 5080-done@debbugs.gnu.org, Parag Nemade , Kenichi Handa To: Lars Magne Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Nov 19 03:53:14 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kfa4P-0000je-RN for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 Nov 2020 03:53:13 +0100 Original-Received: from localhost ([::1]:39430 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kfa4O-00029M-MP for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 18 Nov 2020 21:53:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57504) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfa4F-00027k-Gc for bug-gnu-emacs@gnu.org; Wed, 18 Nov 2020 21:53:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54053) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kfa4E-0002jh-Rr for bug-gnu-emacs@gnu.org; Wed, 18 Nov 2020 21:53:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kfa4E-0005ZE-RS for bug-gnu-emacs@gnu.org; Wed, 18 Nov 2020 21:53:02 -0500 Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Thu, 19 Nov 2020 02:53:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 5080 X-GNU-PR-Package: emacs Mail-Followup-To: 5080@debbugs.gnu.org, stefan@marxist.se, pravi.a@gmail.com Original-Received: via spool by 5080-done@debbugs.gnu.org id=D5080.160575433221314 (code D ref 5080); Thu, 19 Nov 2020 02:53:02 +0000 Original-Received: (at 5080-done) by debbugs.gnu.org; 19 Nov 2020 02:52:12 +0000 Original-Received: from localhost ([127.0.0.1]:37361 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kfa3P-0005Xh-Q9 for submit@debbugs.gnu.org; Wed, 18 Nov 2020 21:52:12 -0500 Original-Received: from mail-ed1-f47.google.com ([209.85.208.47]:41155) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kfa3N-0005XH-16 for 5080-done@debbugs.gnu.org; Wed, 18 Nov 2020 21:52:10 -0500 Original-Received: by mail-ed1-f47.google.com with SMTP id t9so4234613edq.8 for <5080-done@debbugs.gnu.org>; Wed, 18 Nov 2020 18:52:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:user-agent :mime-version:date:message-id:subject:to:cc; bh=KUfu/9WpNpjsmQeubExTG1y50qVVNbV+03KxIkB0c+I=; b=I4JDM6ELq5c2CcRO5CmZuh2KC3lmoTvIz8uynoB2SrQBoavMgh3ukjHN+s+4UxbcV/ 1JccZYLCKDn4JRVoQ6YiJlXqovXwpYn+TxzJPtrSU8uikCQXcP0SlbiwwAUPBKo0iQOy KpOhXn8hQ8tzu3605qWOquATjqnicQHRizlMR0QBzZQjX3gJje53HjW2ySSVbJv9QWbf KeDtTuOqXaclmnYJUCUxLRQruGb1pTHX58TlSPc7BcjK2UD84fbMXRhF0lvBaBzAP774 6l8I/O+P5yzEK4wKn4683JceeVw1iQ28Khg3IEIiA7BolBP8JNhURqVMwBMCkEMt10JH 2wGQ== X-Gm-Message-State: AOAM532LlnVMqzyXHBed4Iw/1w8B6E7wYYv84IOvTpEE99dK2dvKnAEo rh1Err8hJ4TCQLjLSdi1OFUVdI2S2BdBFm3ViFI= X-Google-Smtp-Source: ABdhPJxGZaNTNDc5ZLMiSbXedSXcLEmvzCeNwcWCw6xeybfGYUi084LSfzK/Dhi05LgqdK6SaIjQMzS+f7pitTcUeQg= X-Received: by 2002:a50:bb25:: with SMTP id y34mr28052969ede.249.1605754323359; Wed, 18 Nov 2020 18:52:03 -0800 (PST) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Wed, 18 Nov 2020 18:52:02 -0800 In-Reply-To: (Stefan Kangas's message of "Wed, 12 Aug 2020 19:04:57 -0700") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:193675 Archived-At: Stefan Kangas writes: > Lars Magne Ingebrigtsen writes: > >> Praveen A writes: >> >>>> (4a) Why is it taking Lohit Malayalam by default >>>> (4b) Why is the display cluttered/overlapped with some fonts like Meera >>> >>> 4b is now resolved, details in >>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5146 >>> >>> Now only remaining issue in the list is about selecting default font. >>> I think it should be taken from fc-match :lang=ml >> >> As far as I can tell from this thread, all the bugs were resolved, >> except possibly this one. >> >> Is this still a problem in Emacs 24? > > That was 9 years ago. Now that Emacs 27.1 is out, with harfbuzz support > and many other changes, could you please try again and see if you are > still seeing any errors? > > FWIW, I tried quickly inserting indic text into a shell-mode buffer and > couldn't see anything wrong with it at a glance. (But my inspection may > be overly superficial I can't read the script.) > > Thanks in advance. More information was requested, but none was given within 14 weeks, so I'm closing this bug. If this is still an issue, please reply to this email (use "Reply to all" in your email client) and we can reopen the bug report.