From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 53260@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#53260: char-syntax differs in interpreter and bytecode [PATCH]
Date: Thu, 20 Jan 2022 10:30:23 +0100 [thread overview]
Message-ID: <87y23a4uvk.fsf@gnus.org> (raw)
In-Reply-To: <AE02E5D0-BB58-4112-8DC6-A1B14CD35B11@acm.org> ("Mattias Engdegård"'s message of "Sun, 16 Jan 2022 12:04:51 +0100")
Mattias Engdegård <mattiase@acm.org> writes:
> Sure, I'm happy to do it either way. Chars retrieved from unibyte
> buffers or strings really should be converted to multibyte before used
> with char-syntax; unibyte buffers are not very common but strings
> slightly more so.
Makes sense to me. Unless Stefan has any further comments, please go
ahead and push.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-01-20 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 16:43 bug#53260: char-syntax differs in interpreter and bytecode Mattias Engdegård
2022-01-15 8:36 ` Lars Ingebrigtsen
2022-01-15 14:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-15 17:29 ` Mattias Engdegård
2022-01-15 17:57 ` Eli Zaretskii
2022-01-15 22:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-16 11:04 ` bug#53260: char-syntax differs in interpreter and bytecode [PATCH] Mattias Engdegård
2022-01-20 9:30 ` Lars Ingebrigtsen [this message]
2022-01-20 10:47 ` Mattias Engdegård
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=87y23a4uvk.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53260@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
/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).