all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 5989@debbugs.gnu.org
Subject: bug#5989: 23.1.96; bug 4209 not completely fixed (regression in re-search-forward)
Date: Sat, 04 Jun 2016 19:15:50 +0300	[thread overview]
Message-ID: <83eg8dudzd.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-9vQfDJWzfs5by+utv+76jWvqUbWSrec3cLE5njLcopYg@mail.gmail.com> (message from Noam Postavsky on Wed, 1 Jun 2016 21:29:36 -0400)

> Date: Wed, 1 Jun 2016 21:29:36 -0400
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> 
> I can reproduce this on recent Emacs, with a small change to the
> recipe since enable-multibyte-characters can no longer be set
> directly:
> 
> (set-buffer (get-buffer-create "*Test Buffer*"))
> (set-buffer-multibyte nil) ; instead of setting `enable-multibyte-characters'
> 
> (insert "\xC2\x4C\xEF\x77\xC6\x69\x8C\x0A")
> 
> (goto-char (point-min))
> 
> (message "looking-at: %s" (looking-at
> "\\`\xC2\x4C\xEF\x77\xC6\x69\x8C\x0A"))
> 
> (message "re-search-forward: %s"
>          (re-search-forward "\\`\xC2\x4C\xEF\x77\xC6\x69\x8C\x0A" 100 t))

If you don't make the buffer unibyte, everything works as expected.
Using multibyte buffers even for raw bytes is what we recommend.  So I
see no problem here that we should work on: unibyte buffers are not
meant to process text.

Thanks.





  reply	other threads:[~2016-06-04 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 18:19 bug#5989: 23.1.96; bug 4209 not completely fixed (regression in re-search-forward) Christopher J. Madsen
2016-06-02  1:29 ` Noam Postavsky
2016-06-04 16:15   ` Eli Zaretskii [this message]
2016-06-04 16:51     ` Noam Postavsky

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83eg8dudzd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=5989@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.