emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: error enlighting file: [8.0-pre (release_8.0-pre-335-g4c426b-git @ org-loaddefs.el can not be found!)]
Date: Mon, 15 Apr 2013 09:05:00 +0200	[thread overview]
Message-ID: <20130415070500.GA2572@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87obdksiiy.fsf@es.gnu.org>

On Fri, Apr 12, 2013 at 02:24:21AM +0200, David Arroyo Menéndez wrote:
> current state:
> ==============
> (setq
>  org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe
> 		      org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
>  org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook)


>  org-confirm-elisp-link-function 'yes-or-no-p
>  org-metadown-hook '(org-babel-pop-to-session-maybe)
>  org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
>  )

While submitting bug reports, could you please try with a minimal setup
first?  Otherwise the bug report becomes unnecessarily cluttered, and
might be difficult to reproduce.  For an example, please look in the
manual, (info "(org) Feedback").

BTW, to others, is it by any chance possible to check how emacs was
started (if -q or -Q was present among the command line options)?  Then
a message could be shown about minimal testing with a setup when users
call `org-submit-bug-report'.



Open source is the future. It sets us free.

  parent reply	other threads:[~2013-04-15  7:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12  0:24 Bug: error enlighting file: [8.0-pre (release_8.0-pre-335-g4c426b-git @ org-loaddefs.el can not be found!)] David Arroyo Menéndez
2013-04-12  6:51 ` Nicolas Goaziou
2013-04-15  7:05 ` Suvayu Ali [this message]
2013-04-15 15:49   ` Bastien
2013-04-15 16:05     ` Suvayu Ali
2013-04-15 16:22       ` Suvayu Ali

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:

  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=20130415070500.GA2572@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).