From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: environment variable don't get coding conversion
Date: Sun, 26 Jan 2003 19:08:50 +0300 [thread overview]
Message-ID: <1438-Sun26Jan2003190850+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <E18coq6-0001RI-00@fencepost.gnu.org> (message from Richard Stallman on Sun, 26 Jan 2003 10:36:54 -0500)
> From: Richard Stallman <rms@gnu.org>
> Date: Sun, 26 Jan 2003 10:36:54 -0500
>
> This would be true ordinarily, but here there is a more important
> factor. The usual thing to do with environment variables is to pass
> them through. Making sure that is solidly reliable is the highest
> priority for environment variables.
Does it really have to be more reliable than what we do with users'
precious files? I'm not sure I see why the reliability of launching
subprocesses is more important than potential loss of information due
to incorrect decoding and encoding of user files.
In any case, at least we should IMHO consider whether getenv and
setenv need to decode and encode the environment variables' values.
> Therefore we have to leave these strings in their original format.
If this is the final decision, we probably should tell Lisp
programmers (in the ELisp manual) how to deal with such unibyte
strings in text processing.
next prev parent reply other threads:[~2003-01-26 16:08 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
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 [this message]
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=1438-Sun26Jan2003190850+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--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).