From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Why does using aset sometimes output raw bytes?
Date: Sun, 09 Dec 2018 16:46:01 +0100 [thread overview]
Message-ID: <87d0qaog92.fsf@gmx.net> (raw)
In-Reply-To: <83y38y3exe.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 09 Dec 2018 17:20:13 +0200")
On Sun, 09 Dec 2018 17:20:13 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> Here's what gets inserted into the buffer (I've represented the raw
>> bytes by ascii strings to make sure they're readable here):
>>
>> \344\366\374\337ſðđŋ
>> äöüßſðđŋ
>>
>> Is this expected, and if so, what's the explanation, i.e., why does this
>> happen with some non-ascii characters (e.g. äöüß) but not with others
>> (e.g ſðđŋ) and why does it happen when aset gets passed a variable
>> for the string but not when it gets passed the string itself?
>
> s0 and s2 originally include only pure ASCII characters, so they are
> unibyte strings. Try making them multibyte before using aset.
Thanks, that works. But why are raw bytes inserted only with some
multibyte strings (e.g. with "äöüß" but not with "ſðđŋ")? Also, is
there some way to ensure a string is handled as multibyte if it's not
known what characters it contains? E.g., s0 in my example sexp could be
bound to some string by a function call and before applying the function
it is not known if the string is multibyte; is there some way in Lisp to
say "treat the value of s0 as multibyte (regardless of what characters
it contains)"?
Steve Berman
next prev parent reply other threads:[~2018-12-09 15:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 15:16 Why does using aset sometimes output raw bytes? Stephen Berman
2018-12-09 15:20 ` Eli Zaretskii
2018-12-09 15:46 ` Stephen Berman [this message]
2018-12-09 15:56 ` Stephen Berman
2018-12-09 17:12 ` Eli Zaretskii
2018-12-09 17:32 ` Stephen Berman
2018-12-09 17:47 ` Eli Zaretskii
2018-12-09 18:50 ` Stephen Berman
2018-12-09 18:55 ` Eli Zaretskii
2018-12-09 17:10 ` Stefan Monnier
2018-12-09 17:20 ` Stephen Berman
2018-12-09 19:20 ` Stefan Monnier
2018-12-09 20:23 ` Eli Zaretskii
2018-12-09 21:20 ` Stefan Monnier
2018-12-10 5:59 ` Eli Zaretskii
2018-12-10 13:56 ` Stefan Monnier
2018-12-09 20:43 ` Stephen Berman
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=87d0qaog92.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).