From: Tak Kunihiro <homeros.misasa@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tkk@misasa.okayama-u.ac.jp, yantar92@gmail.com, 45915@debbugs.gnu.org
Subject: bug#45915: 28.2; delete-char deletes two letters
Date: Mon, 19 Sep 2022 10:02:48 +0900 [thread overview]
Message-ID: <m1r1085g7b.fsf@misasa.okayama-u.ac.jp> (raw)
In-Reply-To: <83edw9yunz.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 18 Sep 2022 11:05:20 +0300")
> 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.
Function (org-table--align-field) in org-table.el sandwiches
text by org-table-separator-space as shown below.
(concat org-table-separator-space
prefix
field
suffix
- org-table-separator-space)))
+ (propertize org-table-separator-space 'display '(space :relative-width 1.001)))))
I confirmed that this modification works good.
>> I have an impression that default characters on
>> org-table-separator-space is problematic.
>
> What do you mean by "default characters"?
Let me take the statement back.
next prev parent reply other threads:[~2022-09-19 1:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 8:01 bug#45915: 27.1; deletechar distorts org-table Tak Kunihiro
2021-01-31 2:54 ` bug#45915: 27.1.91; " 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
2022-09-16 3:59 ` Ihor Radchenko
2022-09-17 3:48 ` Tak Kunihiro
2022-09-17 6:38 ` Eli Zaretskii
2022-09-17 8:20 ` Tak Kunihiro
2022-09-17 11:17 ` Eli Zaretskii
2022-09-18 5:44 ` Tak Kunihiro
2022-09-18 5:56 ` Eli Zaretskii
2022-09-18 8:05 ` Eli Zaretskii
2022-09-19 1:02 ` Tak Kunihiro [this message]
2022-09-22 12:03 ` Ihor Radchenko
2022-09-22 12:03 ` Ihor Radchenko
2022-09-22 12:46 ` Eli Zaretskii
2022-09-22 12:46 ` Eli Zaretskii
2022-09-22 21:36 ` Tak Kunihiro
2022-09-23 6:02 ` Eli Zaretskii
2022-09-23 6:02 ` Eli Zaretskii
2022-09-22 21:36 ` Tak Kunihiro
2022-09-19 1:24 ` Tak Kunihiro
2022-09-19 13:27 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1r1085g7b.fsf@misasa.okayama-u.ac.jp \
--to=homeros.misasa@gmail.com \
--cc=45915@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.