From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: environment variable don't get coding conversion
Date: Sun, 26 Jan 2003 15:41:39 +0100 [thread overview]
Message-ID: <84r8b07z30.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 200301252205.h0PM5gsx029853@beta.mvs.co.il
"Ehud Karni" <ehud@unix.mvs.co.il> writes:
> I agree that to use non-ASCII environment variable name is not
> practical, so this problem is not really important, but the non-ASCII
> values are used a lot, and the practical way for ISO-8859-x is to
> have them in unibyte.
I guess the most important question is: which coding system is used
for values of environment variables? Emacs already has a number of
different coding systems; it's not clear to me which one of them, if
any, is appropriate for environment variables.
process-coding-system? file-name-coding-system?
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?
--
Ambibibentists unite!
next prev parent reply other threads:[~2003-01-26 14: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 [this message]
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
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=84r8b07z30.fsf@lucy.is.informatik.uni-duisburg.de \
--to=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 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.