lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4749 Doc: Min


From: Auto mailings of changes to Lily Issues
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4749 Doc: Minor, superficial changes to CG, Extending, LM and paper-defaults.ly
Date: Sun, 24 Jan 2016 21:06:52 +0000

Diff:

--- old
+++ new
@@ -1,2 +1,10 @@
 These are a number of things which accumulated and didn’t warrant an issue of their own.
 https://codereview.appspot.com/281510043
+
+Contains commits:
+* **Better code formatting in some alists** Previously, the 110-character lines made it difficult to read; the new version is also in line with what the NR says.
+* **Doc Ext: comment TODO remark** Telling the user that he might be confused about something (while he doesn’t understand what exactly that is) only adds to confusion; I find it odd to have this on the surface.
+* **Doc: properly format formatted example** This should actually show how reformatting Scheme code makes it easier to read; however, it uses tabs and the result in both HTML and PDF is a total mess. The new version uses normal spaces only and should be consistent as well as clear.
+* **Doc: minor wording and punctuation improvements**
+* **Doc: always capitalize LilyPond correctly**
+* **Fix typo in LM (follow-up to 4582)** There was an unmatched parenthesis in the text; changed into a comma.

[issues:#4749] Doc: Minor, superficial changes to CG, Extending, LM and paper-defaults.ly

Status: Started
Created: Sat Jan 23, 2016 01:32 AM UTC by Simon Albrecht
Last Updated: Sun Jan 24, 2016 07:08 PM UTC
Owner: Simon Albrecht

These are a number of things which accumulated and didn’t warrant an issue of their own.
https://codereview.appspot.com/281510043

Contains commits:
Better code formatting in some alists Previously, the 110-character lines made it difficult to read; the new version is also in line with what the NR says.
Doc Ext: comment TODO remark Telling the user that he might be confused about something (while he doesn’t understand what exactly that is) only adds to confusion; I find it odd to have this on the surface.
Doc: properly format formatted example This should actually show how reformatting Scheme code makes it easier to read; however, it uses tabs and the result in both HTML and PDF is a total mess. The new version uses normal spaces only and should be consistent as well as clear.
Doc: minor wording and punctuation improvements
Doc: always capitalize LilyPond correctly
Fix typo in LM (follow-up to 4582) There was an unmatched parenthesis in the text; changed into a comma.


Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

reply via email to

[Prev in Thread] Current Thread [Next in Thread]