Talk:CONFIG.SYS - SET Statements: Difference between revisions

Latest revision as of 13:28, 22 November 2017

Organization Needed

This page needs some major reorganization and standards compliance. By standards compliance, I mean that we need to come up with a standards document as a formatting and style guide to bring some uniformity to the content. Of all the CSDP pages, I find this one the most poorly organized and least standard.

Examples of formatting guidelines would be:

Use of uppercase for all variables
Not using SET= in variable names
Proper indenting for usage in CONFIG.SYS
Layout of parameters sections
Devising some consistent means of identifying whether a given variable is system or program specific, and whether it is settable per-session or must be in the master environment

This is not an exhaustive list, but something of a start.

Environment variables

It's a huge task to bring some structure and usability to this content that was originally simply copy'n'pasted to here. Actually it's of no real use at all. First step could be to create a Category "Environment variable(s)" and put each into it. As CONFIG.SYS isn't the only place to alter the environment it becomes more confusing at all. I don't want to create myriads of stub articles here that are hard to maintain. A good practice would be to mock out everything that's not important for a running the base operating system to a temporary article. Please sign your message next time!--ak120 (talk) 00:51, 13 November 2017 (CET)

Martini (talk) 01:12, 13 November 2017 (CET) It will be good to create one example on one SET Statement that will represent the standard. After working on that we can go through the rest little by little on the free time.

I branched out UNZIPOPT for example. Martin, please mark your few byte edits in future as "minor edits". And only edit at section levels to avoid conflicts. It will improve the database performance massively. In case of a name space conflict "VARIABLE (Environment variable)" should be used IMHO.--ak120 (talk) 02:32, 13 November 2017 (CET)

Andreas, please update UNZIPOPT on how you will like the sample page for the SET STATEMENTS. I noticed that you have been changing my pages and not compliant with the UNZIPOPT page you set. Martini (talk) 12:28, 22 November 2017 (CET)

@@ Line 1: / Line 1: @@
-I think it should be added a new section at the begining called "SET: General tips".
+==Organization Needed==
-I wanted to add here the following:
+This page needs some major reorganization and standards compliance. By ''standards compliance'', I mean that we need to come up with a standards document as a formatting and style guide to bring some uniformity to the content. Of all the CSDP pages, I find this one the most poorly organized and least standard.
-You must note that this command behaves slightly different from it's behaviour in command line.
+Examples of formatting guidelines would be:
-So, when you issue the following comands in a OS/2 session:
+* Use of uppercase for all variables
+* Not using SET= in variable names
+* Proper indenting for usage in CONFIG.SYS
+* Layout of parameters sections
+* Devising some consistent means of identifying whether a given variable is system or program specific, and whether it is settable per-session or must be in the master environment
+This is not an exhaustive list, but something of a start.
-SET TEMP=C:\TMP
+== Environment variables ==
-SET TMP=%TEMP%
+It's a huge task to bring some structure and usability to this content that was originally simply copy'n'pasted to here. Actually it's of no real use at all. First step could be to create a Category "Environment variable(s)" and put each into it. As CONFIG.SYS isn't the only place to alter the environment it becomes more confusing at all. I don't want to create myriads of stub articles here that are hard to maintain. A good practice would be to mock out everything that's not important for a running the base operating system to a temporary article. Please sign your message next time!--[[User:Ak120|ak120]] ([[User talk:Ak120|talk]]) 00:51, 13 November 2017 (CET)
-you get:
+[[User:Martini|Martini]] ([[User talk:Martini|talk]]) 01:12, 13 November 2017 (CET) It will be good to create one example on one SET Statement that will represent the standard. After working on that we can go through the rest little by little on the free time.
+I branched out [[UNZIPOPT]] for example. Martin, please mark your few byte edits in future as "minor edits". And only edit at section levels to avoid conflicts. It will improve the database performance massively. In case of a name space conflict "VARIABLE (Environment variable)" should be used IMHO.--[[User:Ak120|ak120]] ([[User talk:Ak120|talk]]) 02:32, 13 November 2017 (CET)
-TEMP=C:\TMP
+Andreas, please update [[UNZIPOPT]] on how you will like the sample page for the SET STATEMENTS. I noticed that you have been changing my pages and not compliant with the [[UNZIPOPT]] page you set. [[User:Martini|Martini]] ([[User talk:Martini|talk]]) 12:28, 22 November 2017 (CET)
-TMP=C:\TMP
-But, if you add the same lines to config.sys:
-SET TEMP=C:\TMP
-SET TMP=%TEMP%
-you get:
-TEMP=C:\TMP
-TMP=%TEMP%
-but not TMP=C:\TMP. The enviroment variable TMP now has the value composed by the letters "%", "T", "E", "M", "P", "%".