From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 6401@debbugs.gnu.org, tim@tenkan.org
Subject: bug#6401:
Date: Tue, 22 Nov 2011 12:29:58 -0500 [thread overview]
Message-ID: <w7r510vze1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1RSlqX-00087N-22@fencepost.gnu.org> (Eli Zaretskii's message of "Tue, 22 Nov 2011 03:36:53 -0500")
Eli Zaretskii wrote:
>> Why does a --with-ns build actually need to set these env-vars for child
>> processes?
>> Could they specifically be unset in spawned M-x shells?
>
> How will Emacs know that these variables weren't set by the parent
> shell?
I'm ignorant of all this. What do child processes of Emacs need these
variables for? Can you give me one example of something I might want to
run inside an emacs M-x shell buffer that needs to know EMACSDATA? It's
not set in shells spawned by a GNU/Linux build.
Also, don't you get a clear error about the charsets directory not being
found if EMACSDATA is wrong (from init_charset), rather than a failue to
load some particular charset? Which makes me think this is probably not
the problem the OP was having anyway...
next prev parent reply other threads:[~2011-11-22 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 11:53 bug#6401: Failure in loading charset map: JISX0208 Sigve Berge Hofland
2011-05-24 16:30 ` bug#6401: Sigve Berge Hofland
2011-07-02 1:01 ` bug#6401: Glenn Morris
2011-11-21 2:33 ` bug#6401: Tim Daly Jr.
2011-11-21 23:31 ` bug#6401: Glenn Morris
2011-11-22 5:38 ` bug#6401: Eli Zaretskii
2011-11-22 7:49 ` bug#6401: Glenn Morris
2011-11-22 8:36 ` bug#6401: Eli Zaretskii
2011-11-22 17:29 ` Glenn Morris [this message]
2011-11-22 17:34 ` bug#6401: Tim Daly Jr.
2011-11-22 17:42 ` bug#6401: Glenn Morris
2011-11-22 22:15 ` bug#6401: Glenn Morris
2012-07-10 1:06 ` bug#6401: Failure in loading charset map: JISX0208 Glenn Morris
2011-11-22 18:08 ` bug#6401: Eli Zaretskii
2011-11-22 17:32 ` bug#6401: Glenn Morris
2011-11-22 18:09 ` bug#6401: Eli Zaretskii
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=w7r510vze1.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=6401@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tim@tenkan.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).