[O] Zero Warnings against Emacs-24

It is extremely good to see Org-mode builds against Emacs-24 with zero warnings. (with make up1 autoloads) Org-mode rocks, /and/ plays nicely with Emacs. Thanks Bastien, Achim, and Maintainers ~ I for one think such attention to detail is a real sign of quality. Also with zero test failures o

Re: [O] local.mk and SUDO

Achim Gratz writes: > Martyn Jago writes: >>>> diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el >>>> old mode 100644 >>>> new mode 100755 [...] > Then you yourself must most likely have changed the mode of those files > to "executable

Re: [O] Symbol's value as variable is void: org-version

Martyn Jago writes: > Hi Thomas > > t...@tsdye.com (Thomas S. Dye) writes: > > >> Aloha all, >> >> In the last day or so, I started running into a problem with a variable, >> org-version. >> >> When I look at Org/Documentation/Show Versi

Re: [O] Symbol's value as variable is void: org-version

Hi Thomas t...@tsdye.com (Thomas S. Dye) writes: > Aloha all, > > In the last day or so, I started running into a problem with a variable, > org-version. > > When I look at Org/Documentation/Show Version, I get: > Org-mode version N/A (N/A @ /Users/dk/.emacs.d/src/org/lisp/org-install.el) The

Re: [O] var `date' lacks a prefix warnings

Hi Bastien Bastien writes: > Hi Martyn, > > Martyn Jago writes: > [...] > We first need to fix Calendar so that it doesn't use ̀date' and `entry' > as the name for dynamically variables that are passed around. > > Then preparing a patch for Org wou

Re: [O] var `date' lacks a prefix warnings

Hi Achim Achim Gratz writes: > Martyn Jago writes: >> Regarding the remaining Org-mode `lacks a prefix' warnings and >> particularly in light of the recent message on emacs.devel [1] would it >> not be sufficient to simply alias date and entry locally: >>

Re: [O] local.mk and SUDO

Hi Achim Achim Gratz writes: > Martyn Jago writes: >> However, when I've just gone to run `make up2' (awesome command by the >> way), I get the error: > [...] >> diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el >> old mode 100644 >> new mo

[O] var `date' lacks a prefix warnings

Regarding the remaining Org-mode `lacks a prefix' warnings and particularly in light of the recent message on emacs.devel [1] would it not be sufficient to simply alias date and entry locally: --8<---cut here---start->8--- (defvaralias 'org--date 'date) (defvar

[O] local.mk and SUDO

I have a local.mk set up with my particular settings, and with SUDO set to blank, as per the comment in default.mk: ,[default.mk] | # How to obtain administrative privileges | # SUDO= # leave blank if you don't need this | SUDO = sudo ` ...since my org-mode files location

Re: [O] missing autoloads / (void-variable org-version)

Hi Achim Achim Gratz writes: > Since my Makefile branch was merged I've been getting flak for breaking > certain setups. Now, the change didn't actually break them, but I did > make (perhaps foolishly) a deliberate decision to make that particular > breakage fatal rather than silent. It would

Re: [O] error on opening org-file with #+startup: indent

Hi Achim Achim Gratz writes: > Fritz Kunze writes: >>      I ran M-x load-library org followed by M-x org-version - which >> returned 7.8.09.  > > You didn't generate and (require 'org-install). > >>           (Incidentally, and for the sake of completeness in this >> report, I built the compile

Re: [O] Makefile restructuring

Achim Gratz writes: Hi Achim > Martyn Jago writes: >> Works nicely for me too, and I have a modified local.mk config for >> multiple Emacs versions and a non-default org location. >> >> Note: `make install check' will make, install, and run the tests! > >

Re: [O] Makefile restructuring

Hi Achim François Allisson writes: >> Achim's branch is now merged in Org's git master branch. >> >> Please test this and report any problem while using make >> to install Org. >> >> -- >> Bastien >> > > It runs smoothly for me, using make clean, make, make doc, and make > install (without

[O] [bug] Regression due to relocation of org-export.el

Hi There's a small regression in org-export due to removal of EXPERIMENTAL / relocation. Best, Martyn >From eb3c7717cdd4a4dc1e5f76da4746293ff6f40d17 Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Sat, 21 Apr 2012 18:02:27 +0100 Subject: [PATCH] Fix require path due to re

Re: [O] org-program-exists vs executable-find

Hi "Sebastien Vauban" writes: > Hi Bastien, > > Bastien wrote: >> "Sebastien Vauban" writes: >> The name `org-program-exists' is actually misleading, it should be `org-executable-call' instead, while still checking if the executable exists before calling it. >>> >>> Nope, the nam

Re: [O] Frequent crashes of Emacs 24 on Mac OS X 10.7.3 due to org-mode

Ho Marius Marius Hofert writes: > There was another crash this morning, here is the report (as from > Console.app): > > Process: Emacs [6378] > Path:/Applications/Emacs.app/Contents/MacOS/Emacs > Identifier: org.gnu.Emacs > Version: Version 24.0.95 (9.0) > Code

Re: [O] Frequent crashes of Emacs 24 on Mac OS X 10.7.3 due to org-mode

Hi Marius Marius Hofert writes: > Hi, > > I work with GNU Emacs 24.0.95.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) > [installed as Emacs-pretest-24.0.95-universal-10.6.8 from > http://emacsformacosx.com/builds ] on Mac OS X 10.7.3. (The reason for Emacs > 24 > is because of the latest fea

Re: [O] Ever used org-mode contrib packages?

suvayu ali writes: > Hi François, > > On Wed, Apr 11, 2012 at 21:22, François Allisson wrote: >> I'm curious >> to know what you are using from org-contrib... > > - I use org-notmuch to link to emails from org files. > - I also use org-occur-goto for easier navigation. > - I also use org-google-

[O] [bug] (org-todo-list ) causes exception with sticky agenda buffers.

Hi I've noticed that if (org-todo-list ) is called programatically where `org-agenda-sticky' is set to t, an exception is caused: The exception happens in (org-prepare-agenda ): --8<---cut here---start->8--- (defun org-prepare-agenda (&optional name) (if (or

Re: [O] buffer-wide tangle filename

"Julian Burgos" writes: > Hello everyone, > This may be a very simple question. I want to tangle multiple source code > blocks into a single file. Instead of using the same output filename as a > block header (e.g. :tangle output.el) in each code block, can I I define a > buffer-wide tangle fil

Re: [O] Sticky Agenda buffer: Announcement and request for testing

Rainer Stengele writes: [...] +1 Works very well for me. My Org Agenda usage has modified somewhat thanks to the use of 'org-agenda-sticky and I really like my current usage. Thanks! Martyn --- Org-mode version 7.8.06 (release_7.8.03.594.g013d) GNU Emacs 24.0.94.1 (x86_64-apple-darwin, NS

Re: [O] GSoC 2012 -- Elisp backend for Ragel

Hi, and welcome Aurélien, Nicolas Goaziou writes: > Hello, > > Aurélien Aptel writes: > >> On Sun, Mar 25, 2012 at 6:17 AM, Rustom Mody wrote: >>> FYI, there is already an elisp Org parser being worked on in development >>> branch of Org mode. It isn't finished yet, but still advanced enough s

Re: [O] [patch][babel] ob-lilypond maintenance

Hi Bastien Bastien writes: > Hi Martyn, > > Martyn Jago writes: > >> Maintenance patches: >> >> 1) Fix compiler warning >> 2) Leave versioning to Org >> 3) Set `no cache' default in audition mode >> 4) Redirect `homepage' to Worg

[O] [patch][babel] ob-lilypond maintenance

Maintenance patches: 1) Fix compiler warning 2) Leave versioning to Org 3) Set `no cache' default in audition mode 4) Redirect `homepage' to Worg Best, Martyn >From 5fc49bc167c8fcc194c1c5761ea25c0a625500cb Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Wed, 21 Mar 2012 0

Re: [O] Should maint branch be deprecated?

Bastien writes: Hi Bastien, Achim > Hi Martyn, > > Martyn Jago writes: > >> As an infrequent committer to org-mode, I wonder if the maint branch is >> more pain than gain. > > It is a pain when too many things should happen on it. > > IMO It is a gain

[O] Should maint branch be deprecated?

As an infrequent committer to org-mode, I wonder if the maint branch is more pain than gain. I've read through the mails arguing for its conception, and the benefits just don't appear to be resultant. Add to that - infrequent committer's who commit via the list generally know nothing about the

Re: [O] Org release 7.8.04 (BUGFIX-only release)

Hi Since all the `errors' are whitespace it may be better to work around the release? Best Martyn Achim Gratz writes: > Achim Gratz writes: >> Well, all this "manual reverting" messed up master quite royally. I >> haven't checked maint, but things might be a bit easier there. I'm >> current

Re: [O] ob-lilypond open pdf and midi asynchroniously

Hi Ezequiel > Ezequiel Birman writes: > Is there a reason to not append "&" to shell-command's args? I get > disconnected from ERC/Bitlbee each time I peek at the score too long. Apologies for my delayed response - I've been rather busy. I've pushed a patch to the list to make auditioning of pd

[O] [babel][patch] Make ob-lilypond audition calls asynchronous

Hi A patch to make ob-lilypond audition calls asynchronous (and tests). Best, Martyn >From 2e7cd607cd6dbc25edd5ff9972fbd2528d48416e Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Sat, 10 Mar 2012 15:00:57 + Subject: [PATCH] Make auditioning of midi and pdf generations asynchronous,

Re: [O] [babel][patch] sqlite3 in org-babel

Added [babe][patch] to title to avoid patch being overlooked. Best, Martyn Daniel Clemente writes: > Hi, >org-babel works well with sqlite3 if you add this (which I propose for > inclusion): > > - > diff --git a/lisp/ob-sql.el b/lisp/ob-sql.el > index 3f7882c..a59db

Re: [O] Updating the Babel section of Worg

Hi Thomas and Eric Love it. I will try to help! Worg is a great resource that is getting better and better. The template looks good (Babel wise) and should be up there as a check-sheet, although maybe not as a requirement. Eric - perhaps mark good pages as good rather than bad pages. They're no

Re: [O] [babel][patch] BUG in inline source blocks

Hi Eric Andreas Leha writes: [...] >> Thanks for this patch Martyn, I just pushed up your [:punct:] change. >> >>> >>> Hi Martyn, >>> >>> thanks for this patch! It does half the job for me. Now export (or >>> evaluation) already work. But in the export I get a space inserted. >>> >>> I my e

Re: [O] Export without code blocks

Martyn Jago writes: > Hi Aaron > > aaron barclay writes: > >> Hi, >> >> I am having trouble finding the correct way to export a document without >> the code blocks included. Should I be using #+EXPORT_EXCLUDE_TAGS? I can't >> seem to get it to wor

Re: [O] Export without code blocks

Hi Aaron aaron barclay writes: > Hi, > > I am having trouble finding the correct way to export a document without > the code blocks included. Should I be using #+EXPORT_EXCLUDE_TAGS? I can't > seem to get it to work, anyone have the correct syntax? > > cheers, > aaron. #+EXPORT_EXCLUDE_TAGS is

Re: [O] [babel][patch] BUG in inline source blocks

Martyn Jago writes: > Hi, > > Andreas Leha writes: > >> Hi all, >> >> I experience unexpected behaviour when an inline source block is not >> preceded by whitespace. >> >> Example: >> === >> * Test inlin

Re: [O] [babel][patch] BUG in inline source blocks

7; example. Patch is attached for consideration. Best, Martyn >From ce7ccfe97ce640f47ed83cdb2fdb6ffa8a6d3c54 Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Thu, 26 Jan 2012 13:22:25 + Subject: [PATCH] Fix for where inline source block is not preceded by whitespace but by punctuation (reported

Re: [O] [babel][patch] provide consistent result removal (type `wrap')

[...] Oops - patch provided at start of this thread is malformed and should be ignored. The correct patch is provided below for consideration. Apologies for the noise. Best, Martyn Martyn Jago writes: > Patch to fix `org-babel-result-end' command to provide consistent result &

[O] [babel][patch] provide consistent result removal (type `wrap')

est-ob/org-babel-remove-result--results-wrap' which is uncommented in the patch. Best, Martyn >From a4b2f8484ec4810e7a891b4db0caf5463e96a58d Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Tue, 24 Jan 2012 15:39:30 + Subject: [PATCH] Fix `org-babel-result-end' command to pr

Re: [O] export-as-hmtl fail

Hi Aaron aaron barclay writes: > Hello, > > When I use a python code block in a document any export-as-html results in > the error "Invalid file-name". Without a code block the export goes without > a hitch. Other exports work no probs such as export-as-ascii. The code > block within the documen

Re: [O] [ANN] ASCII back-end for new export engine

Hi Nicolas Goaziou writes: [...] >> 1) The commented out `# :exports both' appears to be exported as >> uncommented and relevant (actually, this appears to be true of the >> original exporter too). > > I cannot reproduce it. Anyway, see my comments below. > >> 2) If the source block is execute

Re: [O] [ANN] ASCII back-end for new export engine

Hi Nicolas Nicolas Goaziou writes: > Hello, > > I've commited an ASCII back-end for new export engine. > > Assuming contrib directory is in your load-path, you just need to > (require 'org-export) to have both LaTeX and ASCII exporters ready to > boot. > > You can then access to the dispatcher w

Re: [O] [BUG] Inconsistency in src block hiding

Hi Nicolas Goaziou writes: > Hello, > > Eric Schulte writes: > >> Well maybe we should roll back this change. > > Please don't. _That_ would be a regression. > These changes /have/ caused a software regression, and should be reverted immediately, since: - they change current expected and imp

[O] org-property-accumulation tests broken

Just a testing head's up... commit f1043a53cc46d2ce2e578d3cb498f895dc65f1ff breaks the tests. FAILED test-org-property-accumulation-append-use FAILED test-org-property-accumulation-append-val FAILED test-org-property-accumulation-top-use FAILED test-org-property-accumulation-top-

Re: [O] Capitalisation and good taste ?

pin...@iro.umontreal.ca (François Pinard) writes: > Bastien writes: > >> Eric Schulte writes: > >>> That said I'm happy that Org-mode is forgiving enough to allow me to >>> lowercase most of my keywords locally. > >> Actually, I'm thinking of another solution: > >> - keep one-line option/environ

Re: [O] [patch][babel] `org-babel-result-end' bug fix and regression tests

ly those > tests which should still apply? This results handling is certainly an > area which will benefit from beefing up the test suite. The attached patch contains the remaining tests. Best, Martyn >From 6700e3f350c76f68891ad0ccd35538b5523312d9 Mon Sep 17 00:00:00 2001 From: Martyn

Re: [O] [patch][babel] `org-babel-result-end' bug fix and regression tests

Eric Schulte writes: Hi Eric > Hi Martyn, > > Unfortunately there is no way to remove raw results because there is no > way to know where the results end. While your patch will certainly work > most of the time, it will not work in cases where the results includes > an empty line, and ultimately

Re: [O] [patch][babel] Fix latest block export tests to suit Emacs 22

Bastien writes: > Martyn Jago writes: > >> What appears to be a subtle difference in html export detail between >> Emacs 22 and Emacs 23+ breaks these latest tests on Emacs 22. >> >> The attached patch fixes them (and the subtle difference is not relevant >>

[O] [patch][babel] `org-babel-result-end' bug fix and regression tests

' correctly removes the result. Best, Martyn >From 5a3148fb1e3de288e5e3534ceb06eb64c20697aa Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Fri, 6 Jan 2012 17:10:00 + Subject: [PATCH] `org-babel-result-end' bug fix and `org-babel-remove-result' regression tests. * lisp/ob.el: T

Re: [O] [patch][test] Avoid writes to non-temp test-example files

Achim Gratz writes: > Achim Gratz writes: >> It may still have to >> do with the environment — I start NTemacs from Cygwin to be able to use >> Cygwin's make and this combination is somewhat fragile. > > ... and that seems indeed to be the culprit, running NTemacs from the > Cygwin shell somehow

[O] [patch][babel] Fix latest block export tests to suit Emacs 22

00:00:00 2001 From: Martyn Jago Date: Fri, 6 Jan 2012 08:08:21 + Subject: [PATCH] Changes to latest block export tests to suit Emacs 22. * testing/lisp/test-ob-exp.el: Changes to latest block export tests to suit Emacs 22. --- testing/lisp/test-ob-exp.el |

Re: [O] [patch][babel] test fix - was: Add test-run capability to Makefile

Martyn Jago writes: [...] > > However before you test it could you consider applying the following > patch. It is a fix to a relative character position offset change of 2 > caused by the trailing whitespace cleanup (my bad for leaving dirty test > data)! > [...] This p

Re: [O] [patch][test] Avoid writes to non-temp test-example files

Achim Gratz writes: > Martyn Jago writes: >> Attached is a patch to modify all tests that currently write to non-temp >> test-example files such as `testing/babel.org'. Instead, the tests now >> write to temp files, which are thrown away at the conclusion of the >

[O] [patch][babel] Fix for bug in ob-emacs-lisp.el

911e Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Thu, 5 Jan 2012 18:00:12 + Subject: [PATCH] Bug fix in ob-emacs-lisp.el. * lisp/ob-emacs-lisp.el: A comment on the last line of an emacs-lisp code block would cause an error when the block is was executed. This fix cures this behaviour. *

[O] [patch][test] Fix and suplement pending tests in test-ob-exp.el

Fix pending tests in test-ob-exp.el related to exporting blocks with various header arguments. Best, Martyn >From e71a64c531969876e9bba0659db2308a97806e5d Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Thu, 5 Jan 2012 15:49:16 + Subject: [PATCH] Fixed and suplemented pending tests

Re: [O] [patch][test] Avoid writes to non-temp test-example files

Nick Dokos writes: > Martyn Jago wrote: > >> >> Attached is a patch to modify all tests that currently write to non-temp >> test-example files such as `testing/babel.org'. Instead, the tests now >> write to temp files, which are thrown away at the conclus

Re: [O] [patch] Add test-run capability to Makefile

Bastien writes: > Martyn Jago writes: > >> Since the Makefile is currently getting a refresh I thought it would be >> very useful to allow running of the regression test suite directly from >> make using `make test'. > > Nice -- I will test this through

[O] [patch][test] Avoid writes to non-temp test-example files

>From c56d5101de63bda4a0df7bf0800761f51624194b Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Wed, 4 Jan 2012 17:44:09 + Subject: [PATCH] Modify tests to avoid writing to non-temp test-example files. * testing/examples/babel.org: * testing/examples/table.org: * testing/lisp/test-ob.el: * testing/lisp/test-org-table.el

[O] [patch] Add test-run capability to Makefile

ation. This makes it super-easy for a user to validate their latest org-mode installation. HTH Best, Martyn >From f025591e918d8921eaea0188da0b0da806c8b6f6 Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Wed, 4 Jan 2012 14:24:27 + Subject: [PATCH] Add test command to Makefile * Makefil

[O] [babel][patch] org-test-with-temp-text-in-file works in Emacs 22

-ob-lob/do-not-eval-lob-lines-in-example-blocks-on-export' on Emacs 22. This fixes the remaining unexpected test failure on Emacs 22.1.1 Best, Martyn >From 5622523ccc9995ff6a0c804c4de8c414ca5e6181 Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Wed, 4 Jan 2012 13:37:07 + Subject: [P

Re: [O] [babel][bug] org-babel-balanced-split (with Emacs-22)

Eric Schulte writes: > Martyn Jago writes: > >> Martyn Jago writes: >> >> [...] >> >> The problem appears to be associated with the way `member' works: >> >> - on Emacs 23+ the following doesn't generate an error >

Re: [O] [babel][bug] org-babel-balanced-split (with Emacs-22)

Martyn Jago writes: > There is a bug running babel on Emacs 22.1.1 with a minimal init file. > [...] > > The following fails: > > * Test fails > > #+begin_src emacs-lisp :results silent > > "hello there" > > #+end_src > [...] The problem app

[O] [babel][bug]

There is a bug running babel on Emacs 22.1.1 with a minimal init file. The following code works: --8<---cut here---start->8--- * Test passes #+begin_src emacs-lisp "hello there" #+end_src #+results: : hello there --8<---cut here---

Re: [O] Happy new year!

Bastien writes: > Dear all, > > time to wrap-up for today and to celebrate. > This has been a *great* year of development! > May all your TODOs belong to your %s_archive. > > Happy new year :) Indeed! Bonne année et bonne santé! It's time to get the glad rags on and C-c C-c :)

Re: [O] ca47d10e commit broke the build

Hi Jambunathan Jambunathan K writes: > Martyn > > The probelmatic commit could actually be this: > commit - 07f006e4fd9a7b66643cd7b404c8994665ba8300 > which touches the Makefile. The problem was indeed related to the Makefile - the thing that changed (I'm guessing) is the use of the EMACS

[O] ca47d10e commit broke the build

Frankly I'm not sure why, but my build is broken against emacs 22,23,24 Ref: http://martynjago.co.uk:/builds/Org-mode_on_Emacs_24/ca47d10e1f0070f5c6461ff763486b693ff77209 Best, Martyn

Re: [O] Refresh of http://orgmode.org

Bastien writes: > Dear all, > > I made a small refresh of the website. > > http://orgmode.org > > - random quote (taken from worg/org-quotes.org) > - random screenshot > - twitter feed > - g+/flattr/fb buttons > - french translation (http://orgmode.org/fr/) > > If you want to help with the transl

Re: [O] Worg migration complete

Hi Jason Achim Gratz writes: > Nick Dokos writes: >> ... but then you'll encounter problems when you try to push, right? > > Yes. It's sorted now, thanks to Jason. First there was some bogus > newlines in the authentication file of the server, so some keys were not > recognized. The remote t

Re: [O] Bastiens talk

Hi Bastien writes: > Rustom Mody writes: > >> I'll try and flesh out the rest and post it here > > http://orgmode.org/worg/org-tutorials/org-screencasts/ghm2011-demo.html > > Next step is to have worg-links to the main concepts presented here. > > Thanks! I think this is a great screencast for

Re: [O] [bug] Commit 6f8ea8e breaks the build

Hi Jambunathan Jambunathan K writes: > Martyn Jago writes: > >> Commit 6f8ea8e breaks the build. > >>> make clean >>> make >> >> ...returns the error: >> >> >> emacs -batch -q -no-site-file -eval "(setq load-path (cons (e

[O] [bug] Commit 6f8ea8e breaks the build

Commit 6f8ea8e breaks the build. > make clean > make ...returns the error: --8<---cut here---start->8--- emacs -batch -q -no-site-file -eval "(setq load-path (cons (expand-file-name \"./lisp/\") (cons \"/usr/local/share/emacs/site-lisp\" load-path)))" -f b

Re: [O] [PATCH] Lilypond: added PDF output

Hi Torsten Torsten Anders writes: > Dear all, > > The current implementation how org-babel calls Lilypond hard-wires the > supported output file formats to EPS and PNG. Attached is a very > simple patch that adds support for PDF as well, so that resulting PDF > files can be directly integrated i

Re: [O] [BUG] org-table: time difference delivers wrong results

Martyn Jago writes: Apologies I had a typo - please ignore the previous mail. So this looks more sensible: > Daniel Bausch writes: > >> Anyone? It might be a duplicate of what Gustav Wiktröm reported on 1st of >> September, but his problem was not resolved, either. >

Re: [O] [BUG] org-table: time difference delivers wrong results

Daniel Bausch writes: > Anyone? It might be a duplicate of what Gustav Wiktröm reported on 1st of > September, but his problem was not resolved, either. > > Daniel > > Am Dienstag 15. November 2011, 22:12:45 schrieb Daniel Bausch: >> Hello list, >> >> consider the following example: >> |

[O] Updating Worg re standard source block syntax

Hi There are literally hundreds of uses of #+srcname and #+source within Worg - should I be updating these to #+name ? In other words, does Worg reflect the last official release (the Emacs release), or the bleeding edge (I tend to assume the latter because of the Org community spirit of Worg), bu

Re: [O] Bugs in lisp/ob-lilypond.el

Martyn Jago writes: Hi Torsten > Hi Torston > > Torsten Anders writes: > >> Also, the setting results: silent seems to be ignored. >> >> Best wishes, >> Torsten >> >> >> On 19 Nov 2011, at 15:22, Torsten Anders wrote: >> >&

Re: [O] [ANN] Org Elements in contrib

Nicolas Goaziou writes: Hi Nicolas > Hello, > > > I've added org-element.el in contrib directory. It is a complete parser > and interpreter for Org syntax. > > While it was written to be extensible, it is also an attempt to > normalize current syntax and provide guidance for its evolution. > > Or

Re: [O] [babel] :var assignment no longer tolerant of whitespace

Eric Schulte writes: Hi Eric > Hi Martyn, > > Tom mentioned this regression earlier and I treated it as a new > restriction on variable specifications, but if multiple people are > running into this issue I suppose spaces around equals should be > supported. > > I have just pushed up a change and

[O] [babel] :var assignment no longer tolerant of whitespace

Martyn Jago writes: (Fixed typos in heading) Hi It used to be the case that you could assign a variable and any whitespace would be chomped: #+begin_src emacs-lisp :var a = 1 :var b = 2 (+ a b) #+end_src However it is now required to remove the whitespace: #+begin_src emacs-lisp :var a

[O] [babe] :var assignment no longer of tolerant of whitespace

Hi It used to be the case that you could assign a variable and any whitespace would be chomped: --8<---cut here---start->8--- #+begin_src emacs-lisp :var a = 1 :var b = 2 (+ a b) #+end_src --8<---cut here---end--->8--- H

Re: [O] Bugs in lisp/ob-lilypond.el

Hi Torston Torsten Anders writes: > Also, the setting results: silent seems to be ignored. > > Best wishes, > Torsten > > > On 19 Nov 2011, at 15:22, Torsten Anders wrote: > >> Dear Martyn Jago, dear all, >> >> I just pulled the latest version of

Re: [O] Export #+call: within example block

Eric Schulte writes: Thanks Eric - sorted my script. Best, Martyn > Hi Martyn, > > Thanks for pointing out this bug. I've just pushed up a fix and a test > case. > > Cheers -- Eric > > Martyn Jago writes: > >> Hi >> >> Is there a way to

[O] Export #+call: within example block

Hi Is there a way to export the following, is this a bug, or is there a work-around (to HTML)? --8<---cut here---start->8--- #+begin_example #+call: rubbish() #+end_example --8<---cut here---end--->8--- For instance thi

Re: [O] [bug][babel] #+call: execution broken

Eric Schulte writes: > Martyn Jago writes: > >> Hi >> >> C-c C-c on a #+call: block() statement no longer causes the block to >> execute. >> >> This regression occurred on Nov 8th: >> >> commit a4273cbe0e0480bd02c59464cafb985951b1c5a2 >&

[O] [bug][babel] #+call: execution broken

I've supplied a patch which provides a couple of failing tests which highlight the problem. Best, Martyn >From 68a64d29222548eff3f414b8881f583f50ea4a96 Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Thu, 17 Nov 2011 12:33:08 + Subject: [PATCH] Tests for testing basic `#+cal

Re: [O] [bug] regression tests broken

actual deployment (currently on OSX). Best, Martyn > Thanks -- Eric > >> >> Best Martyn >> >>> Thanks -- Eric >>> >>> Martyn Jago writes: >>> >>>> Hi >>>> >>>> All automated regression tests broken since 7720786 commit >>>> >>>> http://martynjago.com: >>>> >>>> Best, Martyn >>>> >>>> >> >>

Re: [O] [bug] regression tests broken

and is particularly annoying during test development. Below is a patch > that fixes this problem for me. > >From b868e208dd3ece7c10818ed73f2cf0dc86dac94b Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Sun, 13 Nov 2011 16:03:51 + Subject: [PATCH] Fix don't load symlinks (Emacs interloc

Re: [O] [bug] regression tests broken

Martyn Jago writes: Hi Eric [...] Further to the problem of tests failing under sandboxed conditions unexpectedly, I've made a few observations which I want to pass on. * ID Currently the ID searching command `org-id-find' has global scope to find ID's all over the hos

Re: [O] [bug] regression tests broken

s other gnu projects that use cruisecontrolrb. Your server would need Ruby installed (I use v1.9.2), but installation should be straight-forward since I have already written the scripts, which is fairly simple anyway. Hope that helps Best Martyn > Thanks -- Eric > > Martyn Jago writes: > &g

[O] [bug] regression tests broken

Hi All automated regression tests broken since 7720786 commit http://martynjago.com: Best, Martyn

Re: [O] [test] Failure on GNU Emacs 22.3.2 (i686-pc-linux-gnu) of 2011-05-28 on x60s

David Maus writes: > Running the test suit on > > GNU Emacs 22.3.2 (i686-pc-linux-gnu) of 2011-05-28 on x60s > > currently fails with the backtrace below. > > Somehwere/somehow Babel ends up calling `member' with the second > argument not being a list. In Emacs22 this triggers an error, but not >

Re: [O] FYI: Org mode testing framework, Emacs 23 and 22

Hi Brian Wightman writes: > On Mon, Oct 24, 2011 at 7:12 AM, Sebastien Vauban > wrote: >> For my information, why do you need to test that 2 suites don't run at the >> same time?  They only write to temp buffers, no?  Can they conflict? > > If they do conflict and only one set of tests should r

Re: [O] [RFC] Standardized code block keywords

Nick Dokos writes: > Eric Schulte wrote: > >> Surprisingly (to me) srcname is the winner here, but luckily I haven't >> yet voted, and although I would have though #+source: would have been >> the winner I like the simplicity of using #+name: for named code blocks >> as well as named data. So I

Re: [O] GNU Emacs crashing on large Orgmode files

Hi Karl Karl Voit writes: > * Marcelo de Moraes Serpa wrote: >> >> Hi list, > > Hi individual! > >> I love org and I think there's nothing like it out there, > > Ack! > >> but I'm considering using Evernote for reference notes, because my >> reference.orgfile has grown too big (4234k + lines).

[O] [patch][babel] Patch to fix regression (commit 53573d6)

Hi Patch to fix regression caused by commit 53573d6 (lisp/ob-shen.el causes isolated tests to fail). See http://martynjago.com:/ Best, Martyn >From 18e67dae6ac7c9ec8bfee9d53358e379b0e1ece1 Mon Sep 17 00:00:00 2001 From: Martyn Jago Date: Fri, 7 Oct 2011 15:37:02 +0100 Subject: [PATCH]

Re: [O] Registration for Worg commit access

Hi Jason Jason Dunsmore writes: > Martyn Jago writes: > >> Hi >> >> Would it be possible for someone to provide we with commit access to >> Worg? > > Hi Martyn, > > Here are the instructions for contributing to Worg: > http://orgmode.org/worg/worg-

[O] Registration for Worg commit access

Hi Would it be possible for someone to provide we with commit access to Worg? I'm adding and updating documentation for various testing activities. I've registered with repo.org.cz and added my key user name: mjago Best, Martyn

Re: [O] [babel] BUG in :session

Hi Sebastien "Sebastien Vauban" writes: > Hi Martyn and Eric, > > Martyn Jago wrote: >> Eric Schulte writes: >>> Martyn Jago writes: >>>> Eric Schulte writes: >>>>> I've just pushed up what will hopefully be a more gener

Re: [O] [babel] BUG in :session

Hi Eric Eric Schulte writes: > Martyn Jago writes: > >> Hi Eric >> >> Eric Schulte writes: >> >>> Martyn Jago writes: >>> >>>> Hi Eric >>>> >>>> Eric Schulte writes: >>>> >>>>

Re: [O] [PATCH] Modifications to enable test script to run with emacs-23 and emacs-22

Hi David David Maus writes: > Hi Eric, > Hi Martyn, > > At Tue, 20 Sep 2011 09:03:27 -0600, > Eric Schulte wrote: >> >> Applied, Thanks! -- Eric > > I noticed that newlines in the commit messages of patches by Martyn > are somehow messed up: > > , > | Modifications to enable test script to r

Re: [O] [babel] BUG in :session

Hi Eric Eric Schulte writes: > Martyn Jago writes: > >> Hi Eric >> >> Eric Schulte writes: >> >>> Hi Martyn, >>> >>> I've just pushed up what will hopefully be a more general solution. >>> Basically, language-specif

  1   2   >