unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tak Kunihiro <homeros.misasa@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tak Kunihiro <homeros.misasa@gmail.com>,
	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:24:55 +0900	[thread overview]
Message-ID: <m1mtaw5f6g.fsf@misasa.okayama-u.ac.jp> (raw)
In-Reply-To: <83illlz0m7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 18 Sep 2022 08:56:48 +0300")

OK. Now I understand <delete> only deletes one letter.  Two spaces are
shown as one letter, as expected.

To have a distorted table soon after deletion of text is OK.

However, when two spaces are shown as one letter, point moves randomly
when I press <up>.  I cannot keep editing with this condition.

I show recipe to reproduce this situation. Is there a trick to move
point in expected way?

(defun emacs-bug-reproduce-45915 ()
  "Reproduce bug#45915."
  ;; (gnus-read-ephemeral-emacs-bug-group 45915)
  (interactive)
  (with-current-buffer (get-buffer-create "*temp buffer*")
    (erase-buffer)
    (require 'org)
    (orgtbl-mode 1)
    (insert (format "emacs-version: %s, org-version: %s\n" emacs-version org-version))
    (insert "| 1 |   |   |   |   |   |   |   |   |"))
  (switch-to-buffer-other-window "*temp buffer*")
  (execute-kbd-macro (kbd "M-< C-n C-f C-f"))
  (message "I will call #'org-table-copy-down.")
  (sit-for 2)
  (call-interactively #'org-table-copy-down)
  (sit-for 2)
  (message "I will hit <delete>.")
  (sit-for 2)
  (execute-kbd-macro (kbd "<delete>"))
  (message "One letter was deleted expectedly.")
  (sit-for 2)
  (message "I will hit <up>.")
  (sit-for 2)
  (execute-kbd-macro (kbd "<up>"))
  (message "Point moved unexpectedly."))
;;; (call-interactively 'emacs-bug-reproduce-45915)





  parent reply	other threads:[~2022-09-19  1:24 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
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 [this message]
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=m1mtaw5f6g.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).