>>
>> I don’t see org-export-use-babel in available options. I cannot customise it.
>>
>> '(org-export-use-babel (quote inline-only))
>>
>> Seems to have no effect. Is that so because, as you say later, users are not
>> supposed to touch this option?
>
> No. You must have an older version
Jarmo Hurri writes:
> Running 'make cleanall' didn't help.
>
> However, a fresh clone followed by a reconfiguration of local.mk solved
> the issue. Most likely the result of a local.mk that is no longer
> consistent.
Just FYI, you can avoid having to re-clone the repo by
Nicolas Goaziou writes:
> Let's adjust the patch, then. Thank you!
Hi Nicolas,
Here is the new patch. I took the liberty of using a macro to replace
the code that was duplicated in the four agenda functions. Please let
me know if you would like any further changes.
> On Aug 19, 2017, at 7:24 PM, Vikas Rawal
> wrote:
>
>
>>
>> There is a bug in the documentation -- `org-export-babel-evaluate' is
>> obsolete. It should say `org-export-use-babel’.
>
> I don’t see org-export-use-babel in available options. I cannot
>
> There is a bug in the documentation -- `org-export-babel-evaluate' is
> obsolete. It should say `org-export-use-babel’.
I don’t see org-export-use-babel in available options. I cannot customise it.
'(org-export-use-babel (quote inline-only))
Seems to have no effect. Is that so because,
> On Aug 19, 2017, at 6:10 PM, Vikas Rawal
> wrote:
>
>>
>>
>> The first problem is that you have babel code *inside* a macro. Since
>> macros are run after babel executes, nothing will happen.
>
> From the manual: "Org expands macros at the very beginning
>
>
> The first problem is that you have babel code *inside* a macro. Since macros
> are run after babel executes, nothing will happen.
From the manual: "Org expands macros at the very beginning of the export
process.”
These macros run fine if I allow code evaluation. Macro replacement
Looks like htmlize was removed from contrib a few days ago
(commit d0ced9894) which is probably the cause of your issue. You can get
it from https://github.com/hniksic/emacs-htmlize
You can generate a new local.mk by running 'make local.mk'. You may have to
remove or rename the existing local.mk
On 2017-08-19 08:57, Nicolas Goaziou wrote:
It is not possible in the general case. The export block is not
guaranteed to contain a complete environment; it isn't necessarily
displayable either.
Thank you for your kind attention, anyway :) .
I think this is an acceptable workaround. I think
On 19 August 2017 at 09:50, Nicolas Goaziou wrote:
> Adam Spiers writes:
>> I was also expecting to be able to use #+NAME: foo in front of a
>> headline
>
> You cannot use a NAME keyword to a headline (or an inlinetask).
> CUSTOM_ID is morally
Eric Abrahamsen writes:
> Subject: [PATCH 2/2] Inherit TIMEZONE and LOCATION properties in iCalendar
> export
>
> * lisp/ox-icalendar.el (org-icalendar-entry): Both properties now
> optionally inherit, depending on value of
> `org-use-property-inheritance'.
> *
> On Aug 19, 2017, at 1:36 PM, Vikas Rawal
> wrote:
>
>
>> On 20-Aug-2017, at 12:57 AM, Nicolas Goaziou wrote:
>>
>> Hello,
>>
>> Vikas Rawal writes:
>>
>>> My org-version (latest on org ELPA) is:
Nicolas Goaziou writes:
> Eric Abrahamsen writes:
>
>> It's a little strange, because the manual section for this specifically
>> mentions the inheritance of the LOCATION property, but the code doesn't
>> do it. Shall I add it in? It makes sense
Eric Abrahamsen writes:
> It's a little strange, because the manual section for this specifically
> mentions the inheritance of the LOCATION property, but the code doesn't
> do it. Shall I add it in? It makes sense for LOCATION and TIMEZONE to be
> inheritable, but not
> On 20-Aug-2017, at 12:57 AM, Nicolas Goaziou wrote:
>
> Hello,
>
> Vikas Rawal writes:
>
>> My org-version (latest on org ELPA) is: Org mode version 9.0.9
>> (9.0.9-82-gb862c2-elpa @ /Users/vikas/.emacs.d/elpa/org-20170814/)
>>
>>
Nicolas Goaziou writes:
> Eric Abrahamsen writes:
>
>>> BTW, as long as Org doesn't support time zones, the "ox-icalendar"
>>> property may be prefixed with "ICALENDAR_" (e.g., ICALENDAR_TZ).
>>
>> Done!
>
> I realize this is not a great idea
On Sat, Aug 19, 2017 at 6:19 AM Nicolas Goaziou
wrote:
> Fixed. Thank you.
>
Thanks! I confirm the fix.
--
Kaushal Modi
Hello,
Vikas Rawal writes:
> My org-version (latest on org ELPA) is: Org mode version 9.0.9
> (9.0.9-82-gb862c2-elpa @ /Users/vikas/.emacs.d/elpa/org-20170814/)
>
> The following is not working:
>
> #+PROPERTY: header-args :eval inline-only
>
> ":eval
Eric Abrahamsen writes:
>> BTW, as long as Org doesn't support time zones, the "ox-icalendar"
>> property may be prefixed with "ICALENDAR_" (e.g., ICALENDAR_TZ).
>
> Done!
I realize this is not a great idea since other properties do not have
"ICALENDAR_" prefix. Sorry
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> Out of curiosity, what's your stance on supporting time zones in Org's
>> timestamps? It would be an enormous amount of work, obviously, but in
>> principle?
>
> In principle I
On Sat, Aug 19, 2017 at 7:06 AM Vikas Rawal
wrote:
> Is it by choice that org-table.el is part of both org and org-plus-contrib?
org-plus-contrib = org + the stuff in contrib/ dir
So yes, *everything* in org is in org-plus-contrib too.
> Does it have to be
Completing myself,
Nicolas Goaziou writes:
> `org-table-toggle-column-width' is now bound to "C-c TAB". I removed
> "noshrink" STARTUP keyword, which wasn't useful. I also introduced an
> honest test coverage.
>
> Still no documentation, though.
I made some final
My org-version (latest on org ELPA) is: Org mode version 9.0.9
(9.0.9-82-gb862c2-elpa @ /Users/vikas/.emacs.d/elpa/org-20170814/)
The following is not working:
#+PROPERTY: header-args :eval inline-only
":eval never-export” works; but ":eval inline-only" does not.
I can deal with this by
James Harkins writes:
> On Sat, 19 Aug 2017 04:36:58 -0400 Nicolas Goaziou
> wrote
>> Adding a special style to every paragraph contained in a plain list is
>> very easy to do. Just let me know if it happens to be the way to solve
>>
Is it by choice that org-table.el is part of both org and org-plus-contrib?
Does it have to be explicitly loaded?
Vikas
On Sat, 19 Aug 2017 04:36:58 -0400 Nicolas Goaziou
wrote
> Adding a special style to every paragraph contained in a plain list is
> very easy to do. Just let me know if it happens to be the way to solve
> the issue at hand.
I think that is the correct
Hello,
William Denton writes:
> I noticed this last week, but I'm on vacation. I'm compiling and running Org
> and Emacs from source, and have been keeping up to date, but the problem's
> been
> there for a while. For Org, I'm on the master branch, not tables, and
>
Hello,
Paul Stansell writes:
> I think there might be a something wrong when explicitly setting a width
> of a table column.
>
> For example, for this table
>
> |---+--|
> | | <6> |
> | 1 | one
Dear Jarmo,
> Jarmo Hurri writes:
> Hi Colin.
> Colin Baxter writes:
>> Works for me using 'make clean' followed by 'make all'.
> For some reason I still get the same error even with that sequence
> of commands.
> Make
Hello,
Sam Halliday writes:
> Regression in org-plus-contrib from http://orgmode.org/elpa/ vs version
> distributed with Emacs 25.2.1
>
> Running
>
> M-x md-org-export-to-markdown
>
> on a simple org file such as the following
>
>
Regression in org-plus-contrib from http://orgmode.org/elpa/ vs version
distributed with Emacs 25.2.1
Running
M-x md-org-export-to-markdown
on a simple org file such as the following
==
#+TITLE: Functional Programming in Scala for Mortals
Hello,
Fabrice Popineau writes:
> You could also prefix the link by a string holding (in ascii) the number of
> bytes of the unencoded link.
>
> But that makes raw/manual editing of an org file much harder.
I'd rather have something simple.
Here are some
Hello,
Peter Tomhas writes:
> Perhaps that could become something like (apologies for poorly
> formatted texinfo):
>
> %\1 @dots{} %\N @r{Insert the text entered at the Nth
> %^@{@var{prompt}@}, where @code{N} is}
> @r{a number, starting from 1.@footnote{As
Hello,
ed...@openmail.cc writes:
> I would like to ask if it is possible to preview latex blocks. Something
> like this (replace EXPORT with SRC, if you wish):
>
> #+BEGIN_EXPORT latex
> \begin{align}
>I_{0}
>& > \max{(\lambda_{f}^{2})}
>\\
Hello,
Adam Spiers writes:
> I was also expecting to be able to use #+NAME: foo in front of a
> headline
You cannot use a NAME keyword to a headline (or an inlinetask).
CUSTOM_ID is morally equivalent, though.
> or even other elements like paragraphs, but this doesn't
Hello,
James Harkins writes:
> So I would say, postpone this issue unless I can gather more evidence.
OK.
> A short answer to your questions is that every list item does consist
> of paragraphs, and each paragraph must have a paragraph style, but --
> the paragraph style
Hello,
Eric Abrahamsen writes:
> Out of curiosity, what's your stance on supporting time zones in Org's
> timestamps? It would be an enormous amount of work, obviously, but in
> principle?
In principle I agree this would be a very good thing, if possible at
all.
>
Colin Baxter writes:
> >
> > jarmo@localhost org-mode]$ diff local.mk local.mk~ 31c31 <
> > ORG_ADD_CONTRIB = htmlize ---
> >> #ORG_ADD_CONTRIB = ox-* # e.g. the contributed exporter
>
Dear Jarmo,
> Jarmo Hurri writes:
> Greetings.
> Just pulled the latest version and tried to compile it. I get the
> following error:
> --
> [jarmo@localhost org-mode]$ make compile
Hi Colin.
Colin Baxter writes:
> Works for me using 'make clean' followed by 'make all'.
For some reason I still get the same error even with that sequence of
commands.
Make reports that the error is coming from addcontrib. Isn't there some
file that controls local contrib
40 matches
Mail list logo