xffm start terminal emulator

[edscott wilson garcia]

On Fri, 2003-07-18 at 15:45, Bernhard Walle wrote:
> On Fri, 18 Jul 2003 at 15:39 (-0500), edscott wilson garcia wrote:
> > On Fri, 2003-07-18 at 15:28, Bernhard Walle wrote:
> > > On Fri, 18 Jul 2003 at 20:46 (+0200), Bernhard Walle wrote:
> > > > On Fri, 18 Jul 2003 at 13:34 (-0500), edscott wilson garcia wrote:
> > > > > On Fri, 2003-07-18 at 12:56, Bernhard Walle wrote:
> > > > > > On Fri, 18 Jul 2003 at 11:15 (-0500), edscott wilson garcia wrote:
> > > > > > > On Fri, 2003-07-18 at 09:35, Bernhard Walle wrote:
> > > > > > > > On Fri, 18 Jul 2003 at 09:27 (-0500), edscott wilson garcia wrote:
> > > > > > > > > On Fri, 2003-07-18 at 04:12, Bernhard Walle wrote:
> > > > > > > > > > 
> > > > > > > > > > is there any way to prevent xffm to start the terminal emulator without
> > > > > > > > > > the -u8 option?
> > > > > > > > > 
> > > > > > > > >  Could you be more specific? I don't understand what you are talking
> > > > > > > > > about.
> > > > > > > > 
> > > > > > > > I just click on the Terminal icon in xffm and it starts my xterm with
> > > > > > > > "xterm +mesg -aw +cm +dc -j -rightbar -s -sb -u8 -wf -sl 1024".
> > > > > > > > (TERM in the settings is set to "xterm".)
> > > > > > > > 
> > > > > > > > Why all this options? Xffm should just start xterm.
> > > > > > > 
> > > > > > > If you want xffm just to start xterm, or to use any other options, just
> > > > > > > define it in the TERM environment variable with the xfce-mcs-manager.
> > > > > > > The reason of the default u8 option is to be consistent with gtk2 using
> > > > > > > utf-8. Here I'm just guessing what Olivier would prefer. 
> > > > > > 
> > > > > > I did this. In the xffm window it appears:
> > > > > > 
> > > > > >             Das Argument ist ungültig:TERM=xterm
> > > > > > In English: The argument is invalid:TERM=xterm
> > > > > 
> > > > > You get that if g_find_program_in_path("xterm") returns NULL or
> > > > > access(g_find_program_in_path("xterm"),X_OK)!=0 (in src/mcs-manager.c).
> > > > > Why does that happen on your system? 
> > > > 
> > > > It doesn't happen in general. I tried following test program:
> > > > 
> > > > #include <glib-2.0/glib.h>
> > > > #include <stdio.h>
> > > > #include <unistd.h>
> > > > 
> > > > int main (void){
> > > > 
> > > >         if (g_find_program_in_path("xterm") == NULL) {
> > > >                 printf("Returned NULL\n");
> > > >         } else {
> > > >                 printf("Returned not null\n");
> > > >                 if (access(g_find_program_in_path("xterm"),X_OK)==0) {
> > > >                         printf("Everything ok\n");
> > > >                 }
> > > >         }
> > > > 
> > > >         return 0;
> > > > }
> > > > 
> > > > [~] $ ./test 
> > > > Returned not null
> > > > Everything ok
> > > 
> > > Maybe the problem has something to do with the TERM crash, I applied the
> > > patch.
> > 
> > Do a CVS checkout and remove all previous versions. That should fix
> > things.
> 
> Couldn't you put a tarball online? Anonymous CVS on sourceforge is
> extremely slow and doesn't work really good at the moment.

I'm not in Mexico City until Tuesday, so my bandwidth is very reduced.
If you do cvs update it is much easier and faster since only modified
modules get downloaded.

> 
> And if I set this TERM to xterm, then xterm is started *without* any
> additional options? That's all what I want.

Or with any options you prefer. Or using a different terminal emulator
like gnome-terminal. 

regards

Edscott
> 
> 
> Regards,
> Bernhard