From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: environment variable don't get coding conversion
Date: Mon, 27 Jan 2003 12:41:34 -0500 [thread overview]
Message-ID: <E18dDGI-0007if-00@fencepost.gnu.org> (raw)
In-Reply-To: <1438-Sun26Jan2003190850+0200-eliz@is.elta.co.il>
Does it really have to be more reliable than what we do with users'
precious files?
Since it can easily be 100% reliable, it should be.
In any case, at least we should IMHO consider whether getenv and
setenv need to decode and encode the environment variables' values.
That's exactly what I've suggested. That can do the user-level part
of this job in a way that cannot interfere with inheritance.
I recommend using locale-coding-system.
> 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.
That is a good idea too. It shouldn't take much text to do this.
next prev parent reply other threads:[~2003-01-27 17:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 12:05 environment variable don't get coding conversion Dave Love
2003-01-17 6:13 ` Kenichi Handa
2003-01-18 0:46 ` 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
2003-01-27 17:41 ` Richard Stallman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E18dDGI-0007if-00@fencepost.gnu.org \
--to=rms@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.