Code cleanup (#201)

Code cleanup (#201)

Author: Sen-real

.vscodeignore

@@ -1,4 +1,5 @@
 .git/**
+.github/**
 .nyc_output/**
 .vscode/**
 .vscode-test/**
@@ -22,7 +23,9 @@ DevREADME.md
 Jenkinsfile
 pack.py
 winCompile.bat
+macCompile.sh
 package-lock.json
+publish.py
 tsconfig.json
 tslint.json
 utils/**

README.md

@@ -1,6 +1,6 @@
 # <span id="visual-studio-code-extension-for-autocad®-autolisp">Visual Studio Code Extension for AutoCAD® AutoLISP<span>
 
-[中文简体](#autocad®-autolisp-visual-studio-code-扩展)
+[简体中文](#autocad®-autolisp-visual-studio-code-扩展)
 
 This extension adds support for AutoCAD AutoLISP source (LSP) files to Visual Studio Code. It allows you to edit and debug your lisp programs with AutoCAD 2021.
 For information on creating lisp programs for AutoCAD with the AutoLISP programming language, see the:
@@ -40,7 +40,7 @@ Your feedback is highly appreciated! Should you have any suggestions, please cre
     * Find & Search in a project
 
 ## Getting started
-- Step 1. Install a supported AutoCAD release on your system. 
+- Step 1. Install a supported AutoCAD release on your system.
 - Step 2. Install this extension.
 - Step 3. Open a folder that contains the AutoLISP source (LSP) files you want to work on. Or open an Autolisp project file via VSCODE side bar.
 - Step 4. Open a LSP file to modify or debug.
@@ -59,7 +59,7 @@ Windows | Mac | Linux |
 ## How to use the extension
 To debug an AutoLISP source file:
 1.  Open a LSP file.
-2.  Click Run > Start Debugging (or press F5). 
+2.  Click Run > Start Debugging (or press F5).
 3.  Then choose one of the following debug configurations:
      * AutoLISP Debug: Launch – Launches a new instance of the AutoCAD application to debug the current LSP file.
      * AutoLISP Debug: Attach – Allows you to attach to a running instance of the AutoCAD application to debug the current LSP file.
@@ -87,16 +87,15 @@ Example (on Mac OS):
 For more information, see the [documentation online](https://www.autodesk.com/autolisp-extension).
 
 ## Notes
-
-1.	Other AutoLISP extensions may conflict with this extension. If you are unable to set a breakpoint in a LSP file or you can’t use the launch/attach debug configurations, you should disable or uninstall all other AutoLISP extensions.
-2.	When using this extension on Mac® OS, the "Launch Program" attribute in extension setting should be ".../AutoCAD &lt;release&gt;.app/Contents/MacOS/AutoCAD" rather than the absolute path of AutoCAD &lt;release&gt;.app.
-3.	For AutoCAD specialized toolsets or OEM-based products, the product name might not be the same as AutoCAD or acad.exe. To use this extension with those products, set the value of the "Launch Program" attribute in extension setting based on the product you want to debug with.
-4.	If you launch AutoCAD as an administrator, you should start Microsoft Visual Studio Code as an administrator as well. Otherwise, Microsoft Visual Studio Code will be unable to locate the AutoCAD process for attach debug.
+1.  Other AutoLISP extensions may conflict with this extension. If you are unable to set a breakpoint in a LSP file or you can’t use the launch/attach debug configurations, you should disable or uninstall all other AutoLISP extensions.
+2.  When using this extension on Mac® OS, the "Launch Program" attribute in extension setting should be ".../AutoCAD &lt;release&gt;.app/Contents/MacOS/AutoCAD" rather than the absolute path of AutoCAD &lt;release&gt;.app.
+3.  For AutoCAD specialized toolsets or OEM-based products, the product name might not be the same as AutoCAD or acad.exe. To use this extension with those products, set the value of the "Launch Program" attribute in extension setting based on the product you want to debug with.
+4.  If you launch AutoCAD as an administrator, you should start Microsoft Visual Studio Code as an administrator as well. Otherwise, Microsoft Visual Studio Code will be unable to locate the AutoCAD process for attach debug.
 
 ## Legal
 Visual Studio Code Extension for AutoCAD® AutoLISP © 2020 Autodesk, Inc. All rights reserved.
 
-### Privacy 
+### Privacy
 To learn more about Autodesk’s online and offline privacy practices, please see the [Autodesk Privacy Statement](https://www.autodesk.com/company/legal-notices-trademarks/privacy-statement).
 
 ### Trademarks
@@ -105,7 +104,6 @@ The license does not grant permission to use the trade names, trademarks, servic
 All other brand names, product names or trademarks belong to their respective holders.
 
 ### Third-Party Trademarks, Software Credits and Attributions
-
 See [here](NOTICE.md).
 
 # <span id="autocad®-autolisp-visual-studio-code-扩展">AutoCAD® AutoLISP Visual Studio Code 扩展</span>
@@ -206,19 +204,16 @@ See [here](NOTICE.md).
 3. 对于 AutoCAD 专用工具集或基于 OEM 的产品，产品名称可能与 AutoCAD 或 acad.exe 不同。要将此扩展用于这些产品，请根据要调试的产品在扩展设置中设置对应“Launch Program”的值。
 4. 如果以管理员身份启动 AutoCAD，则同样应以管理员身份启动 Microsoft Visual Studio Code。否则，Microsoft Visual Studio Code 将无法找到用于附加调试的 AutoCAD 进程。
 
-## 法律通告
-
-Visual Studio Code Extension for AutoCAD® AutoLISP © 版权所有 2020 Autodesk Inc. 保留所有权利。
-
-### 隐私
+## Legal
+Visual Studio Code Extension for AutoCAD® AutoLISP © 2020 Autodesk, Inc. All rights reserved.
 
-要了解有关 Autodesk 联机和脱机隐私文档的详细信息，请参见 [Autodesk 隐私声明](https://www.autodesk.com/company/legal-notices-trademarks/privacy-statement)。
+### Privacy
+To learn more about Autodesk’s online and offline privacy practices, please see the [Autodesk Privacy Statement](https://www.autodesk.com/company/legal-notices-trademarks/privacy-statement).
 
 ### Trademarks
 The license does not grant permission to use the trade names, trademarks, service marks, or product names of Autodesk, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of any notice file. Autodesk, the Autodesk logo, AutoCAD and AutoLISP are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk is not responsible for typographical or graphical errors that may appear in this document.
 
 All other brand names, product names or trademarks belong to their respective holders.
 
 ### Third-Party Trademarks, Software Credits and Attributions
-
-See [here](NOTICE.md).
+See [here](NOTICE.md).