[scite] implementing "indentifier search" into SciTE
I would like to implement a search feature similar to the "go to definition" feature in many IDEs. Basically, what I have is an XML tag in an XML document (for example something like this) What I want is for the end user to be able to select, say, ThingTemplate="ControlPoint" and then select "go to definition" somehow (context menu option, hotkey, whatever makes most sense in SciTE). Then, code I will write searches for the relavent ThingTemplate (by parsing the XML files and looking for the relavent XML tag which has id="ControlPoint" in this case). In addition to the selected attribute, I also need to be able to access the entire contents of the currently open files I know C++ and don't mind getting my hands dirty with the SciTE codebase :) But if I can do what I need with the LUA interface, thats fine too. How hard would it be to add what I want to SciTE? ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
[scite] Syntax highlighting for kconfig
I do not know if this is the right place to start an inquiry like this, but I hope so: I often edit kconfig-like files, i.e. kernel-config-like - definition and - settings files. These are used by the Linux kernel as well as other projects like Buildroot, BusyBox and so forth. The menu definition files often have names like Config.in, the settings which are the output of a configuration run are often named .config. Has anybody created lexers and properties files for both types of files? I would be interested in gathering and using them. Thank you. -- Alexander Kriegisch ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Single instance and Director Extension in SciTEGTK
There seems to be some unnecessary entities. Looking at the set of properties mentioned in the DirectorExtension, ["ipc.director.name", "current.pid", "ipc.scite.name", "PipeName"] it appears that "PipeName" is just giving "ipc.scite.name" a default value so could go into ipc.scite.name (is there a property hierarchy issue here?). I don't see any use for "current.pid". AddSendPipe should error out a little more nicely by ignoring calls after s_send_cnt has reached MAX_PIPES. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] implementing "indentifier search" into SciTE
Jonathan Wilson: What I want is for the end user to be able to select, say, ThingTemplate="ControlPoint" and then select "go to definition" somehow How hard would it be to add what I want to SciTE? Its a simple matter of writing some Lua and attaching it to a command or menu item. There's plenty of example Lua code at http://lua-users.org/wiki/SciteScripts Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
