🚀 go-pugleaf

--> On Tue, 4 Aug 1992 15:40:50 GMT, kinstrey@plato.rdrc.rpi.edu (Michael Kinstrey) said:

  /michael/ I compiled Epoch4.0p2 on an HP730 with no problems.
  /michael/ Everything seems to work just fine, except when starting
  /michael/ up epoch with a filename argument. If I "cd" to a
  /michael/ subdirectory below my HOME directory, and start epoch with
  /michael/ a filename argument (which exists in that subdirectory),
  /michael/ epoch comes up with a blank buffer saying that <filename>
  /michael/ is NEW. What gives? If I use find-file, it loads fine.
  /michael/ Also, when the new buffer is created, the find-file
  /michael/ directory prompt in the minibuffer starts at the HOME
  /michael/ path, not the subdirectory path epoch was started from.

  /michael/ This behavior happens in epoch AND the ascii-version of
  /michael/ epoch.

  /michael/ Does Epoch/Emacs use an environment variable or something
  /michael/ to load files? I've never seen this happen on any other
  /michael/ machine type.

This is a problem with broken shells.  Emacs (and Epoch) uses the PWD
environment variable to determine the default directory upon startup,
and many shells (notably csh) fail to maintain this variable when you
move to a new directory.

Marc

--
Marc Andreessen
Epoch Development Team
University of Illinois at Urbana-Champaign
marca@ncsa.uiuc.edu