On Fri, Apr 03, 1998 at 09:00:33AM -0500, Ossama Othman wrote:
(..)
> However, it is possible that the pstree will be longer then the number of
> lines in an xterm of default size (24 lines). What then? We can always
> increase the size of the xterm but that wouldn't be a solution since there
> i
On Fri, 3 Apr 1998, Ossama Othman wrote:
> Hi Greg,
>
> > I'd suggest to run `watch -n 10 pstree' in the xterm...
>
> I like that solution! I didn't know about the "watch" command. However,
> it is possible that the pstree will be longer then the number of lines in
> an xterm of default size (
Hi Greg,
> I'd suggest to run `watch -n 10 pstree' in the xterm...
I like that solution! I didn't know about the "watch" command. However,
it is possible that the pstree will be longer then the number of lines in
an xterm of default size (24 lines). What then? We can always increase
the size
On Fri, 3 Apr 1998, Ossama Othman wrote:
> Since pstree exits as soon as it has printed the process tree, is there
> any point to having fvwm* start up an xterm that will close very soon
> after it is opened? For example, I can never see the outout of pstree
> when running it from the fvwm* menus
On Fri, 3 Apr 1998, Ossama Othman wrote:
> Since pstree exits as soon as it has printed the process tree, is there
> any point to having fvwm* start up an xterm that will close very soon
> after it is opened? For example, I can never see the outout of pstree
> when running it from the fvwm* menus
Hi,
Since pstree exits as soon as it has printed the process tree, is there
any point to having fvwm* start up an xterm that will close very soon
after it is opened? For example, I can never see the outout of pstree
when running it from the fvwm* menus since the xterm it opens up just
closes too
6 matches
Mail list logo
