From: Eli Zaretskii <eliz@gnu.org>
To: Tak Kunihiro <homeros.misasa@gmail.com>
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 16:27:09 +0300 [thread overview]
Message-ID: <83wn9zxzo2.fsf@gnu.org> (raw)
In-Reply-To: <m1mtaw5f6g.fsf@misasa.okayama-u.ac.jp> (message from Tak Kunihiro on Mon, 19 Sep 2022 10:24:55 +0900)
> From: Tak Kunihiro <homeros.misasa@gmail.com>
> Cc: Tak Kunihiro <homeros.misasa@gmail.com>, yantar92@gmail.com,
> 45915@debbugs.gnu.org
> Cc: tkk@misasa.okayama-u.ac.jp
> Date: Mon, 19 Sep 2022 10:24:55 +0900
>
> 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?
This is an unrelated bug, now fixed on the master branch.
(A workaround is to press C-f or <RIGHT> before <UP>.)
prev parent reply other threads:[~2022-09-19 13:27 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
2022-09-19 13:27 ` 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.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=83wn9zxzo2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45915@debbugs.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.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).