Am Freitag, 29. Dezember 2006 01:00 schrieb Neil Hodgson: > Holger Kohnen: > > if i am working on a project i normally > > have a file(ant etc.) which allows me to build and test > > the whole project. if i want command.go to launch that > > file i have to create SciTE.properties(local option files) > > files in any folder of my project. The other way would be > > to set the command.go in the user option file for the > > required filetypes. Both ways are not nice, for the first > > you have to create files redundantly and for the second you > > have to change global settings just for one project. > > You may install SciTE once for each project so that there are > different global properties for each project.
This would solve my problem on windows but on linux scite looks in /usr/share/scite for it's global properties. > Project builds can be approached by standardising the > compile/build/go commands to either understand the project structure > themselves or invoke wrappers that understand project structures. Some > build tools (IIRC, scons and jam) will search upwards for build > settings from the invocation directory. =) Oh yes, thank you, that solves my problem the easy way > > :::solution one::: > > > > enable a new action: "Rerun last command.go"(Shift + F5). > > The last command can be rerun in the output pane by entering ">" > and pressing Enter. Yes, i know, but a shortcut would fit it more ;-) Not really important to me anymore. > > enable a new type of option-file. the "directory option file". > > this file would be searched by walking the path upwards. > > defined launched configurations should be run in "directory > > option files" directory. > > Problems with walking up the path include time spent opening files, > parent directories being on other machines and having different > ownership and permissions, unexpected files being applied since it is > harder to reason about where a setting is when there are more places. > If this was included, it would have to be an option and there would > need to be a clear decision on how they are combined (I'd expect lower > file settings to override upper). Ok, i see the problem and the need that such a feature have disabled to be by default. What i like about SciTEDir.properties is that they would enable us to inject project specific features to scite tools menu. So for example project specific generation or test scripts could lunched easily from any developer on that project using scite. The options could look something like the following: dir.properties.enable=yes|no dir.properties.lower.override.upper=yes|no I really like to see this feature implemented, hopefully is there someone who wants that feature too and wants to implement that, or are i am the only one who misses that feature? kind of regards, Holger > > Neil > _______________________________________________ > Scite-interest mailing list > [email protected] > http://mailman.lyra.org/mailman/listinfo/scite-interest _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
