emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "B.V. Raghav" <bvraghav@iitk.ac.in>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Export [8.3.2 (8.3.2-48-g700b8e-elpa @ /home/bvr/.emacs.d/elpa/org-20151214/)]
Date: Fri, 18 Dec 2015 06:11:35 +0530	[thread overview]
Message-ID: <87fuz0si4g.fsf@think.bvr.lan> (raw)
In-Reply-To: <87io3wc1uq.fsf@alphaville.usersys.redhat.com> (Nick Dokos's message of "Thu, 17 Dec 2015 14:27:25 -0500")

Nick Dokos <ndokos@gmail.com> writes:

> "B.V. Raghav" <bvraghav@iitk.ac.in> writes:
>
>> Remember to cover the basics, that is, what you expected to happen and
>> what in fact did happen.  You don't know how to make a good report?  See
>>
>>      http://orgmode.org/manual/Feedback.html#Feedback
>>
>> Your bug report will be posted to the Org-mode mailing list.
>> ------------------------------------------------------------------------
>>
>> 1. find-file new-file.org
>> 2. insert template default + texinfo
>> 3. fill in title, subtitle, description etc.
>> 4. fill some random nodes
>> 5. export using <C-c> <C-e> i i
>>
>> Following backtrace of the error:
>>> Debugger entered--Lisp error: (wrong-type-argument listp #("Modeling
>>> notes for Mged" 0 23 (:parent (#1))))
>>> ...
>>
>>
>> Emacs  : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.2)
>>  of 2015-10-25 on trouble, modified by Debian
>> Package: Org-mode version 8.3.2 (8.3.2-48-g700b8e-elpa @
>> /home/bvr/.emacs.d/elpa/org-20151214/)
>
> I cannot reproduce it.

This is a duplicate to `bug#22182: 24.5; Org Mode Export' from debbugs,
filed by the same user.

>
> I tried with both current master and current maint: the latter is just two
> commits ahead of the elpa version you have at this point and neither of
> those two seems to have anything to do with texinfo. It seems plausible
> that this might be caused by something in your setup: use
>
>    emacs -q -l /some/minimal/init/file.el
>
> to start emacs without (most of) your setup and see if you can reproduce
> the problem there.
>
> There are two other things you can do (and that's general advice, not
> limited to this particular problem) to help us help you: 1) specify
> steps 3 and 4 above more precisely (tell us *exactly* what you typed)
> and 2) use uncompiled org-mode to produce the backtrace - you can reload
> org-mode and make it use uncompiled code with
>
> C-u M-x org-reload RET
>
> See
>
>    (info "(org) Feedback")
>
> in particular the section entitled "How to create a useful backtrace"
> for more details.

This was highly informative, as well as educational. I will look in
detail later on.

>
> --
> Nick
>
>
>
>

Thanks,

-- 
(B.V. Raghav)

      reply	other threads:[~2015-12-18  0:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15 23:05 Bug: Export [8.3.2 (8.3.2-48-g700b8e-elpa @ /home/bvr/.emacs.d/elpa/org-20151214/)] B.V. Raghav
2015-12-17 19:27 ` Nick Dokos
2015-12-18  0:41   ` B.V. Raghav [this message]

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=87fuz0si4g.fsf@think.bvr.lan \
    --to=bvraghav@iitk.ac.in \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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
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

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