Re: pkg/46804: Emacs Load Path issues when using emacs-nox11 w/ other packages such as flim, semi, and skk

[David Holland <dholland-pbugs%netbsd.org@localhost>]

The following reply was made to PR pkg/46804; it has been noted by GNATS.

From: David Holland <dholland-pbugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/46804: Emacs Load Path issues when using emacs-nox11 w/
 other packages such as flim, semi, and skk
Date: Wed, 22 Aug 2012 08:46:29 +0000

 On Wed, Aug 22, 2012 at 08:40:05AM +0000, OBATA Akio wrote:
  >  >  That doesn't work with emacs20 :(
  >  > % emacs -q -batch -f eval '(print load-path)' --no-site-lisp
  >  >  Wrong number of arguments: #<subr eval>, 0
  >  >  %
  >  
  >  How about following instead?
  >    emacs -q -batch -eval '(print load-path)' --no-site-lisp
 
 Also need to remove --no-site-lisp; then it works.
 
 emacs23 produces the same behavior, btw.
 
  >  >  Wouldn't a better solution to be to define EMACSLOADPATH when building
  >  >  emacs, add it to BUILD_DEFS so it's in +BUILD_INFO, and fetch it back
  >  >  with pkg_info -B?
  >  
  >  Packages don't know about default EMACSLOADPATH of built emacs.
 
 I don't understand the objection. Isn't it easier to define
 EMACSLOADPATH correctly in each of the emacs packages (which can be
 version-specific) than to try to extract it afterwards?
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost