unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 11199@debbugs.gnu.org
Subject: bug#11199: 24.0.95; killing right-to-left text at eob leads to inconsistent state
Date: Sun, 08 Apr 2012 10:33:28 +0300	[thread overview]
Message-ID: <83bon2ad9z.fsf@gnu.org> (raw)
In-Reply-To: <wlk41r7yce.wl%mituharu@math.s.chiba-u.ac.jp>

> Date: Sun, 08 Apr 2012 11:26:41 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> 
> Steps to reproduce:
> 
> 1. emacs -Q
> 2. type the following text in the *scratch* buffer:
> 
>   (progn
>     (delete-region (point) (point-max))
>     (insert (substring (get-language-info "Hebrew" 'sample-text) 7)))
> 
> 3. move the cursor to the beginning of the next line of the above text.
> 4. C-x C-e
> 5. C-a
> 6. C-k
> 
> Result:
> 
> The Hebrew text is still shown, though it is internally killed.
> Typing C-p after the last step does not move the cursor.

I cannot reproduce this with today's bzr, neither in the emacs-24
release branch nor with the trunk version.  I cannot run a GUI session
with a GTK build on GNU/Linux where I'm typing this, but I tried GUI
and TTY sessions on MS-Windows and a TTY session on GNU/Linux, and
they all work correctly: the Hebrew text is killed and C-p works as
expected.  (Btw, did you mean C-p or C-n?)

Can you try reproducing this in a clean build, or on another system?

Also, what happens on the system where you see the problem, if you
switch to another buffer and then back to *scratch*, so that it is
completely redrawn? does the killed text re-appear or not?

Thanks.





  reply	other threads:[~2012-04-08  7:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-08  2:26 bug#11199: 24.0.95; killing right-to-left text at eob leads to inconsistent state YAMAMOTO Mitsuharu
2012-04-08  7:33 ` Eli Zaretskii [this message]
2012-04-08 18:28   ` Michael Welsh Duggan
2012-04-08 18:33     ` Michael Welsh Duggan
2012-04-08 20:03     ` Eli Zaretskii
2012-04-08 20:13       ` Eli Zaretskii
2012-04-08 20:19         ` Michael Welsh Duggan
2012-04-08 20:16       ` Michael Welsh Duggan
2012-04-08 20:20         ` Eli Zaretskii
2012-04-08 20:25           ` Michael Welsh Duggan
2012-04-08 20:37             ` Eli Zaretskii
2012-04-08 20:48               ` Eli Zaretskii
2012-04-08 21:01                 ` Michael Welsh Duggan
2012-04-08 21:10                   ` Eli Zaretskii
2012-04-08 21:17                     ` Michael Welsh Duggan
2012-04-09  6:24                       ` Eli Zaretskii
2012-04-08 20:49               ` Michael Welsh Duggan
2012-04-08 21:07                 ` Eli Zaretskii
2012-04-09  8:21                   ` YAMAMOTO Mitsuharu
2012-04-09  9:32                     ` Eli Zaretskii
2012-04-09  9:10             ` Eli Zaretskii
2012-04-09  9:48               ` YAMAMOTO Mitsuharu
2012-04-09 10:17                 ` Eli Zaretskii
2012-04-09 11:07                   ` Eli Zaretskii
2012-04-09 11:52                     ` Eli Zaretskii
2012-04-09 12:18                       ` Michael Welsh Duggan
2012-04-09 12:34                         ` Eli Zaretskii
2012-04-09 23:50                           ` YAMAMOTO Mitsuharu
2012-04-10  6: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=83bon2ad9z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11199@debbugs.gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).