gEDA-bug: [Bug 726898] Re: gentenv PWD does not work in gnome desktop environment

[Peter TB Brett <726898@xxxxxxxxxxxxxxxxxx>]

The getenv function is supposed to access the environment. If the
environment isn't set up properly for gschem to run or in accordance
with what the gschem user is expecting, that's a bug in whatever
launched gschem, not a bug in gschem.

I note however that there are some example and testsuite Scheme scripts
that use (getenv "PWD"). The examples should probably be changed, but
since the testsuite isn't ever going to be launched from a desktop
environment I'm not particularly upset by allowing it to rely on $PWD
being set correctly.

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/726898

Title:
  gentenv PWD does not work in gnome desktop environment

Status in GPL Electronic Design Automation tools:
  New

Bug description:
  If gschem is started from the file manager nautilus, the string
  (getenv "PWD") is not interpreted properly.

  To reproduce:

  1) Put a gafrc with these lines in a working directory:
        (define current-working-directory (getenv "PWD"))
        (component-library current-working-directory)
        (source-library  current-working-directory)

  2)  copy a symbol to the working directory and rename it to local.sym

  3) open gschem on the command line

  4) add the local symbol local.sym to the schematic. Add some symbols
  from the default library.

  5) save schematic and close gschem

  6) browse nautilus to the working directory

  7) double click the saved schematic

  gschem starts, but can't find the symbol local.sym . The symbols from
  the default library are rendered fine, though.

  Workaround:
     (define current-working-directory ".")
  This loads local symbols fine.

  ---<)kaimartin(>----


_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug