unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tak Kunihiro <homeros.misasa@gmail.com>
To: yantar92@gmail.com, 45915@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Cc: tkk@misasa.okayama-u.ac.jp
Subject: bug#45915: 28.2; delete-char deletes two letters
Date: Sun, 18 Sep 2022 14:44:59 +0900	[thread overview]
Message-ID: <m1a66x6xt0.fsf@misasa.okayama-u.ac.jp> (raw)
In-Reply-To: <83o7ve1c8a.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Sep 2022 14:17:41 +0300")

>>   (buffer-substring (line-beginning-position) (line-end-position))
>> 
>> line 1 returns: "| 1 |"
>> line 2 returns: #("| 1 |" 1 2 (display (space :relative-width 1)) 3 4
>> (display (space :relative-width 1)))
>
> Those two 'display' properties are now displayed as a single stretch
> glyph, because two adjacent text properties with the same value are
> indistinguishable from a single one that spans all of the buffer
> positions.
>
> This is not a bug, this is how Emacs always worked.

I see. I understand that 'display' properties on an org-table matters.
I took a look for (org-table-align) and found that
`org-table-separator-space' defines the text properties as shown below.

org-table.el: (defconst org-table-separator-space
org-table.el:   (propertize " " 'display '(space :relative-width 1))
org-table.el:   "Space used around fields when aligning the table.
org-table.el: This space serves as a segment separator for the purposes of the
org-table.el: bidirectional reordering.")

Although I still do not understand the purpose of `:relative-width',
problem disappeared with following configuration.

  (with-eval-after-load "org-table"
    (setq org-table-separator-space " "))

I have an impression that default characters on
org-table-separator-space is problematic.





  reply	other threads:[~2022-09-18  5:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16  8:01 bug#45915: 27.1; deletechar distorts org-table Tak Kunihiro
     [not found] ` <m2k0rtak9x.fsf@misasa.okayama-u.ac.jp>
     [not found]   ` <87im477xpk.fsf@gnu.org>
     [not found]     ` <1AD1B9B7-5A15-4F86-9274-B04B83694C85@misasa.okayama-u.ac.jp>
     [not found]       ` <m135p8pey0.fsf_-_@misasa.okayama-u.ac.jp>
     [not found]         ` <m1zgpc7qkj.fsf_-_@misasa.okayama-u.ac.jp>
     [not found]           ` <877dc0sqm6.fsf@localhost>
     [not found]             ` <m1lf047wn9.fsf@misasa.okayama-u.ac.jp>
     [not found]               ` <87ilqrusnk.fsf@localhost>
     [not found]                 ` <m15yk1co5p.fsf_-_@misasa.okayama-u.ac.jp>
     [not found]                   ` <m1r10dj86u.fsf_-_@misasa.okayama-u.ac.jp>
2022-09-16  3:59                     ` bug#45915: 28.2; delete-char deletes two letters 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 [this message]
2022-09-18  5:56                               ` Eli Zaretskii
2022-09-18  8:05                                 ` Eli Zaretskii
2022-09-19  1:02                                   ` Tak Kunihiro
2022-09-22 12:03                                   ` Ihor Radchenko
     [not found]                                   ` <87sfkjaa50.fsf@localhost>
2022-09-22 12:46                                     ` Eli Zaretskii
2022-09-22 21:36                                       ` Tak Kunihiro
     [not found]                                       ` <20220923.063658.703945866478584943.tkk@misasa.okayama-u.ac.jp>
2022-09-23  6:02                                         ` Eli Zaretskii
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

  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=m1a66x6xt0.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 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).