Re: Aterm catching console messages
David Mihm (davemann@ionet.net)
Fri, 9 Apr 1999 13:28:15 -0500 (CDT)
On Fri, 9 Apr 1999, Coplan wrote:
! I don't know how to solve _that_ particular problem...but I do have an
! alternative. Try setting a system wide alias for Startx as follows:
!
! startx='startx > ~/.xerrors 2>&1'
!
! This will pipe the output to a file ~/.xerrors. Then, in your autoexec
! file, load up aterm like such:
!
! Exec "I" aterm -T atail --geometry +0+0 -e tail -f ~/.xerrors
While this indeed does catch "messages", they are not console
messages. The best method is to direct the AfterStep messages (not to
~/.xerrors) to the console as well, thusly:
startx 2>&1 >/dev/console <-- for bassh type shells
startx >& >/dev/console <-- for *csh type shells
and then using the Exec line in autoexec:
Exec "I" aterm -T xconsole -n xconsole -C &
Use whatever geometry, transparency, and tinting option as well to suit
your needs
+--------------------------------------------------------------------+
| d a v i d @ m i h m reality.sys corrupt! |
| davemann @ ionet.net reboot universe(y,n)? |
| webmaster @ afterstep.org ICQ:906859 |
| ftpmaster @ afterstep.org www.the-site.loonybin.net |
+--------------------------------------------------------------------+
E4 90 15 ED E5 9F 18 8A B0 CC FF 68 61 36 4A 6F
--
WWW: http://www.afterstep.org/
FTP: ftp://ftp.afterstep.org/
MAIL: http://www.caldera.com/linuxcenter/forums/afterstep.html