Q32033: Preventing Generation of Tabs in the Edited Disk Files

Article: Q32033
Product(s): See article
Version(s): 1.00   | 1.00
Operating System(s): MS-DOS | OS/2
Keyword(s): ENDUSER | | mspl13_basic
Last Modified: 25-JUL-1988

It is impossible to search for a tab or replace a string with a tab
in the M editor.
   When a file is being edited, there are no tab characters in the
file. When the M editor reads from disk to memory, it converts tabs to
spaces. When it writes from memory to disk, it converts spaces to tabs
(unless you set the ENTAB switch to 0).
   This may create problems when devices other than your machine
access the file. For example, if you edit a source file on your IBM PC
with the M editor, then try to compile the source file on a mainframe,
the source file may not compile because of the tabs in the disk file
created by the M editor.
   The solution is to set ENTAB to 0 in the TOOLS.INI file; this value
will prevent tabs from being used to represent white space when
writing from memory to disk.
   For more information on the ENTAB switch, please refer to Table 7.2
on Page 59 of the "Microsoft Editor User's Guide."

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.