From: Eli Zaretskii <eliz@gnu.org>
To: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Cc: yantar92@gmail.com, homeros.misasa@gmail.com,
45915-done@debbugs.gnu.org, emacs-orgmode@gnu.org,
tkk@misasa.okayama-u.ac.jp
Subject: Re: bug#45915: 28.2; delete-char deletes two letters
Date: Fri, 23 Sep 2022 09:02:21 +0300 [thread overview]
Message-ID: <83iller5le.fsf@gnu.org> (raw)
In-Reply-To: <20220923.063658.703945866478584943.tkk@misasa.okayama-u.ac.jp> (message from Tak Kunihiro on Fri, 23 Sep 2022 06:36:58 +0900 (JST))
> Date: Fri, 23 Sep 2022 06:36:58 +0900 (JST)
> Cc: yantar92@gmail.com, homeros.misasa@gmail.com, 45915@debbugs.gnu.org,
> emacs-orgmode@gnu.org, tkk@misasa.okayama-u.ac.jp
> From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
>
> >>> 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.
Thanks, done.
prev parent reply other threads:[~2022-09-23 6:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210116.170134.789950463868688311.tkk@misasa.okayama-u.ac.jp>
2021-01-31 2:54 ` bug#45915: 27.1.91; deletechar distorts org-table Tak Kunihiro
2021-04-28 6:03 ` Bastien
2021-04-28 8:36 ` bug#45915: 27.2; " Tak Kunihiro
2021-10-11 0:45 ` bug#45915: 29.0.50; " Tak Kunihiro
2021-12-07 8:43 ` bug#45915: 28.0.90; " Tak Kunihiro
2021-12-19 12:53 ` Ihor Radchenko
2021-12-29 6:28 ` Tak Kunihiro
2022-04-30 4:00 ` Ihor Radchenko
2022-05-23 9:26 ` Tak Kunihiro
2022-05-23 9:55 ` Ihor Radchenko
2022-06-18 6:20 ` Ihor Radchenko
2022-04-30 4:00 ` Ihor Radchenko
2022-07-13 10:17 ` bug#45915: 28.1; delete-char deletes two letters Tak Kunihiro
2022-09-15 9:30 ` bug#45915: 28.2; " Tak Kunihiro
[not found] ` <m1v8pmu0d3.fsf@misasa.okayama-u.ac.jp>
[not found] ` <83bkre33pa.fsf@gnu.org>
[not found] ` <m2pmfuwgxh.fsf@misasa.okayama-u.ac.jp>
[not found] ` <83o7ve1c8a.fsf@gnu.org>
[not found] ` <m1a66x6xt0.fsf@misasa.okayama-u.ac.jp>
[not found] ` <83illlz0m7.fsf@gnu.org>
[not found] ` <83edw9yunz.fsf@gnu.org>
2022-09-22 12:03 ` Ihor Radchenko
2022-09-22 12:46 ` Eli Zaretskii
2022-09-22 21:36 ` Tak Kunihiro
2022-09-23 6:02 ` Eli Zaretskii [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83iller5le.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45915-done@debbugs.gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=homeros.misasa@gmail.com \
--cc=tkk@misasa.okayama-u.ac.jp \
--cc=yantar92@gmail.com \
/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/org-mode.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).