Package: bosh / 0.6-10

fix-lintian-hyphen-used-as-minus-sign.patch Patch series | download
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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
Description: Fix hyphen-used-as-minus-sign lintian warnings for bosh.1
 manpage.
Forwarded: yes
Author: Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
--- a/bosh.1
+++ b/bosh.1
@@ -2,8 +2,7 @@
 .\"(C) Alex Sisson, 2008-2009
 .TH bosh 1 "18-MAR-2008" bosh-0.6
 .SH NAME
-.B bosh
-(Browsable Output SHell)
+.B bosh \- Browsable Output SHell
 .SH SYNOPSIS
 .B bosh
 .I [OPTIONS] [CONFIGURATION] [CONFIGURATION OPTIONS]
@@ -73,19 +72,19 @@
 .SH CONFIGURATION FILES
 
 Bosh configs are fairly simple. Firstly you need a line which tells bosh the
-actual program to execute to show it it's buffer -
+actual program to execute to show it it's buffer \-
 
 .RS
 .B command=ps x
 .RE
 
-It could also be a chain of commands (bash) -
+It could also be a chain of commands (bash) \-
 
 .RS
 .B command=for i in *; do echo $i; done
 .RE
 
-Or it can spread it over multiple lines for readablity with a \\ (must be at the end of line!) -
+Or it can spread it over multiple lines for readablity with a \\ (must be at the end of line!) \-
 
 .RS
 .B
@@ -101,7 +100,7 @@
 done
 .RE
 
-Or now even better, bosh supports blocks delimited by {{ and }} -
+Or now even better, bosh supports blocks delimited by {{ and }} \-
 .RS
 .B
 command{{
@@ -125,7 +124,7 @@
 These can be used with all options and actions.
 
 Command line arguments given to bosh after the COMMAND parameter are available
-and can be used as follows -
+and can be used as follows \-
 
 .RS
 .B command=ps $*
@@ -142,7 +141,7 @@
 
 .RS
 .B
-command=if [ -z "$1" ] \\
+command=if [ \-z "$1" ] \\
 .HP
 .B
 then \\
@@ -168,7 +167,7 @@
 
 After the command option, you can specify any of the options specified above in the
 .B OPTIONS
-section, but without the -- prefix -
+section, but without the \-\- prefix \-
 
 .RS
 .B header=4
@@ -178,7 +177,7 @@
 
 
 .SH ACTIONS
-Basic actions are defined as -
+Basic actions are defined as \-
 
 .RS
 .B KEY=command
@@ -187,19 +186,19 @@
 eg:
 
 .RS
-.B k=kill $(echo $BOSH | cut -f1 -d' ')
+.B k=kill $(echo $BOSH | cut \-f1 \-d' ')
 .P
-.B 9=kill -9 $(echo $BOSH | cut -f1 -d' ')
+.B 9=kill \-9 $(echo $BOSH | cut \-f1 \-d' ')
 .RE
 
-Or, using the preaction setting (see above) -
+Or, using the preaction setting (see above) \-
 
 .RS
-.B preaction=PID=$(echo $BOSH | cut -f1 -d' ');
+.B preaction=PID=$(echo $BOSH | cut \-f1 \-d' ');
 .P
 .B k=kill $PID
 .P
-.B 9=kill -9 $PID
+.B 9=kill \-9 $PID
 .RE
 
 The keys available are a-z,0-9 and enter. Bosh keys are not case sensitive,
@@ -215,7 +214,7 @@
 .SS ACTIONS WITH OUTPUT
 For basic actions such as kill, which has no output to stdout, the above
 definition is sufficient. However, bosh can now intercept the output of actions
-and place that in the bosh window. These are defined as follows -
+and place that in the bosh window. These are defined as follows \-
 
 .RS
 .B KEY=[.]command
@@ -225,20 +224,20 @@
 eg:
 
 .RS
-.B l=[.]/usr/sbin/lsof -p $PID
+.B l=[.]/usr/sbin/lsof \-p $PID
 .RE
 
 Assuming the preaction is used above, this action will use lsof to show in
 bosh a list of files that process $PID has open. In this situation, the output
 of the original command is lost, and replaced with the output of the action.
 
-Alternatively an action can be defined -
+Alternatively an action can be defined \-
 .RS
 .B KEY=[>]command
 .RE
 
 In this situation, bosh is like a web browser, in that this output (lsof) will not
-override the current buffer, but create a new buffer - You can get then move back and forward
+override the current buffer, but create a new buffer \- You can get then move back and forward
 through these buffers with the left and right arrow keys. At this stage, actions are only available
 in the original buffer.
 
@@ -263,10 +262,10 @@
 .B $BOSHPARAM
 variable.
 
-eg: Using the ps example above, with PID preaction -
+eg: Using the ps example above, with PID preaction \-
 
 .RS
-.B s=[!:signal] kill -s "$BOSHPARAM" $PID
+.B s=[!:signal] kill \-s "$BOSHPARAM" $PID
 .RE
 
 When this action is called,
@@ -284,7 +283,7 @@
 .B $BOSHPARAM
 and
 .B $BOSHERR
-(all explained above), the following variables available to actions -
+(all explained above), the following variables available to actions \-
 
 .TP
 .B $BOSHPID
@@ -314,7 +313,7 @@
 the above examples are taken from. The original inspiration for bosh was being able to kill
 processes easily in this manner.
 
-To run bops, type -
+To run bops, type \-
 
 .RS
 .B $ ./bops
@@ -322,7 +321,7 @@
 
 This invokes bosh through the shebang at the top (assuming the path is set correctly).
 
-Or to run it the traditional way -
+Or to run it the traditional way \-
 
 .RS
 .B $ ./bosh ./bops