File: 0007-pygmentize-lexer.patch

package info (click to toggle)
crmsh 5.0.0-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 7,980 kB
  • sloc: python: 50,399; sh: 1,207; makefile: 255; xml: 243; exp: 234; awk: 22
file content (81 lines) | stat: -rw-r--r-- 2,267 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
From: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Subject: Patch to avoid using the custom lexer
 This patch makes some changes to the crmsh doc build so it doesn't use
 the included custom lexer.
Forwarded: not-needed
Last-Update: 2016-09-23

--- a/doc/website-v1/history-guide.adoc
+++ b/doc/website-v1/history-guide.adoc
@@ -51,7 +51,7 @@
 preparing this document we noticed that a probe failed repeatedly
 on a node which wasn't even running the resource <<Listing 2>>.
 
-[source,ansiclr]
+[source,c]
 [caption="Listing 2: "]
 .crm status output[[Listing 2]]
 -----------------
@@ -61,7 +61,7 @@
 The history +resource+ command shows log messages relevant to the
 supplied resource <<Listing 3>>.
 
-[source,ansiclr]
+[source,c]
 [caption="Listing 3: "]
 .Logs on failed +nfs-server+ probe operation[[Listing 3]]
 -----------------
@@ -88,7 +88,7 @@
 tracing of the resource agent. <<Listing 4>> shows how to do
 that.
 
-[source,ansiclr]
+[source,c]
 [caption="Listing 4: "]
 .Set `nfs-server` probe operation resource tracing[[Listing 4]]
 -----------------
@@ -126,7 +126,7 @@
 To begin, we run the `info` command which gives an overview, as
 shown in <<Listing 5>>.
 
-[source,ansiclr]
+[source,c]
 [caption="Listing 5: "]
 .Basic history information[[Listing 5]]
 -----------------
@@ -155,7 +155,7 @@
 The listing is annotated to explain the output in more detail.
 
 
-[source,ansiclr]
+[source,c]
 [caption="Listing 6: "]
 .Viewing transitions[[Listing 6]]
 -----------------
@@ -194,7 +194,7 @@
 It may sometimes be useful to see what changed between two
 transitions. History `diff` command is in action in <<Listing 7>>.
 
-[source,ansiclr]
+[source,c]
 [caption="Listing 7: "]
 .Viewing transitions[[Listing 7]]
 -----------------
@@ -212,7 +212,7 @@
 actions of that transition are yet to be executed. So, the status
 section of transition _N_ corresponds to the configuration _N-1_.
 
-[source,ansiclr]
+[source,c]
 [caption="Listing 8: "]
 .Full transition log[[Listing 8]]
 -----------------
@@ -232,7 +232,7 @@
 	  recommendable), then use the history `detail` command to
 	  increase the level of detail displayed.
 
-[source,ansiclr]
+[source,c]
 [caption="Listing 9: "]
 .Resource related messages[[Listing 9]]
 -----------------