Go to main content

man pages section 1: User Commands

Exit Print View

Updated: Thursday, June 13, 2019
 
 

flea (1)

Name

flea - Report a bug (or rather a flea) in mutt.

Synopsis

flea

Description

flea(1)                          User Manuals                          flea(1)



NAME
       flea - Report a bug (or rather a flea) in mutt.

SYNOPSIS
       flea

DESCRIPTION
       flea  is  a shell script which helps you to submit a bug report against
       the mutt(1) mail user agent.

       If you invoke flea, you'll first be prompted for a short description of
       the problem you experience.  This will be used as the bug report's sub-
       ject line, so it should be concise, but informative.

       You are then asked to assign an initial severity level to  the  problem
       you  observe;  flea will give you a description which severity level is
       appropriate or not.

       Then, you are asked for the location of a  core  dump  (normally  named
       core)  which  may  have been left over by a crash of your mutt(1).  You
       can just type "no" here, or you can enter the path leading  to  a  core
       dump.  flea will try to use either sdb(1), dbx(1), or gdb(1) to extract
       some information from this core dump which may be helpful to developers
       in order to determine the reason for the crash.

       Finally,  you are asked whether or not you want to include personal and
       system mutt(1) configuration files with the bug report.  If at all pos-
       sible, we urge you to answer these questions with "yes", since a refer-
       ence configuration makes it incredibly easier to track down a problem.

       If you are using Debian GNU/Linux, flea will now check whether  or  not
       mutt has been installed as a Debian package on your system, and suggest
       to file the bug against the mutt(1) and Debian  bug  tracking  systems.
       This option was added since the mutt(1) project uses another instantia-
       tion of the Debian bug tracking system, so submitting bugs against both
       systems in one pass is simple.

       You  are  then  dropped  into your favorite editor as determined by the
       EDITOR and VISUAL environment variables.

       Please give us details about the problem in the empty space  below  the
       line  reading  "Please  type your report below this line".  We are most
       interested in precise information on what symptoms you observe and what
       steps  may  be  used  to  reproduce the bug.  Chances are that problems
       which can easily be reproduced will be fixed quickly.  So  please  take
       some time when filling out this part of the template.

       The  remainder  of  the  template contains various kinds of information
       gathered from your system, including output of  the  uname(1)  command,
       output  from  mutt(1)  itself,  and your system's mutt(1) configuration
       files.  You may wish to browse through this part of the bug report form
       in order to avoid leaking confidential information to the public.

       If  you  leave the editor, flea will give you the option to review, re-
       edit, submit, or abandon your bug report.  If you decide to submit  it,
       a mail message containing your report will be sent to <fleas@mutt.org>.
       You'll receive a copy of this message.

       While your bug report is being processed by the  bug  tracking  system,
       you  will  receive various e-mail messages from the bug tracking system
       informing you about what's going on: Once  your  bug  report  has  been
       entered  into  the  bug  tracking  system, it will be assigned a unique
       serial number about which you are informed via e-mail.  If you wish  to
       submit  additional  information  about the bug, you can just send it to
       the address fleas@mutt.org with #serial in the subject.

       Later, you will most likely receive questions from the developers about
       the problem you observed, and you will eventually be informed that your
       bug report has been closed.  This means that the bug has been fixed  at
       least  in  the hg(1) repository.  If the answers you receive don't sat-
       isfy you, don't hesitate to contact the developers directly under mutt-
       dev@mutt.org.

       You  can also browse your bug report and all additional information and
       replies connected to it using the bug tracking system's  Web  interface
       under the following URL: http://bugs.mutt.org/

ENVIRONMENT
       flea will use the following environment variables:

       EMAIL  Your  electronic  mail  address.   Will  be  used to set the bug
              report's From header, and to send you a copy of the report.

       LOGNAME
              Your login name.  If the EMAIL environment variable  isn't  set,
              this  will  be  used  instead  to send you a copy of the report.
              Setting the sender will be left to sendmail(1) on your system.

       REPLYTO
              If set, the bug report will contain a Reply-To header  with  the
              e-mail address contained in this environment variable.

       ORGANIZATION
              If  set, the bug report will contain an Organization header with
              the contents of this environment variable.

       PAGER  If set, this environment variable will be  expected  to  contain
              the  path to your favorite pager for viewing the bug report.  If
              unset, more(1) will be used.

       VISUAL If set, this environment variable will be  expected  to  contain
              the path to your favorite visual editor.

       EDITOR If  set,  this  environment variable will be expected to contain
              the path to your favorite editor.  This variable is examined  if
              and only if the VISUAL environment variable is unset.  If EDITOR
              is unset, vi(1) will be used to edit the bug report.

FILES
       core   If present, this file may contain a post-mortem memory  dump  of
              mutt.  It will be inspected using the debugger installed on your
              system.

SEE ALSO
       dbx(1),  gdb(1),  lynx(1),  mutt(1),  muttrc(5),  sdb(1),  sendmail(1),
       uname(1), vi(1)

       The mutt bug tracking system: http://bugs.mutt.org/

AUTHOR
       flea   and   this   manual   page   were  written  by  Thomas  Roessler
       <roessler@does-not-exist.org>.



ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:


       +---------------+------------------+
       |ATTRIBUTE TYPE | ATTRIBUTE VALUE  |
       +---------------+------------------+
       |Availability   | mail/mutt        |
       +---------------+------------------+
       |Stability      | Uncommitted      |
       +---------------+------------------+
NOTES
       This    software    was    built    from    source     available     at
       https://github.com/oracle/solaris-userland.    The  original  community
       source                was                downloaded                from
       ftp://ftp.mutt.org/pub/mutt/mutt-1.9.1.tar.gz

       Further information about this software can be found on the open source
       community website at http://www.mutt.org/.



Unix                               July 2000                           flea(1)