Steve Youngs <steve@xxxxxxxx> writes:
> I was just thinking (a very dangerous pastime I know), that it'd be
> nice to be able to control more of XWEM from a gnuclient session in a
> console. For those times when things go belly up.
>
> What I'd like to be able to do is:
>
> In a gnuclient session on another console, be able to switch to an
> ordinary SXEmacs buffer that was a "representation" of an XWEM client,
> for example, an XTerm. And then from that buffer, be able to send
> things to the actual client, like a SIGKILL, SIGTERM, etc.
>
> Crap ASCII art of how I see it looking:
>
> +--------------------------------------------+
> | XWEM Client Buffer |
> | ================== |
> | |
> | Client: Mozilla |
> | Uptime: 3 days, 14 hours, 10 minutes |
> | |
> | Send a signal to this client with: |
> | |
> | M-x xwem-tty-signal-client RET SIGNAL RET |
> | |
> | SIGNAL can be one of: |
> | kill term abort hup |
> | |
> | Killing this buffer will kill the XWEM |
> | client that it represents. |
> +--------------------------------------------+
>
> ...it was just an idle thought. :-)
All of this will be in interactive xwem (ixwem), if it will be written
ever :). But i'm sure it will be
--
XWEM - Your kids will be proud.
|