>From 1ed4564cd14369758167758bb8a2eb5c4d0d8f0e Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Thu, 9 May 2013 19:28:37 +0200
Subject: [PATCH] org.el: do not indent option keyword lines
* lisp/org.el (org-indent-line): Keep option keyword lines at column
zero so they don't lo
ific side first.
With these caveats, here's the patchset:
>From fe5f9f46896939179f0163c2ce10f8738ebde709 Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Thu, 9 May 2013 19:47:59 +0200
Subject: [PATCH 1/2] org.el: improve org-property-re and use it throughout
* lisp/org.el (org-proper
Nicolas Goaziou writes:
> Actually this is a bit different. Parsing doesn't backtrack. Look at
> `org-element-parse-buffer' through elp to see that elements are parsed
> only once.
Sorry for the loose terminology.
> The problem comes from `org-element-at-point'. To be effective, it needs
> to mov
Seth Mason writes:
> According to http://orgmode.org/elpa.html the org-plus-contrib package
> has all the files in the /contrib directory but it looks like it's
> only grabbing the files that begin with "org-". None of the "ox-" or
> "ob-" are in the repo. Looks like this line in servers.mk is the
Eric Schulte writes:
> If you really wanted to be fancy, gnuplot will let you specify shell
> transformations as part of the plotting command which would allow you to
> forego the intermediate code block.
As a side-note, if we'd drop the convention that the first separator
defines the heading of t
Lawrence Mitchell writes:
> org-element--current-element takes (on my machine) 0.0003 seconds per
> call. However, when exporting 128x the orgmanual introduction, it's
> called around 25 times giving ~ 80 seconds total time (out of ~200
> total).
I've traced this a bit and the question does w
Andreas Röhler easy-emacs.de> writes:
> What is the best way to put this into an
>
> #+BEGIN_SRC python
>
> foo = {
> "bar": (
> "baz",
> "qux",
> ),
> }
>
> #+END_SRC
< s TAB python C-c ' C-x i src.python C-c '
Regards,
Achim.
Achim Gratz writes:
> Achim Gratz writes:
>> Something in cc-langs that doe not work correctly in batch mode, it
>> fails to define or select the correct fontification function for gawk.
>> In any case, it doesn't happen when you don't export in batch mode and
Eric Schulte writes:
>> #+PROPERTY: header-args:R :session "*R*" :exports none
>
> I hate to change syntax, but the syntax you mention above does look both
> appealing and natural. Even with working file local variables [1].
OK, so let's settle for this.
>> I've checked that the property interfa
Lawrence Mitchell writes:
> I did a bit of digging and here are the results. No potential
> fixes though.
Thanks for beating me to it, that frees up quite some processor cycles
on my end! :-)
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI
Achim Gratz writes:
> Something in cc-langs that doe not work correctly in batch mode, it
> fails to define or select the correct fontification function for gawk.
> In any case, it doesn't happen when you don't export in batch mode and
> Emacs 23 does not have that problem
Jay Kerns writes:
> Doing `toggle-debug-on-error' yields (I'm deleting most of it)
>
> ,
> | Debugger entered--Lisp error: (error "Invalid time specification")
> | format-time-string("%Y-%m-%d" "<2010-04-24 Sat>")
> | org-publish-format-file-entry("%t"
Uh-oh. That function should never ge
Jay Kerns writes:
> 1. I set up worg-local-init.el as you recommended and everything goes
>smoothly until here:
>
> ,
> | Publishing file /home/jay/git/worg/org-hacks.org using
> `org-html-publish-to-html'
> | Loading cc-langs...
> | Symbol's function definition is void: nil
> `
Yes, I
Philipp Moeller writes:
> as of 8.0 org-html uses org-html-head as a prefix for everything related
> to the HTML head. In one line the documentation is still referring to an
> old variable. AFAICT setting HTML_INCLUDE_STYLE also doesn't have any
> effect, but I haven't really confirmed that.
The d
Eric Schulte writes:
> If you mean that there should be new syntax for setting header arguments
> on a file or sub-tree basis w/o using file local variables, I'd be happy
> to apply a patch.
I'm thinking that something like
#+PROPERTY: header-args:R :session "*R*" :exports none
should work. I'v
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:
http://Synth.Stromek
I've been looking at export runtimes for large documents with the new
exporter. The example I've used is the orgmanual.org from Tom. I first
exported each subtree standalone, then the document as a whole to
texinfo. The startup of Emacs takes about 1 s of user time and 1.5 s of
wall time, these
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 an
Jay Kerns writes:
> The new Worg branch publishes for me without error under Org-mode
> version 8.0.1 (release_8.0.1-24-g92f372). I updated the existing
> emacs.el (underlying Worg, IIUC) to the Org 8.0 exporting/publishing
> syntax. You can see the latest draft in
>
> worgtest-init.el
>
> which l
Sebastien Vauban writes:
> Would we want to abstract the above, I guess we should generalize the
> languages families as:
>
> - graphics-only languages (ditaa, dot, gnuplot, etc.)
>
> - general-purpose languages with graphical capacities (R, maxima, octave...
> and, at least, python[1] IIUC)
>
>
Rainer Stengele writes:
> I update (git) and compile org inside of cygwin.
So do I.
> That means the info file will be installed in the cygwin tree.
No it won't if you configure local.mk accordingly.
> But I do use the Windows port of Emacs, not the cygwin port.
http://orgmode.org/worg/dev/org
Karl Voit writes:
> "C-h i" was my first guess but it does not list Org-mode at all :-(
C-u C-h i
But really,
make install-info
shouldn't be so hard to issue?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
ht
Christoph LANGE writes:
> thanks for your improvement suggestions! Before I put this into
> practice, let me ask some questions. I am neither an expert in
> distributing Org nor in writing ebuilds yet.
>
> 2013-04-22 18:21 Achim Gratz:
>>> ELISP_REMOVE="lisp/org-
Please put quotes around the definition of prefix:
prefix = "/Users/bernd.haug/Library/Application Support/Aquamacs Emacs"
(or individually quote each definition if you don't use prefix) which
should then produce the following output from "make config":
> = Emacs executable and Installa
Sebastien Vauban writes:
> What I once heard from ergonomical studies is that "black on white"
> was better than "white on black". Though, is it based on real grounds?
All these studies dependend on which CRT was used (most of which
produced blurry pictures for dark-on-light content) and are mostl
Bastien writes:
> If this is not possible, maybe we can add some #+CAPTION
> lines in the meantime?
I've replaced #+NAME by #+CAPTION, but nothing changes (not
unexpectedly). I'll leave it at that for the moment.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blof
Bastien writes:
> Should be fixed now, thanks.
Thanks. Now the Makefile examples are nicely fontified… Is there an
easy way to have the names of the source blocks added to the export as a
caption or header?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Worg stopped publishing... it dies on some invalid timestamp:
remote: Generating tree-style sitemap for Sitemap for project worg-pages
remote: Generating tree-style sitemap for Sitemap for project worg-pages
remote: Generating tree-style sitemap for Sitemap for project worg-pages
Christoph LANGE writes:
> Gentoo users may find my ebuild for app-emacs/org-mode-8.0.1 useful.
>ELISP_REMOVE="lisp/org-install.el"
You'll also want to remove org-loaddefs.el and org-version.el.
> elisp-install ${PN}/contrib contrib/lisp/*org*.el || die
This is wrong if you use ORG
Bernd Haug writes:
> Finally got to it; pulled up to current (cf shell output below),
> appended your snippet to local.mk and did a clean install:
You don't need to add this anymore (unless you copied the old definition
from default.mk), it is already in mainline Org. But you do need to
quote the
Thomas Koch writes:
> I wouldn't like to rely only on the sum of the time spent on tasks since
> there
> is always work time that can hardly be assigned to a specific task.
I have a heading that I clock stuff like all-hands meetings under that
shouldn't get booked to one of the projects I'm assi
Bastien writes:
>> Can we have some sort of a check while loading Org that picks up these
>> shadowed variables and "deletes" them?
>
> I think Achim has been thinking about some incantation for this
> (at install time). Maybe if this can be done after installation,
> we could document it somewher
Nicolas Goaziou writes:
> Of course, we could work around this with a new rule saying "the longest
> match wins", which, in this case, is the underline. But it would be
> better to find a more elegant solution, one which would remove the sole
> ambiguity, AFAICT, in Org syntax.
>
> Suggestions welc
Ivan Kanis writes:
> Just add (require 'org-macs) in org-macro.el.
Why do you think so?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Aaron Ecay writes:
> If your external org configuration file were kept under version control
> (I’ll discuss git but the principle is general), then reproducibility
> would be possible.
There's a lot more to reproducibility then just this, but yes, the
configuration files would have to be part of
Neuwirth Erich writes:
> I compiled from the repository after the announcement.
> On my Mac (OSX 10.8.3, Emacs 24.3.1) the test for maxima still fail.
> I reported this a few weeks ago.
I can't find any post from you on this mailing list that fits that
description and your last post mentioning max
Rick Frankel writes:
> Overall, Achim's updates to perl babel processing have been
> fantastic. But there seems to be a problem with :result output --
> there is no way to get a table.
Yes, that was not yet handled at all.
> Also, if the results are :value, the stdout is mixed in with the
> retur
Feng Shu writes:
> org-version: 8.0-pre (release_8.0-pre-416-gbf338e)
> makeinfo --no-split org.texi -o org
> org.texi:8719: No closing brace for footnote `'.
> org.texi:8719: Unmatched }.
> makeinfo: Removing output file `org' due to errors; use --force to preserve.
> make[1]: *** [org] Error 1
>
Eric Schulte writes:
> After walking through this patch, it looks like it provides exactly
> the correct behavior. Please go ahead and apply these changes.
Thanks for checking, pushed to master.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables
David Arroyo Menéndez writes:
> Package: Org-mode version 8.0-pre (release_8.0-pre-335-g4c426b-git @
> org-loaddefs.el can not be found!)
Before you go on posting reams of potentially bogus bug reports, could
you perhaps be bothered to fix your installation first by doing a
make autoloads
pleas
Loyall, David writes:
>> Then practically all programs are uncivilized, especially when
>> considering that dynamic libraries are just another form of external
>> executables.
>
> Yes. But would you grant me that this is done in a more orderly
> fashion?
It may appear that way, but the closer you
Bastien writes:
> (Sorry, I pushed a fix for the compiler warning that your patch also
> solves.)
Not in master, though?
> Achim Gratz writes:
>
>> Since the test suite doesn't really test confirmation at all, it would
>> be nice if someone with a good variety of B
Sebastien Vauban writes:
> Hello,
>
> I'm just trying to reuse ERT and run the tests on my (new, Bastien ;-))
> machine.
>
> Results:
>
> Ran 372 tests, 371 results as expected, 1 unexpected (2013-04-10
> 22:04:05+0200)
> 10 expected failures
>
> 1 unexpected results:
>FAILED test-org-babel/i
f5e52c2ab244c1b6ea67dada6e8a2eebb20 Mon Sep 17 00:00:00 2001
From: Achim Gratz
Date: Wed, 10 Apr 2013 20:28:31 +0200
Subject: [PATCH] Babel: avoid superfluous confirmation for internal wrapper
* lisp/ob-exp.el (org-babel-exp-results): Suppress user confirmation
of the emacs-lisp wrapper exec
Nicolas Goaziou writes:
>> Sorry, but using this has quadratic complexity with the number of
>> rows...
>
> That's true. But that doesn't matter unless you plan to export thousand
> row tables. Anyway, patches welcome.
I've been thinking about this… the way I currently see it is that the
row-numbe
Nicolas Goaziou writes:
> Indeed. I had forgotten to implement such a tool in ox.el. I added
> `org-export-table-row-number'.
Sorry, but using this has quadratic complexity with the number of
rows...
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD ada
John Hendy writes:
> Could you provide the equivalent at this repo?
> - http://sourceforge.net/projects/infozip/files/
As the name implies, that's where you get the sources.
> The ftp link above isnt showing any contents in my browser.
Get a browser that tells you why it doesn't show anything or
Bastien writes:
>> #+BEGIN_SRC R :results silent :exports results :session *ssh gauss* :cache
>> yes
[…]
>> with `:results output' instead of `:results: silent' everything works
>> fine.
>
> Please let us know if the documentation* needs some clarification here,
> or if this is a bug -- maybe s
John Hendy writes:
> Just tried doing my first ODT export while booted into Windows and
> don't have the zip utility that Org is looking for. From searching,
> this thread suggests Info-zip:
> - http://comments.gmane.org/gmane.emacs.orgmode/43994
You'll need the latest versions of unzip and zip.
Loyall, David writes:
> And that's why civilized programs don't depend on external executables
> from $PATH.
Then practically all programs are uncivilized, especially when
considering that dynamic libraries are just another form of external
executables.
> Now, I'd imagine that some people have ar
John Hendy writes:
> I'll keep thinking through it. For now, I got Windows working by
> simply editing ox-odt directly and replacing zip with zip.exe :)
The only reason I can think of why this should help is that you
somewhere have a file named "zip" (without any extension) in your path
and before
Sebastien Vauban writes:
> Achim Gratz wrote:
>> Elisp is different from all other languages: it doesn't do any
>> processing of strings to begin with for value returns. The reason that
>> Perl processes "raw" results is that org-babel-result-cond does not
>
Bastien altern.org> writes:
> > The angry unicorn is still in worg though ...
>
> And it's back on orgmode.org too.
Well let me say it again, I don't like it at all. The old unicorn seemed to
be blissful, which I think is what it should feel like using Org. Besides,
the new logo has some hard-
Rick Frankel writes:
> Missed verbatim. Thanks for the pointer, it works, but i think that
> perl is double-processing returned values. If we do the same things in
> elisp i get (my) expected results:
>
> #+begin_src elisp :results raw
> "|c1|c2|
> |-
> |a|1|
> |b|2|";
> #+end_src
Elisp is
Eric Schulte writes:
> Would it be difficult to add another set of code blocks which
> automatically compare the output of these automatically generated code
> blocks, indicating when there are differences.
I'd lobby for integration into the test framework.
>> I still think that the scalar pipe-d
Eric Schulte writes:
> Can you check if this change causes any of the existing tests to fail?
I don't think there is a test for that, at least I don't remember
anything in that direction. However when implementing my earlier change
w.r.t. confirmation I noticed that merging the parameters early h
Aaron Ecay writes:
> * lisp/ob-core.el (org-babel-check-confirm-evaluate): remove
> (org-babel-check-evaluate),
> (org-babel-confirm-evaluate): move logic here
>
> This macro is used in only two places, and has two almost-independent
> complex logics coded into it. So, suppress the macro and m
Aaron Ecay writes:
> * lisp/ob-core.el (org-babel-execute-src-block): Simplify control flow
>
> Avoid potential duplication of org-babel-process-params call. Also
> makes the code simpler.
You may be changing semantics here. I'm not entirely certain if the
current way of dealing with the the unm
Aaron Ecay writes:
> * lisp/ob-core.el (org-babel-if-in-src-block): New macro
[…]
> +(defmacro org-babel-when-in-src-block (&rest body)
> + `(if (or (org-babel-where-is-src-block-head)
> + (org-babel-get-inline-src-block-matches))
> + (progn
> + ,@body
> + t)
> + nil)
Am 28.03.2013 20:35, schrieb Andreas Leha:
so it seems, currently, I (and John...) can not have both, /file local/
and /language local/ variables.
- The emacs-lisp-block
#+begin_src emacs-lisp
(setq org-babel-default-header-args:R
'((:session . "org-R")))
#+end_src
works
Am 29.03.2013 09:24, schrieb Stefan Vollmar:
[...]
This might work reasonably well - if
(1) I could prevent the table from being exported to HTML,
(2) (probably more difficult) if this kind of thing would work:
#+call: hcard(v=card-table) :results html
It does, see:
http://orgmode.org/manual/E
Am 28.03.2013 21:49, schrieb Stefan Vollmar:
(1) "natural" multi-line
#+call: mhead-hcard(
cname="Dr. Stefan Vollmar", # full name for title
gname="Stefan", # given name
photo="stefan-vollmar.jpg", # can be jpg or png
...)
This doesn't parse well, so I venture to guess that N
Am 28.03.2013 15:41, schrieb Nicolas Goaziou:
Then you're contradicting yourself, since you also said:
I suggest to follow the lead of (La)TeX and determine begin and end of
such blocks by blank lines.
In your example, the end of the "P-block" isn't at the blank line. My
comment was on th
Am 28.03.2013 17:22, schrieb Nicolas Goaziou:
My point is that macro templates have to fit in a single line, no
newline character allowed. As a consequence, macro arguments are
implicitly expected to fit in a single line. So a newline character in
an argument is probably wrong.
My point is that
Am 27.03.2013 17:26, schrieb Nicolas Goaziou:
I think all newline characters should be replaced with a whitespace
character in macro arguments. Indeed, macro templates are only one line
long but unwanted "\n" could be inserted by paragraph filling in
arguments.
I'm not sure about that, it would
Am 27.03.2013 16:48, schrieb Nicolas Goaziou:
So this would be a single P-Block with an annotation inside:
8<
There is an annotation by the original author here
#+BEGIN_ANNOTATION
I never meant to break this paragraph.
#+END_ANNOTATION
in the middle of the paragraph
Am 26.03.2013 13:37, schrieb Eric Schulte:
This can be done system wide by setting the language-specific header
arguments.
I've yet to see an example on how to do this.
This can also be done file-wide through the use of file
local variables (instead of the property line above).
Still, lang
Am 25.03.2013 23:15, schrieb Nicolas Goaziou:
The proper way to handle this is to introduce a new syntax for
inlined annotations and to treat them appropriately in exporters.
Since we have both #+begin_src and src_{...} I'd suggest
having annotation_{...} or something similar.
I would suggest
Am 25.03.2013 17:57, schrieb Bastien:
Can you evaluate my patch against the current state of affair?
The current state of affairs is this:
1. Gnus is doing something it shouldn't do, even though it may once have
been OK or at least not dangerous.
2. Org doesn't have something that can direc
Am 25.03.2013 18:05, schrieb Bastien:
I gave it another try. Please let me know.
Now add an annotation at the end of a paragraph... it simply doesn't
work unless org-element gets proper support for telling the exporter
which Org "paragraph" elements should be exported together as a single
p
Am 25.03.2013 17:12, schrieb Christian Moe:
Thanks for looking into this. I just pulled and tested, but I cannot
confirm the fix yet. I still get paragraph breaks around annotations
with Org-mode version 8.0-pre (release_8.0-pre-219-g8eb0d6).
It can't be fixed this way since annotations end the
Am 25.03.2013 16:54, schrieb Bastien:
What about this patch?
I don't think Gnus should be switching major modes just to get
fontification and definitely not with Org.
The change in Gnus is then trivial (see other patch).
Again, I'd rather have a derived mode (org-safe-mode, perhaps) that
Am 25.03.2013 12:53, schrieb Andreas Röhler:
make all builds some .pdf and .html docu, but not info
It does, the info file is called "org".
Regards,
--
Achim.
(on the road :-)
Am 25.03.2013 15:57, schrieb Bastien:
I'm not entirely sure what Gnus does to trigger that foray into Org
(a quick glance in the documentation didn't show anything), but if
anything this indicates that we might need a "safe mode" for Org to
open untrusted files.
Feel free to propose a better be
Am 25.03.2013 14:49, schrieb John Hendy:
$ git clone http://orgmode.org/r/worg.git
Cloning into 'worg'...
fatal: http://orgmode.org/r/worg.git/info/refs?service=git-upload-pack
not found: did you run git update-server-info on the server?
It looks like thios for of HTTP access has been switched
Am 25.03.2013 11:29, schrieb Christian Moe:
Thanks for the tip. I don't think user-side hacks are the way to go
here, though. Org-odt provides an annotation feature for ODT export,
based on using the special-block syntax, that no longer works as
intended. I'm hoping it can simply be fixed, but if
Am 25.03.2013 06:45, schrieb Bastien:
Bastien writes:
This is a problem with Org -- I have a patch for this on my local
branch, but I will push this branch only tomorrow.
Applied now, thanks.
I'd like to ask you to revisit that change. I don't think the question
of whether #+SETUPFILE sh
Am 25.03.2013 10:14, schrieb Carsten Dominik:
I would like to know what the plans are here.
Does this discussion help?
http://thread.gmane.org/gmane.emacs.orgmode/68940
Regards,
--
Achim.
(on the road :-)
Am 24.03.2013 18:52, schrieb John Hendy:
$ git clone http://orgmode.org/w/worg.git
Try
$ git clone http://orgmode.org/r/worg.git
(note how the "w/" changes to an "r/").
Regards,
--
Achim.
(on the road :-)
Am 25.03.2013 01:41, schrieb Trevor Murphy:
(add-to-list 'load-path "/home/trevor/.emacs.d/elpa/org-20130318/")
Don't do this with Org from ELPA, I don't think it will work. Try
'(package-initialize)' instead.
Seems that the defvar counts for nothing? Perhaps because it's already a
defcust
Am 25.03.2013 01:27, schrieb Eric Schulte:
The attached patch fixes this behavior, however I haven't committed it
because I fear it would undo some of Achim's intentions in commit
ca125b82b. I'll leave the final solution to Achim.
This should be the right solution, please commit. However, the
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.
http://www.gnu.org/software/emacs/manual/html_node/elisp/Anonymous-Functions.htm
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) ?\\)
Am 22.03.2013 08:36, schrieb Bastien:
Do you know any free (as-in-speech), easy-to-use alternative?
Hudson. However, I don't think that a CI framework is what we need or
want. As I said, simply running the tests (preferrably with two
different versions of Emacs) should be enough for now. U
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
"\\(+\\)?\\(
Am 21.03.2013 18:59, schrieb Bastien:
Please see my reply to Yagnesh.
It clearly describes a situation where automatically running tests
with a pre-push hook would be a problem.
You keep mentioning a pre-push-hook to be run on the developers machine.
However, the test would run on the server
Am 21.03.2013 14:41, schrieb Bastien:
The test are not automatic, they are manually triggered, so we don't
have an "automated tests framework" -- or am I misunderstanding what
an automated test framework is?
What you probably have in mind is a continuous integration framework
that triggers the
Am 20.03.2013 16:16, schrieb John Hendy:
From the descriptions, I don't understand the difference between:
- make- build Org ELisp and all documentation
- make autoloads - create org-loaddefs.el to load Org in-place
Is =make= *also* making autoloads, and =make autoloads= is
Am 20.03.2013 14:47, schrieb Bastien:
If anyone knows how to setup an automated tests framework for Org,
feel free to go ahead, we will use it and monitor broken tests to
see what's wrong in the code or in the tests or in the environment
running the tests.
We already have one, what Nick and Se
Eric Schulte writes:
> I just pushed up a patch which should allow code blocks to find
> un-named results even when there are comment lines (such as #+options
> or #+attr_backend) between the code block and the results.
Shouldn't babel use org-element for things like this?
Regards,
Achim.
--
+<
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 ac
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 filenam
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
Date: Sun, 17 Mar 2013 10:20:10 +0100
Subject: [PATCH] fix macro expansion with separators and backslas
Nicolas Goaziou writes:
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser. I also added some comments. I am going
> to put the Org file on Worg, so anyone can update it and fix mistakes.
after some playing with the Org manual in Org that T
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.tex
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 e
Neuwirth Erich writes:
> I put my old source directory away and started afresh:
> git clone git://orgmode.org/org-mode.git
I'm not sure what you were trying to accomplish. You can always check
with "git status" what's going on in your worktree and if necessary you
can "git clean" anything you thi
Bastien writes:
> If we agree the macros are not really needed we can make the change.
> We will always be free to find why the macros are causing problems
> later one. I know the move looks like I want to avoid the problems
> instead of fixing them, but it's not: it's about fixing the approach
>
Thomas S. Dye writes:
> Thanks for your help and patience as I try to find the simplest, most
> widely applicable, path to a successful Org installation.
I especially like the fact that it didn't get longer than before.
>In most cases where you have permission to write to system locations,
>
Bastien altern.org> writes:
> One potential problem in the first test is the use of "parent" as the
> name of the symbol to pass to the macro... since this is the very same
> name than the macro second argument. At least this reminded me this
> section of Elisp manual:
I've actually tested this
501 - 600 of 1726 matches
Mail list logo
