From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: cursor moving bug
Date: Mon, 28 Feb 2005 12:58:06 +0100 [thread overview]
Message-ID: <m3acpoc2wh.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20050228.010023.245407976.wl@gnu.org> (Werner LEMBERG's message of "Mon, 28 Feb 2005 01:00:23 +0100 (CET)")
Werner LEMBERG <wl@gnu.org> writes:
>> Can you give a full procedure starting with emacs -Q that exhibits
>> the error.
>
> Execute this in a fresh buffer:
>
> (setq buffer-display-table (make-display-table))
>
> then copy
>
> SGVsbG8sDQogICBJIHdhbnQgdG8gYW5kIEdCMjMxMiB0byBhIGZvbnQgZmlsZSAuQnV0IEl0IGNh
> biBiZSB1c2VkIGJ5IHRoZSBmcmVldHlwZSAuSXQgcmV0dXJuIG1lIGEgNiB3aGVuIEkgdXNlIFNl
> bGVjdF9DaGFybWFwLiAgTWF5YmUgdGhlcmUgYXJlIHRoZSBvdGhlciByZWFzb24gLkNvdWxkIHlv
> dSB0ZWxsIG1lIHRoZSByZWFzb24gPyBUaGFuayB5b3UhT3IgLElmIHlvdSBrbm93IHNvbWUgZm9u
> dCB0aGF0IHN1cHBvcnQgZ2IyMzEyLHBsZWFzZSB0ZWxsIG1lIG9yIHNlbmQgbWUgYSBmb250IC5U
> aGFuayB5b3UgIQ0KDQo9ID0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0gPSA9ID0NCgkJ
> CQ0KDQqhoaGhoaGhoaGhoaGhoaGh1sINCsDxo6ENCiANCgkJCQkgDQqhoaGhoaGhoaGhoaGhoaGh
> 1cXRp8flDQqhoaGhoaGhoaGhoaGhoaGhemhhbmd4dWVxaW5nQGRhdndvcmxkLm5ldA0KoaGhoaGh
> oaGhoaGhoaGhoaGhoaEyMDA0LTA2LTAxDQoNCgoKDQoNCk5vIHZpcnVzIHdhcyBkZXRlY3RlZCBp
> biB0aGUgbWFpbC4NCg0KCgoNCg0KUG93ZXJlZCBieSBNZXNzYWdlU29mdCBTTUcgClNQQU0sIHZp
> cnVzLWZyZWUgYW5kIHNlY3VyZSBlbWFpbCAKaHR0cDovL3d3dy5tZXNzYWdlc29mdC5jb20gCg0K
>
> to the buffer and call `base64-decode-region'.
>
Sorry, but I still cannot reproduce it.
Is your CVS emacs up-to-date?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-02-28 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 5:25 cursor moving bug Werner LEMBERG
2005-02-27 22:12 ` Kim F. Storm
2005-02-28 0:00 ` Werner LEMBERG
2005-02-28 11:58 ` Kim F. Storm [this message]
2005-03-01 8:30 ` Werner LEMBERG
2005-03-01 9:31 ` Kim F. Storm
2005-02-28 0:20 ` Andreas Schwab
2005-02-28 0:33 ` Andreas Schwab
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=m3acpoc2wh.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
/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).