GNU bug report logs - #6401
Failure in loading charset map: JISX0208

Previous Next

Package: emacs;

Reported by: Sigve Berge Hofland <sigve <at> hofland.no>

Date: Fri, 11 Jun 2010 12:53:01 UTC

Severity: important

Fixed in version 24.2

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Glenn Morris <rgm <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 6401 <at> debbugs.gnu.org, tim <at> tenkan.org
Subject: bug#6401: 
Date: Tue, 22 Nov 2011 02:49:30 -0500
Eli Zaretskii wrote:

>> http://lists.gnu.org/archive/html/emacs-devel/2008-10/msg00432.html
>> 
>> I don't know if a solution was ever found for that.
>
> No solution was found, because I, like you, don't know what to do
> about it.  Emacs has no way of knowing whether EMACSDATA etc. is set
> for it or for some other Emacs.  So it cannot remove it from the
> environment when running subprocesses.  Maybe someone could come up
> with some clever idea.

If all else fails, we can at least write a PROBLEMS entry.
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?
Similar to the suggestion in emacs-devel, could configure unset
$EMACSDATA if $EMACS is set (which indicates it is running from an Emacs
shell)? Under what circusmtances would one want to set EMACSDATA when
building Emacs? Or could we replace the env-var with a --with-emacsdata
argument to configure instead? Then people who need the functionality
can still access it, and people who don't won't inadvertently get
affected by it.




This bug report was last modified 12 years and 319 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.