> I see this as a bug in the man page to clarify this. Namely the
> default is FvwmConsole's resource is that of the terminal
> x-terminal-emulator points uses. Also clarify that the example
> resources were written for xterm with the -name FvwmConsole flag.
I figured that would be the likely outcome. That'd be okay by me. But see
below.
> > For now, my workaround is to simply run FvwmConsole with the -name
> > option explictly added to the commandline.
>
> I don't see this as a workaround, but how it should be handled in
> Debian. If you want FvwmConsole's terminal to use a different resource
> than your default terminal's resource for configuration, that is what
> the -name feature is for. You can also use it in conjunction with the
> -terminal option to ensure you are running a terminal that supports
> it.
I see it as a workaround because it requires explicit configuration where
none should be necessary. It seems obvious to me that one would want to
use a different configuration from one's normal terminal emulator, since
that's not really what's needed here. FvwmConsole simply needs some sort
of text widget with history and line editing and the ability to send a
finalized line to a listening program, which is only superficially similar
to a real terminal. That said, a terminal emulator is easy to repurpose.
However, it occurred to me that there might be another way to do this. I
discovered the RESOURCE_NAME environment variable, which I'd never used
before, but if I put
setenv("RESOURCE_NAME", "FvwmConsole", 1);
right before the execvp() call, it works perfectly, and should be
completely ignored by non-X11-toolkit programs. Using the environment
makes sense here, since the process tree involved here is extremely minimal
-- only FvwmConsoleC in addition to the terminal emulator, and it doesn't
care. In fact, I think this change (along with the one to remove -name)
might be worth sending upstream.
Thanks,
Danek
