#464 Environment variables in stored paths

open
nobody
core (195)
5
2013-03-17
2013-03-05
No

Especially for using jEdit as portable app, it would be nice to have environment variables expanded, when path strings are read from files like recent.xml and perspective.xml. Of course, to make it really useful, environment variable replacement should be done before storing paths to these files (which IMHO shouldn't be optional as for displaying paths).

Discussion

  • Alan Ezust

    Alan Ezust - 2013-03-05

    *All* path properties??? Or just some. And which ones?

    At the moment disabling the view option breaks the ProjectViewer option for storing variable-prefixed paths in the project properties.
    I have to come up with another API for plugins to use that is always going to work regardless of the view option.

     
  • Alan Ezust

    Alan Ezust - 2013-03-05
    • assigned_to: nobody --> ezust
     
  • Robert Schwenn

    Robert Schwenn - 2013-03-05

    I feared that a request for "all" path properties in "all" files couldn't have much success. That's why this request is mainly for *recent files list* and restoring *previously open files* at startup. I was hoping these things are core related only (recent.xml and perspective.xml).

     
  • Alan Ezust

    Alan Ezust - 2013-03-06

    I see you already said that in the initial description. Sounds reasonable to me.

     
  • Alan Ezust

    Alan Ezust - 2013-03-17

    recent.xml is easy. perspective.xml is tricky. Unassigning myself for now.
    I will reassign if I feel like mucking around in ugly splitconfig code.

     
  • Alan Ezust

    Alan Ezust - 2013-03-17
    • assigned_to: ezust --> nobody
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks