Re: New to Fortran on Win XP

On Dec 23, 7:15 pm, Sebastian Gallinat <sebastian.galli...@xxxxxxxx>
wrote:

In other words, programs written for a command line should be used from
the command line. Open a cmd.exe, change the directory to that of your
program, and then type "a.exe" (you may type the fully qualified path to
your a.exe also without changing the directory. Note, that the
directory, which you can see in cmd.exe is the working directory of your
program, so all your output files without a path are written in that
directory. You may also use some tricks like piping the output to a file
on the command line or getting input from a file, which looks like
"infile.data < a.exe > outfile data. So you can see, working on the
command line is very important). So you can see all of the output of
your a.exe in the command window, if the buffer of the window is big
enough (you can change the buffer size to a bigger one by clicking the
top-left icon and then click on the properties).

This was good advice about using cmd.exe . I suggest using cmd.exe
within an Emacs-like text editor such as XEmacs, which is free for
Windows (and all other operating systems). After opening XEmacs, one
types "M-x shell" in the minibuffer to start a session of cmd.exe that
runs within XEmacs. Then, all input and output from the command line
is saved in the XEmacs buffer. This is much more convenient than
working with the cmd.exe console directly.
.

Relevant Pages

  • plink from windows to linux under xemacs using ssh works great
    ... but I had trouble passing arguments ... I'm setting up my native-windows xemacs to do compiles on our linux ... the single forward quotes around the shell command line, ...
    (comp.security.ssh)
  • Re: New to Fortran on Win XP
    ... on the command line or getting input from a file, ... your a.exe in the command window, if the buffer of the window is big ... enough (you can change the buffer size to a bigger one by clicking the ... After opening XEmacs, one ...
    (comp.lang.fortran)
  • Re: Help! bash annoyingly kills background processes when xterm is closed
    ... >> ignored so that command can continue after you log out... ... > job control over xemacs, et. al., so a script here wouldn't really ... If you want xemacs to stay up use nohup, or better, start it from your ... window manager. ...
    (comp.unix.shell)
  • Re: Guillemets
    ... XEmacs waits for me to type a command that will be repeated 171 times. ... There may be a command to do what your Windows system does (or perhaps ... UTF-8.) ...
    (alt.usage.english)
  • Re: emacs-editing-mode not bound in BASH
    ... > I want to set my command line in BASH to behave like it was an xemacs ... > controls the functions I describe above) is not emacs. ...
    (comp.unix.shell)