doc: fix links

rainers · rainers · commit 827a372c40d1 · 2016-01-17T21:53:36.000+01:00
diff --git a/doc/Editor.dd b/doc/Editor.dd
@@ -6,27 +6,27 @@ $(UL
  $(LI syntax highlighting supports all sorts of D2 style strings.
   $(IMG_CENTER images/strings.png)
  )
- $(LI statements disabled by version or debug conditionals are displayed in a slightly different color. 
-   Debug and version identifiers and levels can be defined in the same source file or in the current project 
+ $(LI statements disabled by version or debug conditionals are displayed in a slightly different color.
+   Debug and version identifiers and levels can be defined in the same source file or in the current project
    configuration. The compiler predefined version identifiers are also recognized.)
   $(IMG_CENTER images/versionhighlight.png)
- $(LI code in $(LINK2 http://d-programming-language.org/lex.html#TokenString, token string literals) are highlighted 
+ $(LI code in $(LINK2 http://d-programming-language.org/lex.html#TokenString, token string literals) are highlighted
    in another slightly different color than regular code.)
- $(LI highlighting colors can be setup in the "Fonts and Colors" page found in the Tools->Options Dialog. 
-   In addition to the regular colors, you'll find "Visual D Disabled ..." colors for the code disabled 
+ $(LI highlighting colors can be setup in the "Fonts and Colors" page found in the Tools->Options Dialog.
+   In addition to the regular colors, you'll find "Visual D Disabled ..." colors for the code disabled
    through version statements and "Visual D Token String ..." colors for the code in token strings.)
  $(LI underlining of syntax errors (no semantic analysis done)
    $(IMG_CENTER images/syntaxerror.png)
  )
 )
 
-$(P The colorizer can be configured in the "Colorizer" setup page of the language settings in 
+$(P The colorizer can be configured in the "Colorizer" setup page of the language settings in
 Tools->Options->Text Editor->D->Colorizer: )
 
  $(IMG_CENTER images/editor-options.png)
 
-$(P User defined types have there own color settings. You can also manipulate other identifiers by assigning them 
-a different color category: if prefixed with one of the section names, they will be highlighted accordingly. 
+$(P User defined types have there own color settings. You can also manipulate other identifiers by assigning them
+a different color category: if prefixed with one of the section names, they will be highlighted accordingly.
 The available color categories are: )
 
 $(UL
@@ -65,8 +65,8 @@ $(UL
     expansions from the text buffer or JSON browse information will be added.
   )
   $(LI Expansions from text buffer:
-    completion will show identifiers in the vicinity of the caret from the same buffer 
-    (default short-cut Ctrl-Space). If no matching identifier is found or if you press the short-cut 
+    completion will show identifiers in the vicinity of the caret from the same buffer
+    (default short-cut Ctrl-Space). If no matching identifier is found or if you press the short-cut
     again, identifiers from JSON files are also displayed.
   )
   $(LI Expansions from JSON browse information:
@@ -83,18 +83,18 @@ $(UL
   $(LI Use semantic analysis for "Goto Definition":
     goto definition (default short-cut F12) can either request the location of the definition of
     a symbol from the semantic engine or takes information from compiler generated JSON files.
-    A successful build with JSON output enabled is necessary for the laytter. JSON files can also 
-    be precompiled and placed into the directories given in the $$(DDLINK GlobalOptions,global options).
-    If there are multiple 
-    definitions for the identifier at the caret position, the $(DDLINK Search,Search Window) will show up.
+    A successful build with JSON output enabled is necessary for the laytter. JSON files can also
+    be precompiled and placed into the directories given in the $$(VDLINK GlobalOptions,global options).
+    If there are multiple
+    definitions for the identifier at the caret position, the $(VDLINK Search,Search Window) will show up.
   )
   $(LI Use Alexander Bothe's D parsing engine:
-    Use the semantic engine that also powers Mono-D and D-IDE. It is more powerful than the 
+    Use the semantic engine that also powers Mono-D and D-IDE. It is more powerful than the
     engine that is part of Visual D. You must have installed it from within the Visual D installer.
   )
 )
 
-$(P Triggering completion an import statement will always complete the token from the files and folders available 
+$(P Triggering completion an import statement will always complete the token from the files and folders available
 in the import directories.
    $(IMG_CENTER images/import_completion.png)
  )
@@ -106,34 +106,34 @@ $(UL
  $(LI smart indentation will indent nicely after pressing Return. )
  $(LI comment/uncomment a selection of lines)
  $(LI highlight/jump-to matching braces (default shortcut Ctrl-$(ACUTE)))
- $(LI code snippets: let's you select from a list of snippets, some of them allowing token 
-   replacements (default shortcut Ctrl-K Ctrl-X). You can also insert code-snippets by writing its 
-   shortcut, then pressing the key for command "Edit.!InvokeSnippetFromShortcut". For example, 
+ $(LI code snippets: let's you select from a list of snippets, some of them allowing token
+   replacements (default shortcut Ctrl-K Ctrl-X). You can also insert code-snippets by writing its
+   shortcut, then pressing the key for command "Edit.!InvokeSnippetFromShortcut". For example,
    shortcut "for" yields
    $(IMG_CENTER images/codesnippet.png)
  )
- $(LI parameter info tooltips (default short-cut Ctrl-Shift-Space) showing function prototype and 
-   highlighting current position in argument list. As with "goto definition" this feature relies 
+ $(LI parameter info tooltips (default short-cut Ctrl-Shift-Space) showing function prototype and
+   highlighting current position in argument list. As with "goto definition" this feature relies
    on JSON files being generated.
    $(IMG_CENTER images/parameterinfo.png)
  )
- $(LI show scope in status line: to avoid navigating through a larger file to figure out what 
-   class the current function belongs to, command "VisualD.ShowScope" displays the class, function, 
+ $(LI show scope in status line: to avoid navigating through a larger file to figure out what
+   class the current function belongs to, command "VisualD.ShowScope" displays the class, function,
    etc. at the caret position:
    $(IMG_CENTER images/showscope.png)
    This command is also accessible from the Visual D menu, but it is best to assign it to some keyboard shortcut.
  )
  $(LI Outlining of curly braced declarations and statements and multi-line comments
    $(IMG_CENTER images/outlining.png)
-   Automatic outlining can be disabled on the global configuration page 
-   "Tools->Options->Text Editor->D->Colorizer". Using command "Outlining->Collapse to Definitions" 
+   Automatic outlining can be disabled on the global configuration page
+   "Tools->Options->Text Editor->D->Colorizer". Using command "Outlining->Collapse to Definitions"
    will enable it for the current text buffer.
  )
- $(LI Two commands are added to the "Edit->Outlining" menu: "Collapse unittests" will fold away 
-   unittest blocks that might obfuscate the actual code if they become excessive. "Collapse disabled code" 
+ $(LI Two commands are added to the "Edit->Outlining" menu: "Collapse unittests" will fold away
+   unittest blocks that might obfuscate the actual code if they become excessive. "Collapse disabled code"
    will hide code blocks actually not compiled due to version or debug conditions helping you concentrate on
    the active code.)
- $(LI show the clipboard ring in a context menu to paste from. This operation is invoked by 
+ $(LI show the clipboard ring in a context menu to paste from. This operation is invoked by
    the "Edit->Cycle Clipboard Ring" command.
    $(IMG_CENTER images/pastemenu.PNG)
  )
diff --git a/doc/GlobalOptions.dd b/doc/GlobalOptions.dd
@@ -1,6 +1,6 @@
 Ddoc
 
-$(P When starting Visual Studio for the first time after installation of Visual D, you might 
+$(P When starting Visual Studio for the first time after installation of Visual D, you might
 want to check the global settings that can be reached from the Menu Tools -> Options -> Projects:
 )
 
@@ -29,12 +29,12 @@ $(IMG_CENTER images/dmd_directories.png)
 $(BR)
 $(UL
  $(LI Install path: The path to the compiler installation folder you entered within the installer.
-  $(UL 
-   $(LI DMD: this is not the path to the executable dmd.exe, but the folder that contains the full installation so 
+  $(UL
+   $(LI DMD: this is not the path to the executable dmd.exe, but the folder that contains the full installation so
         that the compiler is found as $(LESS)DMD install path$(GREATER)\windows\bin\dmd.exe )
-   $(LI GDC: this is not the path to the executable gdc.exe, but the folder that contains the full installation so 
+   $(LI GDC: this is not the path to the executable gdc.exe, but the folder that contains the full installation so
         that the compiler is found as $(LESS)DMD install path$(GREATER)\bin\gdc.exe )
-   $(LI LDC: this is not the path to the executable ldc.exe, but the folder that contains the full installation so 
+   $(LI LDC: this is not the path to the executable ldc.exe, but the folder that contains the full installation so
     that the compiler is found as $(LESS)DMD install path$(GREATER)\bin\ldc2.exe )
   )
  )
@@ -71,8 +71,8 @@ $(UL
  $(LI any variable from the system environment enclosed in $(DOLLAR)() )
 )
 
-$(P Please note that you'll also find a new entry "D" in the Text Editor branch to setup 
-$(DDLINK Editor,syntax highlighting) and more. )
+$(P Please note that you'll also find a new entry "D" in the Text Editor branch to setup
+$(VDLINK Editor,syntax highlighting) and more. )
 
 Macros:
 	TITLE=Global Options
diff --git a/doc/VersionHistory.dd b/doc/VersionHistory.dd
@@ -366,7 +366,7 @@ $(H2 2013-11-02 Version 0.3.37)
   $(LI changed license to Boost)
  )
 
-$(H2 2013-05-10 $(DDLINK News36,Version 0.3.36))
+$(H2 2013-05-10 $(VDLINK News36,Version 0.3.36))
  $(UL
   $(LI added debug settings to new DMD/GDC project template )
   $(LI regressions caused by switching to installation as VS2010/VS2012 extension:
diff --git a/doc/news36.dd b/doc/news36.dd
@@ -1,7 +1,7 @@
 Ddoc
 
-$(P The latest release 0.3.36 of Visual D included a considerable number of bug fixes and improvements 
-(you can find all of them listed in the $(DDLINK VersionHistory,history)), but I'd like to detail on a few 
+$(P The latest release 0.3.36 of Visual D included a considerable number of bug fixes and improvements
+(you can find all of them listed in the $(VDLINK VersionHistory,history)), but I'd like to detail on a few
 bigger highlights.
 )
 
@@ -13,26 +13,26 @@ the current D source file through rdmd which will pick up imported modules autom
 and add them to the compilation. If the file is part of a project in the solution
 the current compiler settings will be used, otherwise the defaults from the !ConsoleApp
 project template are taken. You can add other options in Visual D's global
-project settings. 
+project settings.
 )
 
 $(IMG_CENTER images/compile_and_run_opt.png)
 
 $(P The standard is "-unittest --main" so after successfully building the
-source file to an executable ("--main" adds an empty main function to the source to automatically create a valid executable), your unit tests will run and you will see 
+source file to an executable ("--main" adds an empty main function to the source to automatically create a valid executable), your unit tests will run and you will see
 the result in the output pane.
 )
 
 $(P [Actually, while writing this text a number of issues have been fixed and improvements
-have been made, so please try the latest release candidate for next version of Visual D 
-from the download folder (0.3.37rc1 as of now). Especially, it will remove some of the 
+have been made, so please try the latest release candidate for next version of Visual D
+from the download folder (0.3.37rc1 as of now). Especially, it will remove some of the
 command line options used to call rdmd that make it crash pretty often.]
 )
 
 <table><tr><td valign="top" width="45%">
 $(P If you add "-cov" to the command line aswell the executable will be instrumented to record
-the source code lines that have been executed and will mark the lines that have 
-code generated but are never executed. This information is written into files named as the 
+the source code lines that have been executed and will mark the lines that have
+code generated but are never executed. This information is written into files named as the
 source files but with extension ".lst". If you enable option "Colorize Coverage" in
 the Visual D colorizer settings (easily reachable through the new entry in the Visual D
 menu), these lines will be highlighted in the editor. The highlighting will not show
@@ -45,12 +45,12 @@ $(D	assert(fib(19) == 4181);)
 to the unittest, and run the unittest again, all lines will become green.
 )
 
-$(P If you start editing the source file Visual D will try to keep coverage information in sync. 
-If you want to get rid of the coverage coloring, just resave the source file. 
+$(P If you start editing the source file Visual D will try to keep coverage information in sync.
+If you want to get rid of the coverage coloring, just resave the source file.
 Visual D will assume the coverage is invalid then and stop displaying it.
 )
 
-$(P If you don't want syntax highlighting from coverage generated .LST files, you can disable 
+$(P If you don't want syntax highlighting from coverage generated .LST files, you can disable
 it by unchecking the respective option on the Tools->Options->Text Editor->D->Colorizer page.
 )
 </td><td width="55%">
@@ -67,9 +67,9 @@ $(H1 New code completion engine by Alexander Bothe)
 $(P While Visual D has been running a semantic analysis for about a year now to
 support code completion and type information in tool tips, I didn't have much time
 to complete it to support all aspects of the D programming language. It is especially
-lacking on topics like template instantiation, function overload resolution and 
+lacking on topics like template instantiation, function overload resolution and
 unified function call syntax (UFCS). Also, compile time function evaluation (CTFE) is
-pretty incomplete. 
+pretty incomplete.
 Due to its pretty large memory foot print the
 stop-the-world garbage collector has been interrupting the source code editing to
 inacceptable degrees, so the analyzer had been
@@ -87,24 +87,24 @@ $(P Alex has put much more effort into making the semantic
 analysis complete, and it obviously does it more efficiently. I wrapped the library
 as a local COM server implementing the same interfaces as Visual D's engine (having to do
 this in C# was a bit of a downer) and just using a different factory now allows switching
-between the two. Right now, Visual D's engine is the default, but you can select 
-Alex's engine by enabling the respective checkbox in the Intellisense 
-settings page (there is a new menu entry for faster access). It provides UFCS 
+between the two. Right now, Visual D's engine is the default, but you can select
+Alex's engine by enabling the respective checkbox in the Intellisense
+settings page (there is a new menu entry for faster access). It provides UFCS
 expansion and also displays DDoc help strings in tool tips.
 )
 
 $(P There is currently work being done on the D front end implemented by DMD
 to be converted from C++ to D, bringing it within reach of using it as a library for IDEs.
 This might produce
-another semantic engine in the future which easily keeps in lock step with the latest 
+another semantic engine in the future which easily keeps in lock step with the latest
 compiler updates.
 )
 
 $(H2 LDC support)
 
 $(P LDC, the D compiler built on top of the LLVM compiler infrastructure is getting
 close to being useful on Windows aswell (at least on Win64 the longest standing
-blocker exception handling is starting to work). You can grab pre-compiled binaries 
+blocker exception handling is starting to work). You can grab pre-compiled binaries
 here: http://www.redstar.de/ldc/LDC.zip (after extracting to any directory just update
 the paths specified in LDC2\etc\ldc2.conf).
 In the Visual D project options, path settings for the three major compilers have been
@@ -117,8 +117,8 @@ General page of your project's property page.
 
 $(IMG_CENTER images/ldc_compiler.png)
 
-$(P Please be aware that both LDC for Windows aswell as the Visual D support for 
-it are pretty experimental, so expect some glitches. Known issue: there is no debug 
+$(P Please be aware that both LDC for Windows aswell as the Visual D support for
+it are pretty experimental, so expect some glitches. Known issue: there is no debug
 information in the built executable that can be used by the VS debugger.
 )
 
diff --git a/doc/visuald.ddoc b/doc/visuald.ddoc
@@ -8,6 +8,7 @@ SELF_PATH =
 LAYOUT_SUFFIX=
 $(SCRIPTLOAD js/run-main-website.js)
 
+VDLINK=$(LINK2 $1.html, $2)
 IMG = <img src="$0" />
 IMG_CENTER = <div align="center"><img src="$0" /></div>
 TABLE_NOBORDER = <table style="border-width: 0px 0">$0</table>

Original file line number	Diff line number	Diff line change
`@@ -366,7 +366,7 @@ $(H2 2013-11-02 Version 0.3.37)`
`366`	`366`	`$(LI changed license to Boost)`
`367`	`367`	`)`
`368`	`368`
`369`		`-$(H2 2013-05-10 $(DDLINK News36,Version 0.3.36))`
	`369`	`+$(H2 2013-05-10 $(VDLINK News36,Version 0.3.36))`
`370`	`370`	`$(UL`
`371`	`371`	`$(LI added debug settings to new DMD/GDC project template )`
`372`	`372`	`$(LI regressions caused by switching to installation as VS2010/VS2012 extension:`