<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'><P>Hello, Arni.</P>
<P>You are wonderful. Your description below is great, and EXTREMELY helps me. I owe you a good Korean dish. Thank you VERY MUCH. Best, </P>
<P>Saang-Yoon<BR><BR></P>
<P>
<HR>
<P></P>
<P><B>From: </B>"Arni Magnusson" <arnima@hafro.is><BR><B>To: </B>users@admb-project.org<BR><B>Cc: </B>"Saang-Yoon Hyun" <shyun@umassd.edu><BR><B>Sent: </B>Tuesday, June 15, 2010 8:59:28 PM<BR><B>Subject: </B>Redirecting compilation output<BR><BR>Hi Saang-Yoon,<BR><BR>If you want to save the compilation output to text files, then you need to <BR>consider that there are two different kinds of output: standard output <BR>(stdout) and errors (stderr).<BR><BR>To take an example, start with simple.tpl and create a bug by inserting an <BR>extra space, so<BR><BR> init_vector Y(1,nobs)<BR><BR>becomes:<BR><BR> init_vector Y(1, nobs)<BR><BR>Now compile and redirect the standard output to 'one.txt' and errors to <BR>'two.txt':<BR><BR> admb simple > one.txt 2> two.txt<BR><BR>This is not new behavior. It works the same in Windows and Linux, and is <BR>not related to ADMB-IDE or the new compilation scripts. This behavior is <BR>in fact older than Windows and Linux.<BR><BR>If you want to do this from within Emacs, you can run shell-command, <BR>either by typing M-x shell-command (that's Alt-x) or by pressing M-! <BR>(that's Alt-Shift-1) and then type:<BR><BR> admb simple > one.txt 2> two.txt<BR><BR>If you find yourself using shell-command on a regular basis, it is easy to <BR>bind it to a more accessible keystroke, such as M-1 or the like. You can <BR>also open a shell inside Emacs using M-x shell, or just open a regular <BR>shell outside of Emacs.<BR><BR>If you want to redirect compilation output all the time, you could write a <BR>new function admb-build-redirect (almost identical to admb-build) and bind <BR>that to a keystroke like S-f8.<BR><BR>Emacs is designed for people like you, Saang-Yoon. Demanding customers.<BR><BR>Arni<BR><BR><BR><BR><BR><BR>On Tue, 15 Jun 2010, Saang-Yoon Hyun wrote:<BR><BR>> Hello, ADMB folks.<BR>><BR>> While I have been using ADMB-IDE, I find something different in compile <BR>> output. In older versions of ADMB, I used to print compile outputs <BR>> mainly to catch errors by using the following command in a DOS window <BR>> (i.e., Command window).<BR>><BR>> makadmb ABC > compileout.txt<BR>><BR>> where "makadmb" is compile-link command in an older version, "ABC" is a <BR>> TPL file, and "compileout.txt" is an arbitrary name. Then all outputs <BR>> including errors in CPP file (i.e., ABC.cpp) are shown in the <BR>> "compileout.txt" file.<BR>><BR>> In ADMB-IDE, I did the same thing like<BR>><BR>> admb ABC > compileout.txt<BR>><BR>> where "admb" is compile-link command in ADMB-IDE version. However, <BR>> outputs of errors in CPP file are never included in the "compileout.txt" <BR>> file. Interestingly all outputs only except errors in CPP file are shown <BR>> in the "compileout.txt" file.<BR>><BR>> What and how should I do to have the output file (compileout.txt) show <BR>> all errors as in before? I find that Emacs editor with ADMB-IDE shows <BR>> the error outputs, but I feel more comfortable with DOS commands. I <BR>> cannot open a DOS window directly from the Emacs editor, except for <BR>> "shell command". But the "shell command" in Emacs does not stay and <BR>> disappears after every command execution, thus the "shell command" does <BR>> not seem helpful to a person who like DOS commands.<BR>><BR>> I would greatly appreciate your advice.<BR>><BR>> Saang-Yoon<BR>></P></div></body></html>