From: Eli Zaretskii <eliz@is.elta.co.il>
Subject: Re: decode-coding-string and consing
Date: Tue, 11 Feb 2003 08:32:40 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1030211083119.25449E-100000@is> (raw)
In-Reply-To: <m3el6f2464.fsf@defun.localdomain>
On Mon, 10 Feb 2003, Jesper Harder wrote:
> >> Under what conditions is the decoding operation "trivial"?
> >
> > If CODING-SYSTEM is nil or such that no encoding is necessary at all.
>
> But I don't understand why any encoding is needed at all in:
>
> (decode-coding-string "abc" 'us-ascii t)
Why did you use us-ascii at all here? It's not really a coding system.
Why not nil or raw-text?
Anyway, is there some real problem behind this discussion?
next prev parent reply other threads:[~2003-02-11 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 16:47 decode-coding-string and consing Jesper Harder
2003-02-10 20:01 ` Eli Zaretskii
[not found] ` <mailman.1748.1044907500.21513.help-gnu-emacs@gnu.org>
2003-02-10 21:53 ` Jesper Harder
2003-02-11 6:32 ` Eli Zaretskii [this message]
[not found] <mailman.1774.1044945196.21513.help-gnu-emacs@gnu.org>
2003-02-11 17:26 ` Jesper Harder
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=Pine.SUN.3.91.1030211083119.25449E-100000@is \
--to=eliz@is.elta.co.il \
/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).