Re: [cssed-devel] cssed-vte-plugin
Brought to you by:
iagorubio
From: Iago R. <iag...@hi...> - 2004-10-10 11:54:18
|
On Sat, 2004-10-09 at 23:36, Mich=C3=A8le Garoche wrote: > Le 9 oct. 2004, =C3=A0 23:23, Iago Rubio a =C3=A9crit : >=20 > > On Sat, 2004-10-09 at 15:44, Mich=C3=A8le Garoche wrote: > >> The vte plugin seems very interesting. When using with the > >> --with-terminal option of cssed, you get two terminals. It seems to > >> work fine, though could you confirm it does make any harm to have both > >> enabled: a terminal via cssed and the plugin terminal loaded? > > > > No harm at all. They share the same code - I mean is tested - but I > > ripped out the vte functions and wrote it down in the plugins code to > > avoid clashes - instead of calling cssed functions from the plugin's > > code that could lead on clashes between both terminal windows. > Oh, perfect, I wondered actually this very thing. >=20 > So, what do you think I must do: let the --with terminal option or no=20 > in the Mac version? It's up to you. I don't ship the terminal in binary Linux builds to avoid one dependency - somewhat stupid as the vte is in most Gtk enabled systems - but it's in your hands to think if it's better in Mac to ship the built-in terminal - as you've been doing - or not. > Only a small problem is if you have the terminal option and the plugin,=20 > both terminals are called console. What do you think about it? Should=20 > not they be called differently? In the C fallback one is "Terminal" and other "Console" ;) In the Spanish translation I've got the same "Terminal" y "Consola". I know I must find better names, but right now they've got this little difference to know which is the plugin's one (in fact the plugin's one is always the last one, if both are enabled). > I'll test the release versions in a few minutes. Great. > Mich=C3=A8le --=20 Iago Rubio =20 - Home page * http://www.iagorubio.com=20 - Last project * http://cssed.sourceforge.net =20 - GPG Keyserv * pgp.rediris.es id=3D0x909BD4DD |