Hello,
Achim Gratz strom...@nexgo.de writes:
the change in org-macro.el to use a literal replacement string is still
missing in mainline Org. Is there something wrong with that patch or
should I apply it?
IIRC I had told you that you could apply it. If that's not the case, you
can apply it
Nicolas Goaziou writes:
IIRC I had told you that you could apply it. If that's not the case,
you can apply it anyway ;)
Done in maint and master.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Wavetables for the Waldorf Blofeld:
Hi Nicolas,
the change in org-macro.el to use a literal replacement string is still
missing in mainline Org. Is there something wrong with that patch or
should I apply it?
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptations for KORG EX-800 and
Am 22.03.2013 19:17, schrieb Nicolas Goaziou:
You might want to use the (function (lambda ...)) form.
Why? (function (lambda ...)) is equivalent to (lambda ...). In fact,
`lambda' uses `function' as a subroutine.
Hello,
Achim Gratz strom...@nexgo.de writes:
Am 22.03.2013 19:17, schrieb Nicolas Goaziou:
You might want to use the (function (lambda ...)) form.
Why? (function (lambda ...)) is equivalent to (lambda ...). In fact,
`lambda' uses `function' as a subroutine.
Am 21.03.2013 22:02, schrieb Nicolas Goaziou:
I suggest the following code instead, which allows to escape the
escaping backslash so the comma is not escaped:
(args (mapcar 'org-trim
(split-string
(replace-regexp-in-string
Hello,
Achim Gratz strom...@nexgo.de writes:
Am 21.03.2013 22:02, schrieb Nicolas Goaziou:
I suggest the following code instead, which allows to escape the
escaping backslash so the comma is not escaped:
(args (mapcar 'org-trim
(split-string
Am 22.03.2013 15:22, schrieb Nicolas Goaziou:
Actually the code I pasted is wrong, I meant:
(split-string
(replace-regexp-in-string
\\(+\\)?\\(,\\)
(lambda (str)
(let ((len (length (match-string 1 str
(if (evenp len) (concat (make-string (/ len 2) ?\\)
Achim Gratz strom...@nexgo.de writes:
Am 22.03.2013 15:22, schrieb Nicolas Goaziou:
Actually the code I pasted is wrong, I meant:
(split-string
(replace-regexp-in-string
\\(+\\)?\\(,\\)
(lambda (str)
(let ((len (length (match-string 1 str
(if
Hello,
Achim Gratz strom...@nexgo.de writes:
Hi Tom,
I have a patch that should fix your problems with some characters in
macro expansions:
From 27b22d17f629a50bd485a0320dac45616d7ceb7f Mon Sep 17 00:00:00 2001
From: Achim Gratz strom...@stromeko.de
Date: Sun, 17 Mar 2013 10:20:10 +0100
Carsten Dominik writes:
I tried the file on github, and export to texinfo fails with the
attached backtrace (exports to other backends as well).
Works for me.
I love this idea, so I really want to try. Any ideas what might be
wrong on my side?
[…]
org-export-to-file(texinfo ./om.texi nil
Hi Carsten,
Carsten Dominik wrote:
On 17.3.2013, at 02:19, Thomas S. Dye t...@tsdye.com wrote:
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Hi Tom,
I'm playing around with the current version, here is what I have so far:
The arguments to #+attr_texinfo need to lose the double
Hi Tom,
I have a patch that should fix your problems with some characters in
macro expansions:
From 27b22d17f629a50bd485a0320dac45616d7ceb7f Mon Sep 17 00:00:00 2001
From: Achim Gratz strom...@stromeko.de
Date: Sun, 17 Mar 2013 10:20:10 +0100
Subject: [PATCH] fix macro expansion with separators
On 17.3.2013, at 07:54, Achim Gratz strom...@nexgo.de wrote:
Carsten Dominik writes:
I tried the file on github, and export to texinfo fails with the
attached backtrace (exports to other backends as well).
Works for me.
I love this idea, so I really want to try. Any ideas what might be
On 17.3.2013, at 08:01, Sebastien Vauban wxhgmqzgw...@spammotel.com wrote:
Hi Carsten,
Carsten Dominik wrote:
On 17.3.2013, at 02:19, Thomas S. Dye t...@tsdye.com wrote:
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Hi Tom,
I'm playing around with the current version, here is
Carsten Dominik writes:
It seems you are not using the build system?
Hi Achim, not sure what exactly you mean. I do compile using make
which I think is what you mean?
It seems you're not producing orgmanual.texi with make, since I can't
see how it would use om.texi as the target filename.
On 17.3.2013, at 14:34, Achim Gratz strom...@nexgo.de wrote:
Carsten Dominik writes:
It seems you are not using the build system?
Hi Achim, not sure what exactly you mean. I do compile using make
which I think is what you mean?
It seems you're not producing orgmanual.texi with make,
Carsten Dominik writes:
So these are not yet in his github repository?
Yes they are, but not in the master branch. You'll want to switch to
the orgmanual branch for now.
I am a bit confused, so I give up for now, maybe you or Tom can send
around some instructions once there is a version
Hi Achim,
thank you for the additional information.
On 17.3.2013, at 18:36, Achim Gratz strom...@nexgo.de wrote:
Carsten Dominik writes:
So these are not yet in his github repository?
Yes they are, but not in the master branch. You'll want to switch to
the orgmanual branch for now.
I
Hi Tom,
I'm playing around with the current version, here is what I have so far:
The arguments to #+attr_texinfo need to lose the double quotes
Index entries in description lists must be separated from their entry by
at least one blank line like in the example below, otherwise the second
such
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Hi Tom,
I'm playing around with the current version, here is what I have so far:
The arguments to #+attr_texinfo need to lose the double quotes
Index entries in description lists must be separated from their entry by
at least one blank
On 17.3.2013, at 02:19, Thomas S. Dye t...@tsdye.com wrote:
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Hi Tom,
I'm playing around with the current version, here is what I have so far:
The arguments to #+attr_texinfo need to lose the double quotes
Index entries in
Thomas S. Dye writes:
I do have a problem here. I think I have mis-configured BTEST_POST.
I have this:
BTEST_POST =
# -L path-to/ert # needed for Emacs23, Emacs24 has ert
built in
# -L path-to/ess # needed for running R tests
-L
Aloha Achim,
Achim Gratz strom...@nexgo.de writes:
Thomas S. Dye writes:
I do have a problem here. I think I have mis-configured BTEST_POST.
I have this:
BTEST_POST =
# -L path-to/ert # needed for Emacs23, Emacs24 has
ert built in
# -L path-to/ess #
Thomas S. Dye writes:
That works nicely. I found the error and orgmanual.pdf is now produced
without errors.
Progress! :-)
With the current version from git I cannot export to texinfo
successfully, though, I get this error near the end of the export:
Debugger entered--Lisp error:
Hello Achim,
On 10 March 2013 08:24, Achim Gratz strom...@nexgo.de wrote:
Thomas S. Dye writes:
That works nicely. I found the error and orgmanual.pdf is now produced
without errors.
Progress! :-)
With the current version from git I cannot export to texinfo
successfully, though, I get
Jonathan Leech-Pepin writes:
The error is actually on line 6069 of the manual. The {{{vindex
[...]}}} line and subsequent paragraph. As far as the list is
concerned there is no associated content for that list
entry. Indenting them appropriately to be recognized as part of the
list allows for
On 10 March 2013 15:25, Achim Gratz strom...@nexgo.de wrote:
Jonathan Leech-Pepin writes:
The error is actually on line 6069 of the manual. The {{{vindex
[...]}}} line and subsequent paragraph. As far as the list is
concerned there is no associated content for that list
entry. Indenting
Hello,
Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes:
The error is not actually within ox-texinfo in this case however I suspect.
The exact same code (at the location of the error in ox-texinfo) appears
within
ox-latex and ox-ascii.
`(org-trim contents)', which removes
Hello,
On 10 March 2013 16:23, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes:
The error is not actually within ox-texinfo in this case however I
suspect.
The exact same code (at the location of the error in ox-texinfo)
Achim Gratz strom...@nexgo.de writes:
Thomas S. Dye writes:
That works nicely. I found the error and orgmanual.pdf is now produced
without errors.
Progress! :-)
With the current version from git I cannot export to texinfo
This is fixed now.
I've extended the Makefile to approximate
Achim Gratz strom...@nexgo.de writes:
Thomas S. Dye writes:
The orgmanual now creates a pdf file, too, but one lacking the indexes
and with links that look like they need another run through TeX.
In that case, texi2dvi and hence make should have signaled an error
(I've just pulled from your
Aloha Yagnesh Raghava Yakkala,
Yagnesh Raghava Yakkala h...@yagnesh.org writes:
Hello Thomas,
These instructions assume more knowledge than I have. Could you be more
specific about in the Org worktree? Should I create a branch where I
do this? Or, should I put this in one of the upstream
Thomas S. Dye writes:
The orgmanual now creates a pdf file, too, but one lacking the indexes
and with links that look like they need another run through TeX.
In that case, texi2dvi and hence make should have signaled an error
(I've just pulled from your repo and it does).
When I'm done
Achim Gratz strom...@nexgo.de writes:
Thomas S. Dye writes:
The orgmanual now creates a pdf file, too, but one lacking the indexes
and with links that look like they need another run through TeX.
In that case, texi2dvi and hence make should have signaled an error
(I've just pulled from your
Yagnesh Raghava Yakkala writes:
IIUC, Achim means,
Thanks for spelling that out for me. :-)
Given texi generation is very slow, I wonder which format of manual
will be included in Emacs trunk.?
Well, there obviously needs to be improvement on that front. I've
profiled the export already,
Hi Achim,
thanks for doing the profiling.
Achim Gratz strom...@nexgo.de writes:
org-macro-replace-all2222.371024111.185512
This one looks suspicious: if the function does what it says,
why does it run twice? If we can spare 111 secs here, that's
already an improvement. I'll have
Hello,
Bastien b...@altern.org writes:
Hi Achim,
thanks for doing the profiling.
Achim Gratz strom...@nexgo.de writes:
org-macro-replace-all2222.371024111.185512
This one looks suspicious: if the function does what it says,
why does it run twice? If we can spare 111 secs
Bastien writes:
org-macro-replace-all2222.371024111.185512
This one looks suspicious: if the function does what it says,
why does it run twice? If we can spare 111 secs here, that's
already an improvement. I'll have a look at some point but
feel free to beat me on this!
That
Achim Gratz strom...@nexgo.de writes:
Bastien writes:
org-macro-replace-all2222.371024111.185512
This one looks suspicious: if the function does what it says,
why does it run twice? If we can spare 111 secs here, that's
already an improvement. I'll have a look at some point
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Thomas S. Dye writes:
[…]
I look forward to picking this project up again in a week or so, or
learning from my Org colleagues that the project ought to be scuttled.
Hi Tom,
this looks good.
Thanks for reviewing a work in progress. I'm
Hello Thomas,
These instructions assume more knowledge than I have. Could you be more
specific about in the Org worktree? Should I create a branch where I
do this? Or, should I put this in one of the upstream branches and
arrange to push it into the Org repo? In any case, can you suggest a
Thomas S. Dye writes:
[…]
I look forward to picking this project up again in a week or so, or
learning from my Org colleagues that the project ought to be scuttled.
Hi Tom,
this looks good.
I've implemented a rough draft of a Makefile that integrates with the
build system (a clean target is
Aloha all,
An experiment to see if it is possible to convert the Org manual to Org
is now (hopefully) at the proof of concept stage and I would like to
determine whether or not the approach is viable. The experiment is here:
https://github.com/tsdye/orgmanual.git
The file orgmanual.org has a
Hi Tom,
wow, a daring project. This would indeed be a testimony to the quality of the
exporter if this works and gives proper output! I am curious and looking
forward to seeing the results.
- Carsten
On 25.2.2013, at 21:21, Thomas S. Dye t...@tsdye.com wrote:
Aloha all,
An experiment
45 matches
Mail list logo
