From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] scratch/gnus-decoded f041412 1/7: Decode group names in newsrc files as raw-text, not utf-8
Date: Sat, 22 Jun 2019 08:45:10 -0700 [thread overview]
Message-ID: <874l4hzks9.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2imsykp56.fsf@linux-m68k.org> (Andreas Schwab's message of "Sat, 22 Jun 2019 10:20:05 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Jun 21 2019, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>> In scratch/gnus-decoded, the group name is the string "nnml:テスト". It
>> is written to newsrc with:
>>
>> (with-current-buffer buf
>> (insert "nnml:テスト")
>> (let ((coding-system-for-write 'raw-text))
>> (save-buffer)))
>>
>> And read with:
>>
>> (set-buffer (nnheader-find-file-noselect newsrc-file))
>> (setq group (read (current-buffer))
>> group (decode-coding-string
>> (symbol-name group) 'raw-text))
>
> The coding rules for symbols and strings are quite different. If you
> want read a symbol, you need to write a symbol.
Actually what I want is to read/write strings. The calls to `read' made
sense when group names were always symbols, but there isn't much point
to that now. I was leaving them on general principle -- smallest viable
change, etc -- but maybe I should just bite the bullet and switch to
buffer substrings.
Eric
prev parent reply other threads:[~2019-06-22 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190621205531.14822.22802@vcs0.savannah.gnu.org>
[not found] ` <20190621205533.D5EB520A01@vcs0.savannah.gnu.org>
2019-06-21 22:17 ` [Emacs-diffs] scratch/gnus-decoded f041412 1/7: Decode group names in newsrc files as raw-text, not utf-8 Stefan Monnier
2019-06-21 22:55 ` Eric Abrahamsen
2019-06-22 8:20 ` Andreas Schwab
2019-06-22 15:45 ` Eric Abrahamsen [this message]
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=874l4hzks9.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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).