Am Donnerstag, 1. März 2007 23:08:36 schrieb Neil Hodgson: > Stefan Schwendeler implemented the directory properties feature > discussed in January. A single SciTEDirectory.properties file sets > options for the directory it is in and its subdirectories. A > simplified version of his code can be downloaded from > > http://scintilla.sourceforge.net/scite.zip Source > http://scintilla.sourceforge.net/wscite.zip Windows executable
Great this is really fantastic. Thank you both so much for this great work. > To use this feature, it must first be turned on with > properties.directory.enable=1 (should probably be renamed to > properties.directory for consistency). Whenever a file is opened or > switched to, directory properties are read as well as local > properties. The directory properties file is called > SciTEDirectory.properties and is opened from the same directory as the > file being opened or switched to. If there is no > SciTEDirectory.properties file in that directory then the parent > directory is checked and so forth up the path until > SciTEDirectory.properties is found or the root is reached. Seems perfectly logic to me. I have just tested it on gtk and it works nearly as i expected. The only thing that seems a little bit odd to me is that the working directory is not switched to SciTEDirectory.properties directory if a command defined there is executed. I am not shure if this would really cleaner or better because we could get the same effect using build tools like rake etc.. So it seems at least not really important, because we could execute project specific scripts through project specific tasks in build files, which is mostly no real overhead. > I found the behaviour a little strange. If there is no active > directory properties file then the Open Directory Options File command > opens one in the same directory as the current file. This is the most > obvious behaviour but I normally expect that the file will go into a > parent directory. > > The code is not committed to CVS yet as I'm not certain about it. I can understand your point, because in most projects most files lieing in sub-directories. On the other hand README and build files lieing more often on projects top-level-directory. I really would prefer the more obvious approach, because this a "once per project" task. kind of regards, Holger _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
