From: Chong Yidong <cyd@stupidchicken.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>,
Jason Rumney <jasonr@gnu.org>
Cc: 38@emacsbugs.donarmstrong.com, emacs-devel@gnu.org
Subject: Re: No coding system used for environment variables
Date: Wed, 23 Jul 2008 20:01:54 -0400 [thread overview]
Message-ID: <87y73s1765.fsf@stupidchicken.com> (raw)
> It seems there is no coding system applied to values of environment
> variables.
What's the current situation with this bug? Jason's patch was reverted,
but nothing else seems to have been done after that.
Two objections were made to Jason's patch: (i) some coding systems are
not ready until some .elc files get loaded (relevant for special cases,
such as the EMACS_LOAD_PATH variable), and (ii) DECODE_FILE causes GC,
so variables such as `nm' in Fexpand_file_name may not point to valid
data after that.
If no elegant solution is forthcoming, I'd suggest simply documenting
(i) as a limitation, and dealing with (ii) by simply turning off GC in
the affected part of the function.
I noticed that the patch posted at
http://lists.gnu.org/archive/html/emacs-pretest-bug/2007-05/msg00115.html
has not been checked into the trunk either.
next reply other threads:[~2008-07-24 0:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 0:01 Chong Yidong [this message]
2008-07-24 0:10 ` No coding system used for environment variables Jason Rumney
2008-07-24 0:30 ` bug#38: " Chong Yidong
2008-07-24 0:30 ` Chong Yidong
2008-07-24 0:10 ` bug#38: " Jason Rumney
-- strict thread matches above, loose matches on Subject: below --
2008-02-21 21:40 Göran Uddeborg
2008-03-05 0:40 ` Jason Rumney
2008-03-05 2:22 ` YAMAMOTO Mitsuharu
2008-03-05 8:57 ` Jason Rumney
2008-03-05 9:16 ` YAMAMOTO Mitsuharu
2008-03-05 10:11 ` Jason Rumney
2008-03-05 11:00 ` YAMAMOTO Mitsuharu
2008-03-05 10:34 ` Andreas Schwab
2008-03-05 16:25 ` Stefan Monnier
2008-03-07 12:12 ` YAMAMOTO Mitsuharu
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=87y73s1765.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=38@emacsbugs.donarmstrong.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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.