Re: [O] org2pdf export broken on parabola
Hi Divan, 2016ko abuztuak 23an, Divan Santana-ek idatzi zuen: > > Hi All, > > So I'm pretty new to Emacs and org-mode. Loving it so far. > > On parabola (FSF approved Arch linux distro) the default emacs org2pdf > function is broken. > > Details on the reason here: > > https://lists.parabola.nu/pipermail/assist/2016-August/000716.html > > Something about freedom licensing issues I think. > > Two questions: > > 1) How can I work around this issue on parabola so I can export org 2 > pdf? > > 2) If there is an issue with the texlive fonts should org upstream not > default to a free software compatible font? So org2pdf works on FSF > approved distros? AFAIK the default org export does not do any font selection (either of free or non-free fonts). So it should work just fine. Obviously it does not for you, though. It would be helpful if you could send an example of an org document (it can be short/meaningless, as long as it demonstrates the problem), the latex it produces on export, and the latex compiler log file, so that we can see the error. Looking at that, we will probably be able to diagnose your problem more precisely, and figure out what needs to be changed to make it work. Thanks, -- Aaron Ecay
Re: [O] Bug: spurious newline after comment [8.3.5 (release_8.3.5-1087-g6b52bc @ /Users/maarhart/elisp/org-mode/lisp/)]
Hello, maarh...@htkl1201-01.hum.jyu.fi (MartÃn Hartmann) 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 mailing list. > > > Hi, > > I am not sure if this was reported before because I don't follow this list: > > http://emacs.stackexchange.com/questions/22574/orgmode-export-how-to-prevent-a-new-line-for-comment-lines > > I have tried it in both the bleeding edge version and in the version > that comes by default in emacs (is it 8.2.10?). This seems to be a bug > in 8.3.5 because this does not occur in 8.2.10. This is a feature. Comments (starting with "# ") are not inline, so they really break paragraphs. The purpose of this blank line is to also break paragraphs in the export output. Note that you can - use somewhat inline comments with @@comment:...@@ syntax - remove commented lines the way you like using a hook: `org-export-before-processing-hook'. Regards, -- Nicolas Goaziou
Re: [O] ox-md.el: Export TOC and Footnotes as Markdown rather than HTML
Hello, Jake Romer writes: > I just submitted it. Thanks! Great! Let me know when the process is over so I can apply the changes. Regards, -- Nicolas Goaziou
Re: [O] recalculate tables
Hello, Michael Welle writes: > I have a few of those, that worked in the past. So I think the behaviour > had changed some time in the past year or so. Quite possible. I made some invasive changes in "org-table.el" a while ago. > I liked the old behaviour (but it's not super important for me) The problem is that I don't know what is "the old behaviour". The fact that column formulas do not apply in table headers has been there for ages. What is that behaviour? Regards, -- Nicolas Goaziou
Re: [O] Footnotes in image captions
Hello, Arun Isaac writes: > Footnotes in image captions are not picked up and published. Is this > intended behaviour? Yes, it is. > If it is intended behaviour, would it not be nice to allow footnotes > in image captions too? I think it is a can of worms. For example, you cannot properly number footnotes anymore since there's no guarantee a caption is going to be exported. Note that footnote references are explicitly excluded from keywords in org-element.el. Regards, -- Nicolas Goaziou
Re: [O] recalculate tables
Hello, Nicolas Goaziou writes: > Hello, > > Michael Welle writes: > >> I have a few of those, that worked in the past. So I think the behaviour >> had changed some time in the past year or so. > > Quite possible. I made some invasive changes in "org-table.el" a while > ago. SCM revealed that I 'fixed' one table with an empty header around Christmas last year. But I can't remember if I found the problem a few weeks earlier or a few months. >> I liked the old behaviour (but it's not super important for me) > > The problem is that I don't know what is "the old behaviour". The fact > that column formulas do not apply in table headers has been there for > ages. Yes, Russell suggested something like that. That puzzles me a bit. The table, that I mentioned above is updated every three months. Even if the formulas would not have been applied three or four times before I found out about it, I wouldn't have used Org version 7.8 (the one that Russell uses) or earlier back at that time, I think. If the change is somewhere in, let's say, org-table.el, one thing I can vaguely imagine is that an older org-table.el was lying around and got loaded. I experienced something like that with ob-sh.el and ob-shell.el. But on the other hand, I have trouble to understand how that could happen (other than with ob-sh the file name stayed the same). > What is that behaviour? I have a handful of tables like the following: |---+---+| | 3 | 4 || |---+---+| #+TBLFM: $3=$2-$1 I don't add data to them very frequently. But since they all have the third column filled, I think recalculating had worked in tables formated like that before. If you give me a week or so I will try to find the change set that introduced the current behaviour. Regards hmw
Re: [O] Footnotes in image captions
> I think it is a can of worms. For example, you cannot properly number > footnotes anymore since there's no guarantee a caption is going to be > exported. In my use case, I can guarantee that all captions will be exported. So, could footnotes in captions be implemented as an optional feature that the user can enable by setting some variable? Or will that be too much trouble? Regards, Arun Isaac. signature.asc Description: PGP signature
[O] Problem exporting file with code references
Hi list, I am trying to run the last example on the documentation page: http://orgmode.org/manual/Literal-examples.html and I am running into a problem. The following is the full org file I am trying to export: --- #+BEGIN_SRC emacs-lisp -n -r (save-excursion (ref:sc) (goto-char (point-min))) (ref:jump) #+END_SRC In line [[(sc)]] we remember the current position. [[(jump)][Line (jump)]] jumps to point-min. --- When trying to export (I tried html or latex), I get the following error message: 'user-error: Unable to resolve link: "sc"'. Trying to investigate, it appears that the `org-babel--normalize-body' function (ob-core.el) removes the references "(ref:sc)" and "(ref:jump)" from the code block prior to execution. This happens during the call to `org-babel-exp-process-buffer' when `org-export-babel-evaluate' is non-nil (in ox.el). From that point, the source block content does not contain the "(ref:sc)" and "(ref:jump)" text. Consequently, when reaching the `org-export-resolve-coderef' function, the link is not found in the code and the error is returned. I get this failure with version: Org-mode version 8.3.5 (release_8.3.5-1079-g61dd51.dirty @ ~/org_git/org-mode/lisp/) For reference, the same file get exported without issue when using an older version: Org-mode version 8.3.5 (8.3.5-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20160815/) Am I missing something here? Is this a bug? Any help would be greatly appreciated. Thanks, thibault
