#225 Set location for .marker files / as with backup files

v5.2
closed
nobody
core (195)
6
2013-12-09
2008-05-22
Jonas Felix
No

There are a lot of projects, companys and other environments where it's bad to place files with meta information directly where the original file is.

So it would great to serve an alternative storage point for marker fields.

Discussion

  • Alan Ezust

    Alan Ezust - 2008-05-23

    Logged In: YES
    user_id=935841
    Originator: NO

    That has my vote too.

     
  • Alan Ezust

    Alan Ezust - 2008-05-23
    • priority: 5 --> 6
     
  • Matthieu Casanova

    Logged In: YES
    user_id=285591
    Originator: NO

    This is a good idea but how to store them ?
    Like the backups ? But if I remove a file, the marker will remains here, how to cleanup this folder ?

     
  • Dale Anson

    Dale Anson - 2008-05-24

    Logged In: YES
    user_id=187628
    Originator: NO

    The BufferLocal plugin has similar functionality for buffer local properties. Maybe code from it could be leveraged to help in this request?

     
  • Anonymous - 2009-03-20

    You can try the MarkerSets plugin, which is a new plugin that supports sets of markers. The plugin provides its own marker objects, which are different from jEdit markers but operate similarly. In addition, you can assign different colors to different sets of markers, and see all of the markers of each set grouped together. The marker sets are stored in a single xml file, located in the settings directory. Does this provide what you're requesting?

     
  • Anonymous - 2009-09-18
    • status: open --> pending
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending --> closed
     

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

Sign up for the SourceForge newsletter:





No, thanks