Penguin
Recent Changes
Annotated edit history of flea(1) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 flea
2 !!!flea
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 ENVIRONMENT
7 FILES
8 SEE ALSO
9 AUTHOR
10 ----
11 !!NAME
12
13
14 flea - Report a bug (or rather a flea) in mutt.
15 !!SYNOPSIS
16
17
18 __flea__
19 !!DESCRIPTION
20
21
22 __flea__ is a shell script which helps you to submit a
23 bug report against the mutt(1) mail user
24 agent.
25
26
27 If you invoke __flea__, you'll first be prompted for a
28 short description of the problem you experience. This will
29 be used as the bug report's subject line, so it should be
30 concise, but informative.
31
32
33 You are then asked to assign an initial severity level to
34 the problem you observe; __flea__ will give you a
35 description which severity level is appropriate or
36 not.
37
38
39 Then, you are asked for the location of a core dump
40 (normally named __core__) which may have been left over
41 by a crash of your mutt(1). You can just type ``no''
42 here, or you can enter the path leading to a core dump.
43 __flea__ will try to use either sdb(1),
44 dbx(1), or gdb(1) to extract some information
45 from this core dump which may be helpful to developers in
46 order to determine the reason for the crash.
47
48
49 Finally, you are asked whether or not you want to include
50 personal and system mutt(1) configuration files with
51 the bug report. If at all possible, we urge you to answer
52 these questions with ``yes'', since a reference
53 configuration makes it incredibly easier to track down a
54 problem.
55
56
57 If you are using Debian GNU/Linux, __flea__ will now
58 check whether or not __mutt__ has been installed as a
59 Debian package on your system, and suggest to file the bug
60 against the mutt(1) and Debian bug tracking systems.
61 This option was added since the mutt(1) project uses
62 another instantiation of the Debian bug tracking system, so
63 submitting bugs against both systems in one pass is
64 simple.
65
66
67 You are then dropped into your favorite editor as determined
68 by the __EDITOR__ and __VISUAL__ environment
69 variables.
70
71
72 Please give us details about the problem in the empty space
73 below the line reading ``Please type your report below this
74 line''. We are most interested in precise information on
75 what symptoms you observe and what steps may be used to
76 reproduce the bug. Chances are that problems which can
77 easily be reproduced will be fixed quickly. So please take
78 some time when filling out this part of the
79 template.
80
81
82 The remainder of the template contains various kinds of
83 information gathered from your system, including output of
84 the uname(1) command, output from mutt(1)
85 itself, and your system's mutt(1) configuration
86 files. You may wish to browse through this part of the bug
87 report form in order to avoid leaking confidential
88 information to the public.
89
90
91 If you leave the editor, __flea__ will give you the
92 option to review, re-edit, submit, or abandon your bug
93 report. If you decide to submit it, a mail message
94 containing your report will be sent to
95 __
96
97
98 While your bug report is being processed by the bug tracking
99 system, you will receive various e-mail messages from the
100 bug tracking system informing you about what's going on:
101 Once your bug report has been entered into the bug tracking
102 system, it will be assigned a unique serial number about
103 which you are informed via e-mail. If you wish to submit
104 additional information about the bug, you can just send it
105 to the address
106 ''serial''__@bugs.guug.de__.
107
108
109 Later, you will most likely receive questions from the
110 developers about the problem you observed, and you will
111 eventually be informed that your bug report has been closed.
112 This means that the bug has been fixed at least in the
113 cvs(1) repository. If the answers you receive don't
114 satisfy you, don't hesitate to contact the developers
115 directly under __mutt-dev@mutt.org.__
116
117
118 You can also browse your bug report and all additional
119 information and replies connected to it using the bug
120 tracking system's Web interface under the following URL:
121 http://bugs.guug.de/
122 !!ENVIRONMENT
123
124
125 __flea__ will use the following environment
126 variables:
127
128
129 EMAIL
130
131
132 Your electronic mail address. Will be used to set the bug
133 report's From header, and to send you a copy of the
134 report.
135
136
137 LOGNAME
138
139
140 Your login name. If the __EMAIL__ environment variable
141 isn't set, this will be used instead to send you a copy of
142 the report. Setting the sender will be left to
143 sendmail(1) on your system.
144
145
146 REPLYTO
147
148
149 If set, the bug report will contain a Reply-To header with
150 the e-mail address contained in this environment
151 variable.
152
153
154 ORGANIZATION
155
156
157 If set, the bug report will contain an Organization header
158 with the contents of this environment variable.
159
160
161 PAGER
162
163
164 If set, this environment variable will be expected to
165 contain the path to your favorite pager for viewing the bug
166 report. If unset, more(1) will be used.
167
168
169 VISUAL
170
171
172 If set, this environment variable will be expected to
173 contain the path to your favorite visual
174 editor.
175
176
177 EDITOR
178
179
180 If set, this environment variable will be expected to
181 contain the path to your favorite editor. This variable is
182 examined if and only if the __VISUAL__ environment
183 variable is unset. If __EDITOR__ is unset, vi(1)
184 will be used to edit the bug report.
185 !!FILES
186
187
188 core
189
190
191 If present, this file may contain a post-mortem memory dump
192 of mutt. It will be inspected using the debugger installed
193 on your system.
194 !!SEE ALSO
195
196
197 dbx(1), gdb(1), lynx(1),
198 mutt(1), muttrc(5), sdb(1),
199 sendmail(1), uname(1),
200 vi(1)
201
202
203 The mutt bug tracking system:
204 http://bugs.guug.de/
205 !!AUTHOR
206
207
208 __flea__ and this manual page were written by Thomas
209 Roessler __
210 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.