>>> "Rasmus" == Rasmus writes:
> #+ATTR_LATEX: :mode math :environment pmatrix :math-suffix \times
> :math-prefix \mathbf{y}=
> | a | b |
> | c | d |
> #+ATTR_LATEX: :mode math :environment pmatrix
> | 1 | 2 |
> | 3 | 4 |
This does not work fo
Hello,
Jay Iyer writes:
> Hi, since this morning I have been running into
> a (wrong-number-of-arguments (0 . 1) 2) error while re-filing. This is new
> behavior, the Mac setup is unchanged, and I am unable to find a solution so
> I am hoping you can point me in the right direction to fix this.
Hello,
Tim Cross writes:
> There appers to be a compatibility issue between latest org-mode and
> goto-addr.el in emacs 25.1. Specifically, the 'goto-address-prog-mode
> funciton. When this function is added to prog-mode-hook, opening an org
> file with src blocks results in an org-mode fontific
Eric Abrahamsen writes:
> This is on the roadmap for EBDB[1]. i
It’s already starred here. ;)
> It already supports multiple databases, and can export to vcard. I'm
> working on vcard import now, and when that's done it will be a native
> Vcard database.
Wonderful…thanks a lot for your work on
thanks Nicolas - will go back and dig further. Not sure where to look next
though.
Tim
On 26 February 2017 at 20:19, Nicolas Goaziou
wrote:
> Hello,
>
> Tim Cross writes:
>
> > There appers to be a compatibility issue between latest org-mode and
> > goto-addr.el in emacs 25.1. Specifically, t
Hi Jorge, Bastien, org-mode developers,
* Jorge Morais Neto [10. Feb. 2017]:
> On 10 February 2017 at 11:53, Bastien wrote:
>> Org 9.0.5, a minor bugfix release, is out.
> In Org 9.0.5, clock out notes are again stored below the corresponding
> clock line, restoring the behavior of an earlier rel
Hello,
Gregor Zattler writes:
> Is there a consensus now where the clocking out notes should go,
> even in future versions? I am affected from this too and before
> I start changing the position of all the clocking out notes I
> would like to know where to move them.
I think the current locati
Hi,
I'm using org-publish-external-link to look up a the link target for a
headline. The following code works, although I'd expect it to fail:
(org-publish-resolve-external-link
(concat "* " (org-element-property :raw-value headline))
source-file)
``headline'' is a headline as returned by org
Hello,
Mark Meyer writes:
> I'm using org-publish-external-link to look up a the link target for a
> headline. The following code works, although I'd expect it to fail:
>
> (org-publish-resolve-external-link
> (concat "* " (org-element-property :raw-value headline))
> source-file)
>
> ``head
Hello,
Alex Bennée writes:
> Ken Mankoff writes:
>
>> An RSS feed I follow mentioned ob-async here:
>> https://github.com/astahlman/ob-async
>>
>> I haven't seen it mentioned on the list yet. Perhaps others would be
>> interested in asynchronous Babel processing. I've seen the feature
>> reques
On 02/26/17 16:27, Nicolas Goaziou wrote:
> The first argument for `org-publish-external-link' is a so-called
> "fuzzy" search string. In such a string "*whatever" is meant to match
> a headline named "whatever", whatever its level is. IOW, the "*"
> character denotes a headline, not a level.
Can
> Can you point me to a way to match a path in the tree?
There isn't. Internal links do not point to paths in the tree. You can,
however, point to a specific headline using its unique name, if
possible, or a custom ID otherwise.
Regards,
On 02/26/17 17:39, Nicolas Goaziou wrote:
> There isn't. Internal links do not point to paths in the tree. You can,
> however, point to a specific headline using its unique name, if
> possible, or a custom ID otherwise.
What do you mean by unique name? Is this a property that is available
via org-
Mark Meyer writes:
> What do you mean by unique name? Is this a property that is available
> via org-element or do I have to set this in the source document?
According to its docstring, `org-publish-resolve-external-link' is used
to resolve the following links:
[[file.org::*heading][descripti
Saša Janiška writes:
> Eric Abrahamsen writes:
>
>> This is on the roadmap for EBDB[1]. i
>
> It’s already starred here. ;)
>
>> It already supports multiple databases, and can export to vcard. I'm
>> working on vcard import now, and when that's done it will be a native
>> Vcard database.
>
> Wo
On 02/26/17 18:28, Nicolas Goaziou wrote:
> I don't know the EPUB exporter. You probably could modify the Org source
> itself instead of the output.
I wrote it yesterday, the code's up at
https://github.com/ofosos/org-epub
it's a little crufty, because I did write it for org 8 initially.
Hmm,
Mark Meyer writes:
> On 02/26/17 18:28, Nicolas Goaziou wrote:
> I wrote it yesterday, the code's up at
>
> https://github.com/ofosos/org-epub
Great.
> it's a little crufty, because I did write it for org 8 initially.
>
> Hmm, I have to think about it. I would like to either have a 1:1 mapping
On 02/26/17 19:12, Nicolas Goaziou wrote:
> It is also easy in Org 9 : (org-export-get-reference headline info). See
> its use in the function above.
I am under the impression that I don't have access to the `INFO' plist
that is required by `org-export-get-reference' - at least not from the
`:comp
Mark Meyer writes:
> On 02/26/17 19:12, Nicolas Goaziou wrote:
>> It is also easy in Org 9 : (org-export-get-reference headline info). See
>> its use in the function above.
>
> I am under the impression that I don't have access to the `INFO' plist
> that is required by `org-export-get-reference'
On 02/26/17 19:28, Nicolas Goaziou wrote:
> Since you're writing the back-end, you don't need to
> use :completion-function, do you?
>
> Just write the TOC the way you like.
Yay! You're completely right. The use case is, folding multiple
documents into a single EPUB (via a project), but I can eas
Thanks.
It looks like the following options are useful.
1. Use a deadline
2. Use an active timestamp in the heading. The first one found seems to
be the one assigned to the heading as far as the agenda goes.
So, both of these will show up in an agenda:
* test meeting <2017-02-26 Sun>
* test m
Thanks a lot. There was some leftover code in my .init file that caused
this weirdness and all is functional now.
I appreciate your prompt response.
-jay
On Sun, Feb 26, 2017 at 1:07 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Jay Iyer writes:
>
> > Hi, since this morning I have been running into
Mark Meyer writes:
> On 02/26/17 18:28, Nicolas Goaziou wrote:
>> I don't know the EPUB exporter. You probably could modify the Org source
>> itself instead of the output.
>
> I wrote it yesterday, the code's up at
>
> https://github.com/ofosos/org-epub
>
> it's a little crufty, because I did wr
Hello all,
Kyle Meyer writes:
> Kyle Meyer writes:
>
> [...]
>
>>> Also, it seems "capitalize" is the wrong verb here?
>>
>> Something with "upcase" or "uppercase" would have been better given the
>> behavior of upcase and capitalize.
>
> Here's a patch. I'll apply it to master in a day or two
On 02/26/17 20:32, Eric Abrahamsen wrote:
> I put together just the very beginnings of the package, I think it's
> capable of unzipping and re-zipping an Epub file, and generating a new
> (empty) template directory structure. Take a look and see if anything in
> there is interesting to you -- I thi
Mark Meyer writes:
> On 02/26/17 20:32, Eric Abrahamsen wrote:
>> I put together just the very beginnings of the package, I think it's
>> capable of unzipping and re-zipping an Epub file, and generating a new
>> (empty) template directory structure. Take a look and see if anything in
>> there is
On 02/26/17 19:28, Nicolas Goaziou wrote:
> Since you're writing the back-end, you don't need to
> use :completion-function, do you?
>
> Just write the TOC the way you like.
I defined `*org-epub-current-file*' as a special variable and set it in
the publish function. Then I extracted the headline
I need some help with this one as I'm running out of ideas.
What I have done -
1. Completely removed all other org installs to eliminate possible 'mixed
version' issues. This includes the org bundled with emacs 25.1. Made no
difference.
2. Try opeing an org file which does not have any source bl
The following example:
* Example
#+begin_example
hello world
#+end_example
#+begin_example
* hello world
#+end_example
exports an HTML file where the second "hello word" is interpreted as a
header, ignoring that it is within begin_example. See below
I am using org-mode version 9.0.3, under em
Hello,
dmg writes:
> The following example:
>
>
> * Example
>
> #+begin_example
> hello world
> #+end_example
>
> #+begin_example
> * hello world
> #+end_example
>
> exports an HTML file where the second "hello word" is interpreted as a
> header, ignoring that it is within begin_example. See bel
30 matches
Mail list logo
