-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Fred Gruber writes:
> Hi
> Is there a way to get org-babel-lilypond to generate midi of music fragments
> in basic mode. Ideally when we export the html the
> images of the music fragments should have a link to the corresponding midi of
> that
On Monday, 23 Apr 2018 at 23:26, Nicolas Goaziou wrote:
> Hello,
>
> Eric S Fraga writes:
>
>> I've gone through the code but cannot determine where this is done and
>> why the ODT export target is treated differently to the LaTeX one.
>
> Both are treated similarly, really. The difference comes f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nicolas Goaziou writes:
> stardiviner writes:
>
>> Hi, Nicolas, thank you always review my Org-mode patches. Yesterday, I
>> ask Bastein about Worg ox-org question. He mentioned I should at least
>> say "Hi" in message. I'm not good at English cu
stardiviner writes:
> Hi, Nicolas, thank you always review my Org-mode patches. Yesterday, I
> ask Bastein about Worg ox-org question. He mentioned I should at least
> say "Hi" in message. I'm not good at English culture of something else.
> But I just want to say, I'm glad you reviewed my patche
Nicolas Goaziou writes:
> Hello,
>
> Carsten Dominik writes:
>
>> I would be interested to discuss a better solution. It would be nice is
>> list items could be TODO's, but I though long and har about this back when,
>> and over allo those years, I could not think of anything that could be
>> i
Hello,
Eric S Fraga writes:
> I've gone through the code but cannot determine where this is done and
> why the ODT export target is treated differently to the LaTeX one.
Both are treated similarly, really. The difference comes from the fact
that LaTeX has no markup for paragraph. Therefore,
Hello,
Carsten Dominik writes:
> I would be interested to discuss a better solution. It would be nice is
> list items could be TODO's, but I though long and har about this back when,
> and over allo those years, I could not think of anything that could be
> implemented with reasonable effort.
Hello Nicolas,
I think I've corrected all points. You'll find new versions attached.
Would you mind consider to include the patch for the detection of
encoding with the #+include keyword in 9.2 release ?
>From e4d6cf8f9959781c682738a4b9e5ea8ae5747b6b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pierr
I don't have any objections to merging now, or in the future. org-ref
addresses a fairly specific need, which is simple citations that ultimately
end up being processed by bib(la)tex/latex. It does a mediocre job
supporting footnote style citations, and limitations of the link format it
uses make i
Ah, yes, you are right, thanks. Have used class before,
but start out with style usually when experimenting.
Thanks,
Andreas
Richard Lawrence writes:
> Hi Andreas,
>
> Andreas Reuleaux writes:
>
>> Leaving out the double quotes may be comfortable, but I am not sure
>> if this was a good id
On Mon, Apr 23, 2018 at 2:11 PM Nicolas Goaziou
wrote:
>
> A warning is not an error. I wouldn't bother.
>
Well, it was bothering me as I have a hook at auto-compiles the .el file
each time I save it. Also bothers my OCD :)
> Anyway, you might want to look at `with-no-warnings'.
>
That's good
Hi Andreas,
Andreas Reuleaux writes:
Leaving out the double quotes may be comfortable, but I am not
sure if this was a good idea: makes it difficult to see which
parts belong to the style, and where the alt attribute starts:
#+attr_html: :style float: right; border: 1px solid brown; :alt
Hello,
Kaushal Modi writes:
> I am trying to update the ox-hugo package to work with zero warnings for
> both Org 9.1 and 9.2.
A warning is not an error. I wouldn't bother.
Anyway, you might want to look at `with-no-warnings'.
Regards,
--
Nicolas Goaziou
Hi,
With headlines like
* [[http://example.com]] Example
org-collector writes just "http://example.com"; in the table, omitting the rest
of the headline.
Patch below.
BR,
Martin
>From 1228efc453d38bc090511f21fafa750e416e8b7a Mon Sep 17 00:00:00 2001
From: Martin Kampas
Date: Mon, 23 Apr 201
On Mon, Apr 23, 2018 at 12:02 PM Kaushal Modi
wrote:
> But ox-hugo still compiles with this warning with Org 9.2:
>
> In org-hugo--get-tags:
> ox-hugo.el:1371:6:Warning: ‘org-get-tags-at’ is an obsolete function (as of
> Org 9.2); use ‘org-get-tags’ instead.
>
> What's the canonical way to de
adding to my own mail:
I have progressed since: I can add style attributes if I start them with
a colon (:style) and then don't use quotes (not: :style "float: right;" )
this sample.org thus works for me:
-
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do
eiusmod tempor incidi
Hello all,
when I export a drawer to LaTeX, the output from
org-latex-format-drawer-function, which I can re-define, is inserted
directly into the LaTeX document. In particular, it is not considered a
different paragraph by default.
When I export to odt, the content text passed to the
org-odt-fo
Hello,
I am trying to update the ox-hugo package to work with zero warnings for
both Org 9.1 and 9.2.
I tried adding this function:
(defsubst org-hugo--get-tags ()
"Wrapper function to pick the correct fn for getting inherited Org tags."
;; Starting Org 9.2, `org-get-tags' returns all the in
On Mon, Apr 23, 2018 at 4:21 PM, Eric S Fraga wrote:
> On Monday, 23 Apr 2018 at 15:50, alain.coch...@unistra.fr wrote:
> > In fact, my use of inelintaks seems to me so basic (I faced the
> > problem since my day 1 with org-mode) that maybe another solution that
> > I overlooked would work for me
On Monday, 23 Apr 2018 at 15:50, alain.coch...@unistra.fr wrote:
> In fact, my use of inelintaks seems to me so basic (I faced the
> problem since my day 1 with org-mode) that maybe another solution that
> I overlooked would work for me. I'll explain my problem in the hope
> that someone might be
> Fixed. Thank you.
Thanks!
Alex
Nicolas Goaziou writes on Mon 16 Apr 2018 14:08:
> Inlinetasks has a lot of glitches [...]. It is not ready for prime
> time. Worse, I don't think its design is good, either.
I would be glad to be able to use an alternative. I see that
"drawers" are mentioned by some of you experts, but it i
Hello,
Alex Branham writes:
> On Fri 20 Apr 2018 at 04:27, Nicolas Goaziou wrote:
>
>>> #+BEGIN_EXAMPLE
>>> #+TAGS: office(c) car(C)
>>> * one
>>> #+END_EXAMPLE
>>
>> FWIW, I couldn't reproduce it on master.
>
> It seems to be a problem with org-tag-persistent-alist. I can't
> reproduce it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> From 596da7b0384d64f3c1c22a49bc9bced8d0d8abf8 Mon Sep 17 00:00:00 2001
>> From: stardiviner
>> Date: Sun, 22 Apr 2018 09:37:40 +0800
>> Subject: [PATCH] ob-eshell.el: Add Eshell suppo
Hello,
stardiviner writes:
> @Nicolas, does current existing testing should be updated to #+begin_src
> shell? Even though they all test passed currently.
I don't think so. "begin_src sh" and "begin_src shell" are not
equivalent, e.g., sometimes, "begin_src shell" could be "begin_src
bash". IOW
Hello,
pierre.techouey...@free.fr (Pierre Téchoueyres) writes:
> I did my homework : found a fix for a) and rebased previous patch on
> master.
Thank you. Some comments follow.
> * lisp/ox.el (org-export-expand-include-keyword): Add new keyword
> `:coding' for specify the file encoding whith
Brad Knotwell writes:
> Thanks for the code review. With one exception--:prefix-builtins is an
> option not an argument--
I don't understand.
Org Lint uses `org-babel-header-args:XXX' value to check if a value for
a given parameters is allowed. So, what's wrong with replacing
(:prefix-builti
Hello,
stardiviner writes:
> From 596da7b0384d64f3c1c22a49bc9bced8d0d8abf8 Mon Sep 17 00:00:00 2001
> From: stardiviner
> Date: Sun, 22 Apr 2018 09:37:40 +0800
> Subject: [PATCH] ob-eshell.el: Add Eshell support for Babel.
Thank you. This could go into master branch once Org 9.2 is out.
> |
Hello,
roberthambr...@gmail.com writes:
> These four patches are independent and can thus be applied individually.
>
> Please let me know if you have any questions.
Thank you.
What's your status wrt FSF papers? If you haven't signed them, you need
to add TINYCHANGE at the end of the commit mess
Hello,
roberthambr...@gmail.com writes:
> * lisp/ob-clojure.el (org-babel-tangle-langs-exts): Add ClojureScript
> to the supported language extensions.
Thank you. Some comments follow.
> (defvar org-babel-tangle-lang-exts)
> (add-to-list 'org-babel-tangle-lang-exts '("clojure" . "clj"))
> +(a
Hello,
roberthambr...@gmail.com writes:
> * lisp/ob-clojure.el (org-babel-edit-prep:clojure): New function that
> sets the buffer's namespace to the value of :ns, if provided.
> (org-babel-edit-prep:clojurescript): Alias for
> org-babel-edit-prep:clojure.
Thank you.
> +(defun org-babel-edit-pre
Hello,
roberthambr...@gmail.com writes:
> * lisp/ob-clojure.el (org-babel-execute:clojure): Implemented :target,
> which allows selection of connection.
> * lisp/ob-clojure.el (org-babel-execute:clojurescript): New
> ClojureScript interface that uses :target flag to specify `cljs`
> evaluation ta
Hello,
roberthambr...@gmail.com writes:
> * lisp/org-src.el (org-src-font-lock-fontify-block): Fixed temporary
> buffer name. Clojure's Cider could not dynamically fontify Clojure
> subsections of the buffer. Removing the rogue space from the temporary
> buffername fixes this.
This is not a rogu
Hi,
Nicolas Goaziou writes:
>> BTW, I write some documents on Worg about ob-clojure :ns usage,
>> ob-clojure-literate.el and ob-js :session usage etc. But I can't push to
>> remote. Here is my steps.
>
> I'm Cc'ing Bastien about it.
Yes, this has been sorted out, thanks.
--
Bastien
I'm writing a document that currently has over 500 footnotes, which is
then exported to latex and subsequently built into a PDF file. But every
time that I write a new footnote, all the other footnotes show as
visible, whereas previously they were hidden under their second-level
title.
How can I
35 matches
Mail list logo
