emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien Guerry <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: [Accepted]  Improving bug reporting documentation
Date: Mon, 12 Dec 2011 17:34:14 +0100 (CET)	[thread overview]
Message-ID: <20111212163414.2622313E90@myhost.localdomain> (raw)
In-Reply-To: 20111108000620.6fd433b6@kuru.homelinux.net

Patch 1033 (http://patchwork.newartisans.com/patch/1033/) is now "Accepted".

Maintainer comment: none

This relates to the following submission:

http://mid.gmane.org/%3C20111108000620.6fd433b6%40kuru.homelinux.net%3E

Here is the original message containing the patch:

> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] Improving bug reporting documentation
> Date: Tue, 08 Nov 2011 04:06:20 -0000
> From: suvayu ali <fatkasuvayu+linux@gmail.com>
> X-Patchwork-Id: 1033
> Message-Id: <20111108000620.6fd433b6@kuru.homelinux.net>
> To: Org mode mailing list <emacs-orgmode@gnu.org>
> 
> Hi Bastien and others,
> 
> Lately I have been seeing a lot of bug reports sent using the
> org-submit-bug-report. The reporter usually reports the bug from a
> session they have been using with their full blown customisations. And
> often they are requested to reproduce the bug with emacs -Q. So I
> thought it would be easier if the manual mentioned this little detail.
> A patch is attached.
> 
> Hope this helps.
> 
> PS: I marked the patch as TINY CHANGE.
> 
> 
> diff --git a/doc/org.texi b/doc/org.texi
> index 4a547d0..1bc9a98 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -987,6 +987,36 @@ @section Feedback
>  that you only need to add your description.  If you re not sending the Email
>  from within Emacs, please copy and paste the content into your Email program.
>  
> +Sometimes you might face a problem due to an error in your Emacs or Org-mode
> +setup.  Before reporting a bug, it is very helpful to start Emacs with minimal
> +customisations and reproduce the problem.  Doing so often helps you determine
> +if the problem is with your customisation or with Org-mode itself.  You can
> +start a typical minimal session with a command like the example below.
> +
> +@example
> +$ emacs -Q -l /path/to/minimal-org.el
> +@end example
> +
> +However if you are using Org-mode as distributed with Emacs, a minimal setup
> +is not necessary.  In that case it is sufficient to start Emacs as @code{emacs
> +-Q}.  The @code{minimal-org.el} setup file can have contents as shown below.
> +
> +@example
> +;;; Minimal setup to load latest `org-mode'
> +
> +;; activate debugging
> +(setq debug-on-error t
> +      debug-on-signal nil
> +      debug-on-quit nil)
> +
> +;; add latest org-mode to load path
> +(add-to-list 'load-path (expand-file-name "/path/to/org-mode/lisp"))
> +(add-to-list 'load-path (expand-file-name "/path/to/org-mode/contrib/lisp"))
> +
> +;; activate org
> +(require 'org-install)
> +@end example
> +
>  If an error occurs, a backtrace can be very useful (see below on how to
>  create one).  Often a small example file helps, along with clear information
>  about:
> 

next prev parent reply	other threads:[~2011-12-12 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 23:06 Improving bug reporting documentation Suvayu Ali
2011-12-12 16:34 ` Bastien Guerry [this message]
2011-12-12 16:47 ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111212163414.2622313E90@myhost.localdomain \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).