Man page 1 : mmove

mmove - move or rename an MSDOS file or subdirectory
     .tr (is' .tr (if` .tr (pd"

This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the end of this man page for details.

The \fR\f(CWmmove\fR command is used to moves or renames an existing MS-DOS file or subdirectory.

\fR\f(CWmmove\fR [\fR\f(CW-v\fR] [\fR\f(CW-D\fR clash_option] sourcefile targetfile
\fR\f(CWmmove\fR [\fR\f(CW-v\fR]  [\fR\f(CW-D\fR clash_option] sourcefile [ sourcefiles... ] targetdirectory

\fR\f(CWMmove\fR moves or renames an existing MS-DOS file or subdirectory. Unlike the MS-DOS version of \fR\f(CWMOVE\fR, \fR\f(CWmmove\fR is able to move subdirectories. Files or directories can only be moved within one filesystem. Data cannot be moved from Dos to Unix or vice-versa. If you omit the drive letter from the target file or directory, the same letter as for the source is assumed. If you omit the drive letter from all parameters, drive a: is assumed by default.

Mtools' texinfo doc

This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate representation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.

• *   
      To generate a printable copy from the texinfo doc, run the following commands:

   ./configure; make dvi; dvips mtools.dvi

\fR

• *   
      To generate a html copy, run:

   ./configure; make html

\fRA premade html can be found at \fR\f(CW(ifhttp://www.gnu.org/software/mtools/manual/mtools.html(is\fR

• *   
      To generate an info copy (browsable using emacs' info mode), run:

   ./configure; make info

\fR

The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the quoting conventions used in info.