[Github-comments] [geany/geany] Improve build docs (#2326)

Matthew Brush notifications at xxxxx
Sat Sep 28 02:54:59 UTC 2019


codebrainz approved this pull request.

I like these changes, just the list nesting comment I think is an actual problem.

> @@ -3042,16 +3039,16 @@ behaviors:
   compiler tab and parse it for errors.
 * Execute commands - are configurable and intended for executing your
   program or other long running programs.  The output is not parsed for errors
-  and is directed to the terminal command selected in preferences.
+  and is directed to the terminal command selected in *Preferences*.

Alternative for `*Preferences*` could be `` `Tools preferences`_ ``.

>  * Fixed commands - these perform built-in actions:
 
-  * Go to the next error.
-  * Go to the previous error.
-  * Show the build menu commands dialog.
+* Go to the next error.
+* Go to the previous error.
+* Show the build menu commands dialog.

I think this indentation was intentional for nesting.

>    execute and preferences independent execute commands can only be set by hand
   editing the appropriate file, see `Preferences file format`_ and `Project file
   format`_.
 
-Build menu commands dialog
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Most of the configuration of the build menu is done through the Build Menu
-Commands Dialog.  You edit the configuration sourced from preferences in the
-dialog opened from the Build->Build Menu Commands item and you edit the
-configuration from the project in the build tab of the project preferences
-dialog.  Both use the same form shown below.
+Set Build Commands dialog
+^^^^^^^^^^^^^^^^^^^^^^^^^
+ 
+Most of the configuration of the build menu is done through the *Set 
+Build Commands* dialog. When no project is open, you can edit the 

Could use `` `Set Build Commands dialog`_ `` or whatever is the hyperlink syntax.

>  An item with an empty label will not be shown in the menu.
-

If merging into a single paragraph, a reflow of the new paragraph might be in order, not a big deal though.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2326#pullrequestreview-294616983
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20190927/400b026b/attachment.html>


More information about the Github-comments mailing list