From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tak Kunihiro Newsgroups: gmane.emacs.bugs Subject: bug#45915: 28.2; delete-char deletes two letters Date: Fri, 23 Sep 2022 06:36:58 +0900 (JST) Message-ID: <20220923.063658.703945866478584943.tkk__40013.388036617$1663882704$gmane$org@misasa.okayama-u.ac.jp> References: <83edw9yunz.fsf@gnu.org> <87sfkjaa50.fsf@localhost> <83czbnshjw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11682"; mail-complaints-to="usenet@ciao.gmane.io" Cc: homeros.misasa@gmail.com, tkk@misasa.okayama-u.ac.jp, emacs-orgmode@gnu.org, yantar92@gmail.com, 45915@debbugs.gnu.org To: eliz@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 22 23:38:18 2022 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 1obTth-0002pM-Ux for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 22 Sep 2022 23:38:17 +0200 Original-Received: from localhost ([::1]:59562 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1obTtg-0001r5-V5 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 22 Sep 2022 17:38:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33516) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1obTtS-0001pc-MS for bug-gnu-emacs@gnu.org; Thu, 22 Sep 2022 17:38:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39650) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1obTtS-00054d-7Y for bug-gnu-emacs@gnu.org; Thu, 22 Sep 2022 17:38:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1obTtR-0002KG-Se for bug-gnu-emacs@gnu.org; Thu, 22 Sep 2022 17:38:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Tak Kunihiro Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 22 Sep 2022 21:38:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 45915 X-GNU-PR-Package: emacs Original-Received: via spool by 45915-submit@debbugs.gnu.org id=B45915.16638826288879 (code B ref 45915); Thu, 22 Sep 2022 21:38:01 +0000 Original-Received: (at 45915) by debbugs.gnu.org; 22 Sep 2022 21:37:08 +0000 Original-Received: from localhost ([127.0.0.1]:38728 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1obTsa-0002J9-8n for submit@debbugs.gnu.org; Thu, 22 Sep 2022 17:37:08 -0400 Original-Received: from jlsv301.okayama-u.ac.jp ([150.46.12.5]:51018) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1obTsU-0002Ig-Q3 for 45915@debbugs.gnu.org; Thu, 22 Sep 2022 17:37:07 -0400 Original-Received: from localhost (vesta.misasa.okayama-u.ac.jp [150.46.48.154]) by jlsv301.okayama-u.ac.jp (Postfix) with ESMTPSA id 1F41C7609DF; Fri, 23 Sep 2022 06:36:59 +0900 (JST) In-Reply-To: <83czbnshjw.fsf@gnu.org> X-Mailer: Mew version 6.8 on Emacs 28.2 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:243442 Archived-At: >>> One other possibility is to use a slightly different :relative-width >>> factor for the two spaces in a table cell: one with the value of 1, >>> the other with 1.001 (say). They will be indistinguishable on >>> display, but since the values are not equal, both stretch gfyphs will >>> be displayed, not just one. >> >> This is a good idea. I used it to fix the reported issue. >> >> Fixed on main. > > Great. So I guess this bug report can be closed? Nice. Yes, please close this bug report.