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

[Krzysztof KoÅciuszkiewicz <726898@xxxxxxxxxxxxxxxxxx>]

I agree with Peter here - it's the user script/config that relies on PWD
being set, not gschem itself.

** Changed in: geda
       Status: New => Invalid

-- 
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:
  Invalid

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