Re: [O] compilation issues of new export framework

Nicolas Goaziou gmail.com> writes: > On the other hand, `org-element-type' and al. from org.el are called > less often. So, it is not a problem if they are compiled as function > calls. They are normally not compiled as function calls, only in single mode. Regarding commit 6b7101b91, did you int

Re: [O] new exporter fails to output footnotes?

Samuel Wales writes: > On 2/10/13, Nicolas Goaziou wrote: >> For now, you can't, but that's a problem. I think the framework needs >> a step before the template function, in order to add some persistent >> data, even in case of a body-only export. > > Thank you for the answer. > > Is there a way

Re: [O] LaTeX export: Theorem with an author

Vincent Beffara writes: > It does seem more consistent with things like fig captions and so on - > thanks for implementing! A little bit more verbose but that's fine ... > and I agree that the previous "#+begin_theorem Somebody" felt a bit > vague. How about a middle ground like this ? > > #+begi

Re: [O] Fwd: Re: Bug? in texinfo exporter

t...@tsdye.com (Thomas S. Dye) writes: > Aloha Jon, [...] > Yes, I believe you are right. The commas are not the culprits. > Apologies for the red herring. > > Perhaps Nicolas should revert the commit? Could you check if this is > the right thing to do? My fix isn't about the comma. Didn't it

[O] colorg: Weekly report

Hi, Org friends. Here is my weekly report on colorg development. colorg is a tool for real-time collaborative edition meant for Org files in the long run, and located at https://github.com/pinard/colorg. There is a client in Emacs Lisp and a server in Python. There were no change at all on the

Re: [O] Feature: Group and limit items in agenda

Thanks for the new feature. I tried and it works well for what it intended to do. However, I still haven't found a way to do the kind of things I mentioned. My intention is to limit the number of tasks in each category. For the new proposed 'org-agenda-max-todos', I can only limit the number of TO

[O] org-element-paragraph-parser fails

Remove the spaces before #+name OR take out the '- item' and org-export-dispatch succeeds. As is, it fails with org-element-paragraph-parser: Invalid search bound (wrong side of point) , | * export dispatcher | | - item | | #+name: xyz | #+BEGIN_SRC emacs-lisp | (pwd) | #+E

Re: [O] Fwd: Re: Bug? in texinfo exporter

Aloha Jon, Jonathan Leech-Pepin writes: > -- Forwarded message -- > From: "Jonathan Leech-Pepin" > Date: Feb 9, 2013 8:57 AM > Subject: Re: [O] Bug? in texinfo exporter > To: "Thomas S. Dye" > Cc: > Just realized I hit reply not reply-all > > If Nick's fix fixes it do much the

[O] hlines in babel output

Hi, I have the following Org document where I would like to add some extra hlines to the output. I'm using babel. I tried the ascii package but couldn't find anything giving me extra hlines. I'd also prefer to stick to just babel. Here's the example: #+begin_src org #+TITLE:hline test * So

Re: [O] Problem with org-html-format-latex

> > thanks for reporting this and for the patch, I've push > > a slightly different fix. Please test and let me know. > > Sounds good to me, thanks! ... well it did sound good to me, but it still fails. Put this in *scratch*, (org-html-format-latex "x" 'mathjax) and C-x C-e. Within org-format-

Re: [O] Problem with org-html-format-latex

> thanks for reporting this and for the patch, I've push > a slightly different fix. Please test and let me know. Sounds good to me, thanks! /v > > Best, > > -- > Bastien

Re: [O] LaTeX export: Theorem with an author

Hi, > There's no right way at the moment: I forgot to implement this. > > Anyway, since this feature was LaTeX only, what do you think about the > following syntax (which doesn't work yet): > > #+attr_latex: :options [Newton] > #+begin_theorem > Blah. > #+end_theorem > > It is heavier but it see

Re: [O] internal links not being followed; instead, offer to create new heading

On Sun, Feb 10, 2013 at 4:28 PM, Brian van den Broek wrote: > On 10 February 2013 16:21, John Hendy wrote: >> On Sun, Feb 10, 2013 at 12:53 PM, Brian van den Broek >> wrote: >>> Hi all, >>> >>> I am having trouble with following internal org links. After carefully >>> reading the documentation (

Re: [O] internal links not being followed; instead, offer to create new heading

On 10 February 2013 16:21, John Hendy wrote: > On Sun, Feb 10, 2013 at 12:53 PM, Brian van den Broek > wrote: >> Hi all, >> >> I am having trouble with following internal org links. After carefully >> reading the documentation (especially 4.2 Internal Links >>

Re: [O] new exporter fails to output footnotes?

On 2/10/13, Nicolas Goaziou wrote: > For now, you can't, but that's a problem. I think the framework needs > a step before the template function, in order to add some persistent > data, even in case of a body-only export. Thank you for the answer. Is there a way to run the old exporter then? I'

Re: [O] new exporter fails to output footnotes?

Samuel Wales writes: > On 2/10/13, Nicolas Goaziou wrote: >> I assume you wonder why there's no footnote definition. That's because >> this is a body-only export. Footnote definitions belong to the global >> template, which is ignored when this option is active. > > Why would you not want footno

Re: [O] Icalendar-export, priorities missing, possible bug

Hi, 2013-02-10 20:31, Nicolas Goaziou skrev: Hello, Anders Johansson writes: When I'm exporting to icalendar, the priorities of todo items (or perhaps any items) don't get carried through correctly. It always falls back to priority 5 (the default). After doing some edebugging I found that

Re: [O] org-latex-classes with functions, incomplete doc

Florian Beck writes: > Nicolas Goaziou writes: > >>> (toc-title (if (plist-get info :toc-title) >>> (org-element-property :toc-title headline))) >> >> There's no :toc-title property in the communication channel. The >> exhaustive list of its properties is written in ox.e

Re: [O] internal links not being followed; instead, offer to create new heading

On Sun, Feb 10, 2013 at 12:53 PM, Brian van den Broek wrote: > Hi all, > > I am having trouble with following internal org links. After carefully > reading the documentation (especially 4.2 Internal Links > ) with the following > test.org file, I would e

Re: [O] latex code block evaluation

Hi Henry, henry atting wrote: > I have this latex code block: > > #+begin_src latex :file foo.pdf > \documentclass{article} > \begin{document} > ...some text... > \end{document} > #+end_src > > After evaluation the resulting file looks like this: > > article ...some text... > > I do not understan

Re: [O] comments after paragraph remove newline

Hello, Samuel Wales writes: > If there were a blank line above the comment, the newline removal > would be appropriate, but not when there is no blank line above it. > > === input > > *** test > no comments > > one > > comments > # test > > two > > === ascii > > no comments > > one > > comments

Re: [O] Bug: Additional empty line in TeXinfo export of #+BEGIN_SRC ... #+END_SRC [7.9.3e (7.9.3e-957-g03e433 @ /home/fifr/.emacs.d/el-get/org-mode/lisp/)]

Hello, Frank Fischer writes: > Consider the following minimal org-file: > > === One line before > #+BEGIN_SRC shell > Some example > #+END_SRC > One line after > === > > When exporting to texi, the file contains an additional empty line > before the "@end example": > > === > ... > One line befor

Re: [O] Scheduling makes link disappear

Hi, Bastien, Thanks! That fixes it and doesn't break any of the agenda views that I use. Best regards, Thomas Bastien writes: > Hi Thomas, > > Thomas Morgan writes: > >> In an Org TODO list, scheduling an item that contains a link can cause >> the link to disappear. > > Thanks very for the r

Re: [O] new exporter fails to output footnotes?

On 2/10/13, Nicolas Goaziou wrote: > Beware, `org-export-to-buffer' expects a string as its second argument, Will fix thanks. > I assume you wonder why there's no footnote definition. That's because > this is a body-only export. Footnote definitions belong to the global > template, which is igno

Re: [O] new exporter fails to output footnotes?

Hello, Samuel Wales writes: > Surely this is pilot error someplace. > > (org-export-to-buffer > 'html > (get-buffer-create "test") > t > nil > t) > Beware, `org-export-to-buffer' expects a string as its second argument, not a buffer. So: (org

Re: [O] Icalendar-export, priorities missing, possible bug

Hello, Anders Johansson writes: > When I'm exporting to icalendar, the priorities of todo items (or > perhaps any items) don't get carried through correctly. It always > falls back to priority 5 (the default). > > After doing some edebugging I found that > > (string-match org-priority-regexp

[O] Bug: Additional empty line in TeXinfo export of #+BEGIN_SRC ... #+END_SRC [7.9.3e (7.9.3e-957-g03e433 @ /home/fifr/.emacs.d/el-get/org-mode/lisp/)]

Consider the following minimal org-file: === One line before #+BEGIN_SRC shell Some example #+END_SRC One line after === When exporting to texi, the file contains an additional empty line before the "@end example": === ... One line before @example Some example @end example One line after ... ==

[O] Icalendar-export, priorities missing, possible bug

Hi, When I'm exporting to icalendar, the priorities of todo items (or perhaps any items) don't get carried through correctly. It always falls back to priority 5 (the default). After doing some edebugging I found that (string-match org-priority-regexp hd) [org-icalendar.el:539] never se

Re: [O] orgstruct-mode with custom headline prefix

Christopher Schmidt writes: > Here is the patch. Now one just needs > > ;; Local Variables: > ;; eval: (orgstruct-mode 1) > ;; orgstruct-heading-prefix-regexp: ";;; " > ;; End: This is in master now. The commit is a3f6570. Christopher

Re: [O] org-latex-classes with functions, incomplete doc

Nicolas Goaziou writes: >> (toc-title (if (plist-get info :toc-title) >> (org-element-property :toc-title headline))) > > There's no :toc-title property in the communication channel. The > exhaustive list of its properties is written in ox.el, at "The > Communication Ch

[O] internal links not being followed; instead, offer to create new heading

Hi all, I am having trouble with following internal org links. After carefully reading the documentation (especially 4.2 Internal Links ) with the following test.org file, I would expect that C-c C-o on the link text in the bar tree would jump to the cor

[O] comments after paragraph remove newline

If there were a blank line above the comment, the newline removal would be appropriate, but not when there is no blank line above it. === input *** test no comments one comments # test two === ascii no comments one comments two === Thanks. Samuel -- The Kafka Pandemic: http://thekafka

Re: [O] org-latex-classes with functions, incomplete doc

Florian Beck writes: > Ok, I tried this. There is a problem, however. This is what I came up > with: > > #+BEGIN_SRC emacs-lisp > (defun fb/org-latex-headline (headline contents info) > (let* ((full-section (org-latex-headline headline contents info)) I suggest (org-export-with-backend 'latex

[O] latex code block evaluation

I have this latex code block: #+begin_src latex :file foo.pdf \documentclass{article} \begin{document} ...some text... \end{document} #+end_src After evaluation the resulting file looks like this: article ...some text... I do not understand this. As far as I know it is possible to define the

Re: [O] org-latex-classes with functions, incomplete doc

Thanks for your explanations, very much appreciated. Nicolas Goaziou writes: > the proper way to do this is to define a derived back-end with > a custom headline translation function. Ok, I tried this. There is a problem, however. This is what I came up with: #+BEGIN_SRC emacs-lisp (defun fb/o

[O] [Bug] Yasnippet/Org: properties messed up when expanding $1

Hi! * Karl Voit wrote: > > I do face strange behavior when using yasnippet with Org-mode: So there does not seem to be anybody who is able to fix this issue. Is there at least somebody who can confirm this weird bug? Thanks! > ,[ Snippet «test» ] >| # name : Testing yasnippet/org issue >|

[O] bug#13668: 24.2.93; strike-through in org mode

On Sun Feb 10 2013 Bastien wrote: > Please provide a patch. I'd much appreciate if the org developers could do that. I have enough such things on my own emacs agenda,

[O] bug#13668: 24.2.93; strike-through in org mode

"Roland Winkler" writes: > I do not find the info nodes on "Structural markup elements" > particularly overloaded. The node "Emphasis and monospace" is just > one short paragraph, and org-fontify-emphasized-text could esily be > mentioned there -- unless this variable also affects other things, >

[O] bug#13668: 24.2.93; strike-through in org mode

On Sun Feb 10 2013 Bastien wrote: > > Why put this in a separate FAQ? Aren't the info pages the first > > source of information for such things? > > Depends. We try to keep the info manual readable, and it's already > quite long. If you can find a good place in the manual, please send > a patch.

Re: [O] org-latex-classes with functions, incomplete doc

Hello, Florian Beck writes: > the docstring for `org-latex-classes' says: > > "Instead of a list of sectioning commands, you can also specify > a function name. That function will be called with two > parameters, the (reduced) level of the headline, and a predicate > non-nil when the headline s

[O] bug#13668: 24.2.93; strike-through in org mode

Hi Roland, "Roland Winkler" writes: > There are spaces both between the 2nd and 3rd line, and between the > 5th and 6th line. -- Possibly, the regexp matcher could distinguish > in a smarter way between word constituents and no word constituents. Sorry I wasn't clear: by default, space is not

[O] org-latex-classes with functions, incomplete doc

Hi, the docstring for `org-latex-classes' says: "Instead of a list of sectioning commands, you can also specify a function name. That function will be called with two parameters, the (reduced) level of the headline, and a predicate non-nil when the headline should be numbered. It must return a

Re: [O] compilation issues of new export framework

Completing myself, Nicolas Goaziou writes: > Speed is the whole point, indeed. A quick profiling with and without > defsubst gives me: > > | defsubst | org-element-parse-buffer | 10 | 16.252699 |1.6252699 | > | defun| org-element-parse-buffer | 10 | 19.812426 | 1.9812425999 | > > It is a

[O] bug#13668: 24.2.93; strike-through in org mode

On Sun Feb 10 2013 Bastien wrote: > > But it appears to me that this feature could use a > > more sophisticated regexp matcher. Note that the 5th and 6th line > > are not striked through. > > Because the space isn't allowed within +...+ fontified constructs. There are spaces both between the 2nd

Re: [O] compilation issues of new export framework

Achim Gratz writes: > It comes from the two autoloads, or probably only the second one as the > first is later declare-function'ed anyway. If you declare these, then > the defsubst get sometimes compiled as function calls and sometimes as > inlined functions (the normal mode of compilation inlin

Re: [O] compilation issues of new export framework

Nicolas Goaziou writes: > Yes, I noticed this one too, but I don't know yet from where it could > come from. It comes from the two autoloads, or probably only the second one as the first is later declare-function'ed anyway. If you declare these, then the defsubst get sometimes compiled as functio

Re: [O] [New exporter] custom emphasis in org-emphasis-alist

Completing myself, > On the other hand, you may be able to parse custom markup with the help > of a filter: > > #+begin_src emacs-lisp > (defun my-special-markup (text backend info) > (when (and (org-export-derived-backend-p backend 'html) > (string-match "\\([ ('\"{]\\|^\\)\\(

Re: [O] [New exporter] custom emphasis in org-emphasis-alist

Hello, Gregor Kappler writes: > I am currently migrating my system and contribute my first stop: > custom emphasis characters that I use extensively: > - "!" is used for exclamations, > - "?" for questions, and > - "#" for in-text comments that I do not want exported. Emphasis characters are no

Re: [O] How to get === on a line by itself to be a special string

Hello, Samuel Wales writes: > I want separators like this: > > === > > to be treated as a special string in HTML. This was the > case in the old exporter. [...] > I don't want them to be interpreted as code. I don't want > to turn off all code just to get this one thing to work. I don't wan

Re: [O] how to indent plain lists in ASCII

Hello, Samuel Wales writes: > The old exporter indented plain lists. > > This does not seem to fix it: > > (add-to-list 'org-export-filter-plain-list-functions >(lambda (plain-list back-end &rest _rest) > (if (eq back-end 'ascii) > (replace-regexp-in-string "^