From: Leo Liu <sdl.web@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: How to use string-to/as-unibyte correctly?
Date: Sat, 25 Jun 2016 09:57:31 +0800 [thread overview]
Message-ID: <m1shw26nec.fsf@zeuss-MBP.lan> (raw)
In-Reply-To: 83bn2t5kwj.fsf@gnu.org
On 2016-06-22 17:59 +0300, Eli Zaretskii wrote:
> You mean, deprecating them? Patches to that effect are welcome.
Should we deprecate string-to/as-multibyte as well?
Leo
next prev parent reply other threads:[~2016-06-25 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 23:40 How to use string-to/as-unibyte correctly? Leo Liu
2016-06-21 0:56 ` Stefan Monnier
2016-06-22 3:33 ` Leo Liu
2016-06-22 7:49 ` Andreas Schwab
2016-06-26 2:02 ` Leo Liu
2016-06-22 14:59 ` Eli Zaretskii
2016-06-25 1:57 ` Leo Liu [this message]
2016-06-25 8:01 ` Eli Zaretskii
2016-06-21 2:36 ` Eli Zaretskii
2016-06-26 2:01 ` Leo Liu
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=m1shw26nec.fsf@zeuss-MBP.lan \
--to=sdl.web@gmail.com \
--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).