调整NppAutoIndent，还是有一个很好的可自定义替代方法? [英] Tweaking NppAutoIndent, or is there a good customizable alternative?

问题描述

我最近开始为Notepad ++使用NppAutoIndent插件，并且对Smart Indent模式非常满意，但是我发现它缺乏可自定义的首选项很烦人，因为我希望在Smart Indent模式下有一些行为进行调整/修改.我考虑过修改插件的源代码并重新编译以尝试获得所需的行为，但是我拥有Visual Studio 2010和

I recently started using the NppAutoIndent plugin for Notepad++, and have been fairly pleased with the Smart Indent mode, but I find its lack of customizable preferences to be annoying as there are a few behaviors in Smart Indent mode that I'd like to tweak/modify. I thought about modifying the plugin's source code and recompiling it to try to get the behavior I want, but I have Visual Studio 2010 and the project for the plugin seems to be a VS 2003 project, and as I'm a complete beginner to using Visual Studio for C/C++ projects I don't even know where to start to deal with some of the warnings given when converting the project to VS 2010.

简而言之:NppAutoIndent插件是否有更可定制的替代方案，还是有更好的方法来更新VS 2010的源项目?

In short: Is there a more customizable alternative to the NppAutoIndent plugin, or is there a better way to update the source project for VS 2010?

更新:

以下是大多数警告.其中许多似乎并不重要，但我不确定需要注意哪些.

Here are most of the warnings. A lot of them seem to be unimportant, but I'm not sure which may be necessary to pay attention to.

• 由于C/C ++编译器的异常处理开关有所更改，因此/EHsc在此项目中已自动转换为/EHa.
• 已完成转换为新项目文件'C:[...] \ NppAutoIndent \ project \ NppAutoIndent.vcxproj'.
• 由于Visual C ++项目必须生成嵌入式(默认情况下)Windows SxS清单，因此现在可以使用清单工具自动构建项目中的清单文件.您可能需要更改构建以使其正常工作.例如，建议将任何清单文件中包含的依赖项信息转换为源代码中包含的头文件中的"#pragma comment(linker，").如果您的项目已经通过资源(.rc)文件在RT_MANIFEST资源部分中嵌入了清单，则可能需要先注释掉该行，然后项目才能正确构建.
• 由于C ++编译器中的一致性更改，可能需要更改代码，然后才能正确构建项目. C ++编译器的早期版本允许按成员函数名称(例如MemberFunctionName)指定成员函数指针. C ++标准要求使用地址运算符(例如& ClassName :: MemberFunctionName)使用标准名称.如果您的项目包含Windows窗体设计器中使用的窗体或控件，则可能必须更改InitializeComponent中的代码，因为设计器生成的代码在委托构造(事件处理程序中使用)中使用了不一致的语法.
• 此应用程序已更新，包括与Windows Vista的用户帐户控制(UAC)功能相关的设置.默认情况下，在启用了UAC的Windows Vista上运行时，此应用程序被标记为以与启动它的进程相同的特权运行.此标记还会使应用程序无法通过虚拟化运行.您可以从项目的属性页"更改与UAC相关的设置.
此版本不支持'VCCLCompilerTool'的
• 属性'Detect64BitPortabilityProblems'，并且在转换期间已将其删除.
• 不再支持VCWebServiceProxyGeneratorTool.该工具已从项目设置中删除.
• C/C ++编译器开关/Og已被弃用，并已从项目设置中删除.建议您改用/O1或/O2.
• VCConvertEngine无法在工具VCCLCompilerTool下转换属性GlobalOptimizations = TRUE.
此版本不支持'VCCLCompilerTool'的
• 属性'Detect64BitPortabilityProblems'，并且在转换期间已将其删除.
此版本不支持
• 'VCLinkerTool'的'OptimizeForWindows98'属性，并且在转换过程中已将其删除.
• VCConvertEngine无法在工具VCCLCompilerTool下转换属性GlobalOptimizations = TRUE.
此版本不支持'VCCLCompilerTool'的
• 属性'Detect64BitPortabilityProblems'，并且在转换过程中已将其删除.
此版本不支持
• 'VCLinkerTool'的'OptimizeForWindows98'属性，并且在转换过程中已将其删除.
此版本不支持'VCCLCompilerTool'的
• 属性'Detect64BitPortabilityProblems'，并且在转换过程中已将其删除.
• MSB8012:$(TargetName)('NppAutoIndent')与项目配置'Debug | Win32'中的链接器的OutputFile属性值'.. \ build \ NppAutoIndentA_D.dll'('NppAutoIndentA_D')不匹配.这可能会导致您的项目无法正确构建.若要更正此问题，请确保$(TargetName)属性值与％(Link.OutputFile)中指定的值匹配.
• MSB8012:$(TargetPath)('C:[...] \ NppAutoIndent \ project .. \ build \ Debug \ NppAutoIndent.dll')与链接器的OutputFile属性值'.. \ build \ NppAutoIndentA_D不匹配. dll"("C:[...] \ NppAutoIndent \ build \ NppAutoIndentA_D.dll")在项目配置"Debug | Win32"中.这可能会导致您的项目无法正确构建.若要更正此问题，请确保$(TargetPath)属性值与％(Link.OutputFile)中指定的值匹配.
• MSB8012:$(TargetName)('NppAutoIndent')与项目配置'Release | Win32'中的链接器的OutputFile属性值'.. \ build \ NppAutoIndentA.dll'('NppAutoIndentA')不匹配.这可能会导致您的项目无法正确构建.若要更正此问题，请确保$(TargetName)属性值与％(Link.OutputFile)中指定的值匹配.
• MSB8012:$(TargetPath)('C:[...] \ NppAutoIndent \ project .. \ build \ Release \ NppAutoIndent.dll')与链接器的OutputFile属性值'.. \ build \ NppAutoIndentA不匹配.项目配置发布| Win32"中的"dll"("C:[...] \ NppAutoIndent \ build \ NppAutoIndentA.dll").这可能会导致您的项目无法正确构建.若要更正此问题，请确保$(TargetPath)属性值与％(Link.OutputFile)中指定的值匹配.
• MSB8012:$(TargetPath)('C:[...] \ NppAutoIndent \ project .. \ build \ Release Unicode \ NppAutoIndent.dll')与链接器的OutputFile属性值'.. \ build \ NppAutoIndent项目配置发布Unicode | Win32"中的".dll"("C:[...] \ NppAutoIndent \ build \ NppAutoIndent.dll").这可能会导致您的项目无法正确构建.若要更正此问题，请确保$(TargetPath)属性值与％(Link.OutputFile)中指定的值匹配.
• MSB8012:$(TargetName)('NppAutoIndent')与项目配置'Debug Unicode | Win32'中的链接器的OutputFile属性值'.. \ build \ NppAutoIndent_D.dll'('NppAutoIndent_D')不匹配.这可能会导致您的项目无法正确构建.若要更正此问题，请确保$(TargetName)属性值与％(Link.OutputFile)中指定的值匹配.
• MSB8012:$(TargetPath)('C:[...] \ NppAutoIndent \ project .. \ build \ Debug Unicode \ NppAutoIndent.dll')与链接器的OutputFile属性值'.. \ build \ NppAutoIndent_D不匹配.dll"("C:[...] \ NppAutoIndent \ build \ NppAutoIndent_D.dll")在项目配置调试Unicode | Win32"中.这可能会导致您的项目无法正确构建.要解决此问题，请确保$(TargetPath)属性值与％(Link.OutputFile)中指定的值匹配.

• Due to a change in the exception handling switches for the C/C++ Compiler, /EHsc has been automatically converted to /EHa in this project.
• Done converting to new project file 'C:[...]\NppAutoIndent\project\NppAutoIndent.vcxproj'.
• Due to the requirement that Visual C++ projects produce an embedded (by default) Windows SxS manifest, manifest files in the project are now automatically built with the Manifest Tool. You may need to change your build in order for it to work correctly. For instance, it is recommended that the dependency information contained in any manifest files be converted to "#pragma comment(linker,"")" in a header file that is included from your source code. If your project already embeds a manifest in the RT_MANIFEST resource section through a resource (.rc) file, the line may need to be commented out before the project will build correctly.
• Due to a conformance change in the C++ compiler, code change may be required before your project will build without errors. Previous versions of the C++ compiler allowed specification of member function pointers by member function name (e.g. MemberFunctionName). The C++ standard requires a fully qualified name with the use of the address-of operator (e.g. &ClassName::MemberFunctionName). If your project contains forms or controls used in the Windows Forms Designer, you may have to change code in InitializeComponent because the designer generated code used the non-conformant syntax in delegate construction (used in event handlers).
• This application has been updated to include settings related to the User Account Control (UAC) feature of Windows Vista. By default, when run on Windows Vista with UAC enabled, this application is marked to run with the same privileges as the process that launched it. This marking also disables the application from running with virtualization. You can change UAC related settings from the Property Pages of the project.
• Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
• VCWebServiceProxyGeneratorTool is no longer supported. The tool has been removed from your project settings.
• The C/C++ compiler switch /Og has been deprecated and has been removed from your project settings. It is recommended that you use /O1 or /O2 instead.
• VCConvertEngine could not convert attribute GlobalOptimizations = TRUE under Tool VCCLCompilerTool.
• Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
• Attribute 'OptimizeForWindows98' of 'VCLinkerTool' is not supported in this version and has been removed during conversion.
• VCConvertEngine could not convert attribute GlobalOptimizations = TRUE under Tool VCCLCompilerTool.
• Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
• Attribute 'OptimizeForWindows98' of 'VCLinkerTool' is not supported in this version and has been removed during conversion.
• Attribute 'Detect64BitPortabilityProblems' of 'VCCLCompilerTool' is not supported in this version and has been removed during conversion.
• MSB8012: $(TargetName) ('NppAutoIndent') does not match the Linker's OutputFile property value '..\build\NppAutoIndentA_D.dll' ('NppAutoIndentA_D') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetName) property value matches the value specified in %(Link.OutputFile).
• MSB8012: $(TargetPath) ('C:[...]\NppAutoIndent\project..\build\Debug\NppAutoIndent.dll') does not match the Linker's OutputFile property value '..\build\NppAutoIndentA_D.dll' ('C:[...]\NppAutoIndent\build\NppAutoIndentA_D.dll') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile).
• MSB8012: $(TargetName) ('NppAutoIndent') does not match the Linker's OutputFile property value '..\build\NppAutoIndentA.dll' ('NppAutoIndentA') in project configuration 'Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetName) property value matches the value specified in %(Link.OutputFile).
• MSB8012: $(TargetPath) ('C:[...]\NppAutoIndent\project..\build\Release\NppAutoIndent.dll') does not match the Linker's OutputFile property value '..\build\NppAutoIndentA.dll' ('C:[...]\NppAutoIndent\build\NppAutoIndentA.dll') in project configuration 'Release|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile).
• MSB8012: $(TargetPath) ('C:[...]\NppAutoIndent\project..\build\Release Unicode\NppAutoIndent.dll') does not match the Linker's OutputFile property value '..\build\NppAutoIndent.dll' ('C:[...]\NppAutoIndent\build\NppAutoIndent.dll') in project configuration 'Release Unicode|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile).
• MSB8012: $(TargetName) ('NppAutoIndent') does not match the Linker's OutputFile property value '..\build\NppAutoIndent_D.dll' ('NppAutoIndent_D') in project configuration 'Debug Unicode|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetName) property value matches the value specified in %(Link.OutputFile).
• MSB8012: $(TargetPath) ('C:[...]\NppAutoIndent\project..\build\Debug Unicode\NppAutoIndent.dll') does not match the Linker's OutputFile property value '..\build\NppAutoIndent_D.dll' ('C:[...]\NppAutoIndent\build\NppAutoIndent_D.dll') in project configuration 'Debug Unicode|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile).

推荐答案

在VS2010中打开VS 2003项目；对话框将引导您完成转换.您只需要阅读说明并单击相应的按钮即可.

Open the VS 2003 project in VS2010 ; a dialog shall walk you through the conversion. You just need to read the instructions and click the appropriate button .

关于缩进，请转到工具--->选项，选择语言(C ++)并转到格式.您可以在那里看到很多选项，并根据需要进行更改.

Regarding indentation, go to Tools ---> Options , choose the Language (C++ ) and go to formatting. You can see a bunch of options there , change it according to your needs .

您完全不需要Notepad ++.顺便说一句，我是Notepad ++的狂热用户，也是我最喜欢的编辑器.

You dont need Notepad++ at all for this . BTW , I am an avid user of Notepad++ , and its my favourite editor.

希望这会有所帮助.

这篇关于调整NppAutoIndent，还是有一个很好的可自定义替代方法?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！