/usr/share/doc/vm/html/Bugs.html is in vm 8.2.0b-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 6.0, http://www.gnu.org/software/texinfo/ -->
<head>
<title>VM User’s Manual: Bugs</title>
<meta name="description" content="VM User’s Manual: Bugs">
<meta name="keywords" content="VM User’s Manual: Bugs">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
<link href="License.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="index.html#Top" rel="up" title="Top">
<link href="Internals.html#Internals" rel="next" title="Internals">
<link href="Future-Plans.html#Future-Plans" rel="prev" title="Future Plans">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space: nowrap}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: serif; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<a name="Bugs"></a>
<div class="header">
<p>
Next: <a href="Internals.html#Internals" accesskey="n" rel="next">Internals</a>, Previous: <a href="Future-Plans.html#Future-Plans" accesskey="p" rel="prev">Future Plans</a>, Up: <a href="index.html#Top" accesskey="u" rel="up">Top</a> [<a href="License.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Reporting-Bugs"></a>
<h2 class="chapter">26 Reporting Bugs</h2>
<a name="index-bug-reports"></a>
<p>VM has a sophisticated bug reporting system in order to provide the
VM maintainers with adequate information about the state of VM when the
error situation occurred. However, it is still important for the
users to give as full an explanation of the problem as possible.
See <a href="http://www.gnu.org/software/emacs/manual/html_node/emacs/Bugs.html#Bugs">Bugs</a> in <cite>the GNU Emacs Manual</cite>.
</p>
<a name="index-vm_002dsubmit_002dbug_002dreport"></a>
<p>The command <code>M-x vm-submit-bug-report</code> should be invoked from the
VM folder buffer in which a problem is encountered. This creates a
mail buffer with information about the state of VM pre-filled. Insert
suitable text to explain the problem and send the bug-report message.
</p>
<a name="index-vm_002dpop_002dstart_002dbug_002dreport"></a>
<a name="index-vm_002dpop_002dsubmit_002dbug_002dreport"></a>
<a name="index-vm_002dimap_002dstart_002dbug_002dreport"></a>
<a name="index-vm_002dimap_002dsubmit_002dbug_002dreport"></a>
<p>For mail server-associated problems dealing with <acronym>POP</acronym>/<acronym>IMAP</acronym> spool files
or <acronym>POP</acronym>/<acronym>IMAP</acronym> folders, the cause of the problem might be in the
interaction with the mail server. To identify the cause, it may be
necessary for the VM maintainer to look at the server interactions
during the problem occurrence. To capture the server interactions,
run <code>vm-pop-start-bug-report</code>/<code>vm-imap-start-bug-report</code>
before the problem occurrence and <code>vm-pop-submit-bug-report</code>
/<code>vm-imap-submit-bug-report</code> after the problem occurrence. All
the server interactions during the interval are captured and
automatically included in the bug-report.
</p>
<hr>
<div class="header">
<p>
Next: <a href="Internals.html#Internals" accesskey="n" rel="next">Internals</a>, Previous: <a href="Future-Plans.html#Future-Plans" accesskey="p" rel="prev">Future Plans</a>, Up: <a href="index.html#Top" accesskey="u" rel="up">Top</a> [<a href="License.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
|