More than one way to do things. I was trying to do it the difficult way.
fg %xemacs works perfectly. As a learning experience for me, why would it be doomed to failure in a script?
Thanks
Chris
-----Original Message-----
From: Mike McNally [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 06, 2000 1:29 PM
To: '[EMAIL PROTECTED]'
Subject: RE: jobs, fg, awk, oh, my
Are you trying to write a script to foreground your "xemacs" session? If so
you're doomed to failure. Write it as a bash function and stick in your
startup file (.bashrc? I'm not a bash user).
Note that you can also do
fg %xemacs
without having to start up any extra processes.
(Because its glance inspired the distance which separates the shortest path)
Mike McNally -- [EMAIL PROTECTED]
-----Original Message-----
From: Mulcahy, Chris [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 06, 2000 1:08 PM
To: '[EMAIL PROTECTED]'
Subject: jobs, fg, awk, oh, my
Greetings all!
Any idea why this (line wrapping probable):
---> SNIP <---
#/bin/bash
fg `jobs | awk '/xemacs/ {printf("%s\n", substr($1, 2, 1));}'`
---> SNIP <---
returns:
---> SNIP <---
fg: no job control
---> SNIP <---
instead of switching me to the currently running xemacs session?
Thanks!
Chris
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
