Steve Donovan wrote:
>That's what I think - named pipes are so easy, you don't need a higher
>degree or special equipment ;) Although controlling a remote instance
>of SciTE might be entertaining, it wouldn't be high on most people's
>list of piorities. But, it's true, pipes are global. I was thinking
>whether it's not better to put the pipes in some local user directory
>like ~/.scite or something.
I finally decided that I like what you've done. You're right, let's keep
pipes, because they're easy to use and we can stay backward compatible.
I don't think we need to put them in another place that the current temp
directory. I'm working right now on making the single instance code use
the director interface unless NO_FILER is defined. I'll submit some
suggestions about the director extension when I'm done.
I also tracked down the bug that you encountered in scite-gdb, when you
had several extender: command passed into you ProcessChunk() function
at once. It wasn't actually a bug in SciTE. You need to end your
messages with a new line to ensure they're parsed as separate commands.
Here's the fix:
void scite_exec(const char* fun, const char* buff)
{
*outbuf = '\0';
strcpy(outbuf,"extender:");
strcat(outbuf,fun);
strcat(outbuf," ");
slashify(outbuf + strlen(outbuf),buff,0);
strcat(outbuf, "\n");
scite_interface(outbuf);
}
(in unix-spawner.c)
(BTW, it's detail, but you might want to always use either spaces or
tabs in your files, not mix them, and also strip trailing spaces)
Nicolas
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
