From: Shlomi Vaknin <shlomivaknin@gmail.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Exception when trying to export inlined-code [8.3.4 (8.3.4-9-gfda14f-elpa @ ~/.emacs.d/elpa/org-20160307/)]
Date: Wed, 9 Mar 2016 21:45:38 -0800 [thread overview]
Message-ID: <CANyzh=gr-b+Jtyj9_F7S0XVFa=rxTqxZ4x6Q+kyf3wv1608xng@mail.gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1603091838470.1940@charles-berrys-macbook.local>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
>
> Its been in master since Jan 2015.
Yeah, I guess I didnt update my packages in quite a while :P
>
> It works for me as does the same with `emacs-lisp' as the language
> under latex or html export to buffer or file using: Org-mode version
> 8.3.4 (release_8.3.4-635-g268486 ...) producing the expected document.
>
> Not sure what gives. Perhaps a mixed installation of org-mode?
>
So I checked this (to the best of my knowledge), I searched and removed
everything that had to do with org-mode, got master, compiled and installed
it. (org-version) now gives "Org-mode version 8.3.4
(release_8.3.4-635-g268486 @ ~/org-mode/org-mode/lisp/)"
and although the minimal example I posted above *does* work now, my real
file does not. I managed to make another non-working example (should I make
a gif showing what I see?):
---------------------------------------
- src_elisp{3} {{{results(=3=)}}}
* B
- src_elisp{3} {{{results(=3=)}}}
-
-
-
- src_elisp{3} {{{results(=3=)}}}
- src_elisp{2} {{{results(=2=)}}}
- {{{results(=2=)}}}
---------------------------------------
again, removing any line from this makes export work again. Otherwise I get
=org-element--current-element: Wrong type argument: integer-or-marker-p,
nil=
This might be something silly, but I really dont know what else to do and I
am quite stuck, I need to present my org file to emacs-hostile people :|
I have a new installation of emacs (used =find= to remove all other emacs
paths), new org-mode compiled from source (looked through =find= as well as
checked all 'load-path locations and removed anything I found) and no
custom init files.... What else could I check on my system?
I am using a mac, if that makes any differences..
Thanks for your help!
[-- Attachment #2: Type: text/html, Size: 2667 bytes --]
next prev parent reply other threads:[~2016-03-10 5:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 21:27 Bug: Exception when trying to export inlined-code [8.3.4 (8.3.4-9-gfda14f-elpa @ ~/.emacs.d/elpa/org-20160307/)] Shlomi Vaknin
2016-03-10 3:00 ` Charles C. Berry
2016-03-10 5:45 ` Shlomi Vaknin [this message]
2016-03-10 6:33 ` Bill Burdick
2016-03-10 9:21 ` Nicolas Goaziou
2016-03-11 21:13 ` Shlomi Vaknin
2016-03-13 17:34 ` Nicolas Goaziou
2016-03-13 19:34 ` Shlomi Vaknin
2016-03-13 19:45 ` Nicolas Goaziou
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='CANyzh=gr-b+Jtyj9_F7S0XVFa=rxTqxZ4x6Q+kyf3wv1608xng@mail.gmail.com' \
--to=shlomivaknin@gmail.com \
--cc=ccberry@ucsd.edu \
--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
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).