From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: kai.grossjohann@uni-duisburg.de
Subject: Re: environment variable don't get coding conversion
Date: Mon, 27 Jan 2003 08:18:57 -0500 [thread overview]
Message-ID: <200301271318.h0RDIvB30264@rum.cs.yale.edu> (raw)
In-Reply-To: 1659-Sun26Jan2003191130+0200-eliz@is.elta.co.il
> > And what happens if you do (setenv foo bar) and bar is a string which
> > can't be encoded in the coding system specified for environment
> > variables?
What currently happens is that foo gets the internal (i.e. emacs-mule)
encoding of bar, which is more or less guaranteed to be the wrong thing
to do. So whatever change we make, it won't be much worse than the
current state of affairs.
We could of course require foo and bar to be unibyte strings so as to
force caller to do the encoding.
Stefan
next prev parent reply other threads:[~2003-01-27 13:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rzqadi1i9ka.fsf@albion.dl.ac.uk>
[not found] ` <200301170613.PAA12807@etlken.m17n.org>
2003-01-18 0:46 ` environment variable don't get coding conversion Richard Stallman
2003-01-20 0:38 ` Kenichi Handa
2003-01-20 16:46 ` Richard Stallman
2003-01-21 18:21 ` Dave Love
2003-01-23 7:59 ` Richard Stallman
2003-01-23 23:04 ` Dave Love
2003-01-25 19:22 ` Richard Stallman
2003-01-25 22:05 ` Ehud Karni
2003-01-26 14:41 ` Kai Großjohann
2003-01-26 16:11 ` Eli Zaretskii
2003-01-27 13:18 ` Stefan Monnier [this message]
2003-01-27 2:48 ` Kenichi Handa
2003-01-26 18:50 ` Dave Love
2003-01-27 2:31 ` Richard Stallman
2003-01-28 18:42 ` Dave Love
2003-01-26 18:22 ` Dave Love
2003-01-21 18:18 ` Dave Love
2003-01-23 8:00 ` Richard Stallman
2003-01-25 0:56 ` Kenichi Handa
2003-01-25 17:09 ` Eli Zaretskii
2003-01-26 15:36 ` Richard Stallman
2003-01-26 16:08 ` Eli Zaretskii
2003-01-27 17:41 ` Richard Stallman
2003-01-27 2:27 ` Kenichi Handa
2003-01-26 18:23 ` Dave Love
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=200301271318.h0RDIvB30264@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=kai.grossjohann@uni-duisburg.de \
/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).