Hello,
Bernt Hansen writes:
> I noticed that the new exporter has one extra blank line in the output
> of source and example blocks while the old exporter does not.
I removed a couple of newline characters in org-e-html.el. The problem
should be fixed. Could you confirm this?
Regards,
--
Ni
Hello,
Michael Brand writes:
> For this alignment with M-q (fill-paragraph) and C-c C-c on
> description list I suggest a formatting cookie, similar to Org table
> where "<19>" on any row narrows the column:
> - when any item contains only "<>": align all descriptions to the
> widest term of t
Hello,
Robert Yates writes:
> What is the reason for disallowing the commands for adding and
> toggling checkboxes on descripton list items (that is "- partA ::
> partB" list items) ? (attempting to do so results in the message
> "Cannot add a checkbox to a description list item")
Good questio
Hello,
William Crandall writes:
> You mentioned before using "filters." I take it these are the ones
> described in org-export-filters.el (line 1775), "The Filter System."
> Has anyone written up any worked examples of these?
org-e-ascii.el and org-e-html.el both use filters. Also, I posted a
Nicolas Goaziou writes:
> Bernt Hansen writes:
>
>> I noticed that the new exporter has one extra blank line in the output
>> of source and example blocks while the old exporter does not.
>
> I removed a couple of newline characters in org-e-html.el. The problem
> should be fixed. Could you conf
Hi Nicolas,
Are there analogous variables to
--8<---cut here---start->8---
(setq org-export-author-info nil)
(setq org-export-creator-info nil)
(setq org-export-time-stamp-file nil)
--8<---cut here---end--->8---
in the new e
Hello,
Bernt Hansen writes:
> Are there analogous variables to
>
> (setq org-export-author-info nil)
> (setq org-export-creator-info nil)
> (setq org-export-time-stamp-file nil)
>
> in the new exporter to control export of the author, creator, and
> timestamp by default?
>
> I haven't been able
Nicolas Goaziou writes:
> I do not notice anything like this. There are many compilation errors
> on some files, but they are the same before and after removing an
> org-e-*.el file.
I get them very consistently, in both Emacs 23.3 and 24.1, with and
without my patches.
org-mode> rm lisp/org-{ex
Hello,
Achim Gratz writes:
> If I pre-load either org-element or org-export (or both) and they have
> been byte-compiled things get worse to the point where Emacs simply
> craps out. I don't know why this is happening, but it's very obvious
> that these files can't be used byte-compiled. Whate
Nicolas Goaziou writes:
> What happens if you revert commit:
>
> 4b0121fc2a18e00ce2c80e145563e41accfc4ddb
I've played with that before. As I already said, the requires and maybe
even the circular dependencies are not the problem. It apparently
croaks on the runtime use of cl macros and/or func
Achim Gratz writes:
> It apparently croaks on the runtime use of cl macros and/or functions,
> but just exactly how is a mystery to me.
org-element uses `every' twice. Since this function doesn't belong to cl
but cl-extra, could it be the source of the problem?
If so, it may be worth a try to r
Nicolas Goaziou writes:
> Achim Gratz writes:
>
>> It apparently croaks on the runtime use of cl macros and/or functions,
>> but just exactly how is a mystery to me.
>
> org-element uses `every' twice. Since this function doesn't belong to cl
> but cl-extra, could it be the source of the problem?
Hello,
"Sebastien Vauban"
writes:
> With the new exporter, most things work. What does not work:
> - macro does not get executed (no string in orange color),
Macro are meant to produce contents, not to talk to back-ends. Every
text they produce will be protected.
> - the =\end{verbatim}= dis
Hello Nicolas,
Many thanks for explaining the logic and functionality
of the new exporter.
I confess I am puzzled by the choice to drop the ability
to apply attributes to links.
The use case I'm aiming for is a standard HTML feature:
3.2.3.2 The 'title' attribute
The title attribute repr
14 matches
Mail list logo
