emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Bugs in lisp/ob-lilypond.el
@ 2011-11-19 15:22 Torsten Anders
  2011-11-19 15:23 ` Torsten Anders
  0 siblings, 1 reply; 4+ messages in thread
From: Torsten Anders @ 2011-11-19 15:22 UTC (permalink / raw)
  To: emacs-orgmode

Dear Martyn Jago, dear all,

I just pulled the latest version of Org mode and noticed a few bugs in the Lilypond support of Org babel that have not been there in the previous version (so far I was still using version 7.6).

In general, there seems to be problems in parsing the line that starts #+begin_src lilypond. More specifically, 

 - Global :noweb settings are now ignored
 - Any settings after the setting :file will be added to output file name!
 - Settings after :noweb yes cause trouble (disable this setting)

Again, thanks for lisp/ob-lilypond.el in the first place.

Best wishes,
Torsten

--
Dr Torsten Anders
Course Leader, Music Technology
University of Bedfordshire
Park Square, Room A315
torsten.anders@beds.ac.uk
http://strasheela.sourceforge.net
http://www.torsten-anders.de

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Bugs in lisp/ob-lilypond.el
  2011-11-19 15:22 Bugs in lisp/ob-lilypond.el Torsten Anders
@ 2011-11-19 15:23 ` Torsten Anders
  2011-11-19 21:10   ` Martyn Jago
  0 siblings, 1 reply; 4+ messages in thread
From: Torsten Anders @ 2011-11-19 15:23 UTC (permalink / raw)
  To: emacs-orgmode

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 Org mode and noticed a few bugs in the Lilypond support of Org babel that have not been there in the previous version (so far I was still using version 7.6).
> 
> In general, there seems to be problems in parsing the line that starts #+begin_src lilypond. More specifically, 
> 
> - Global :noweb settings are now ignored
> - Any settings after the setting :file will be added to output file name!
> - Settings after :noweb yes cause trouble (disable this setting)
> 
> Again, thanks for lisp/ob-lilypond.el in the first place.
> 
> Best wishes,
> Torsten
> 
> --
> Dr Torsten Anders
> Course Leader, Music Technology
> University of Bedfordshire
> Park Square, Room A315
> torsten.anders@beds.ac.uk
> http://strasheela.sourceforge.net
> http://www.torsten-anders.de
> 
> 
> 
> 
> 
> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Bugs in lisp/ob-lilypond.el
  2011-11-19 15:23 ` Torsten Anders
@ 2011-11-19 21:10   ` Martyn Jago
  2011-11-21 22:44     ` Martyn Jago
  0 siblings, 1 reply; 4+ messages in thread
From: Martyn Jago @ 2011-11-19 21:10 UTC (permalink / raw)
  To: emacs-orgmode

Hi Torston

Torsten Anders <torsten.anders@beds.ac.uk> 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 Org mode and noticed a few bugs
>> in the Lilypond support of Org babel that have not been there in the
>> previous version (so far I was still using version 7.6).
>> 
>> In general, there seems to be problems in parsing the line that starts #+begin_src lilypond. More specifically, 
>> 
>> - Global :noweb settings are now ignored
>> - Any settings after the setting :file will be added to output file name!
>> - Settings after :noweb yes cause trouble (disable this setting)
>> 

Thanks for the heads-up Torsten - there have been many changes to the
bare-metal Org as you probably are aware. Your observations will come in
very useful to sort out the transition to the new improved order (which
I am totally in favor of by the way), and the details you provide will
prove very useful.

Certainly consider checking out a `less hot' release to get working
again ( i.e. git checkout release_7.7 ). In the mean-time I will work on
compatibility (tomorrow hopefully) - and better regression tests.

Great to hear you're making use of ob-lilypond by the way!

Best, Martyn

>> Again, thanks for lisp/ob-lilypond.el in the first place.
>> 
>> Best wishes,
>> Torsten
>> 
>> --
>> Dr Torsten Anders
>> Course Leader, Music Technology
>> University of Bedfordshire
>> Park Square, Room A315
>> torsten.anders@beds.ac.uk
>> http://strasheela.sourceforge.net
>> http://www.torsten-anders.de
>> 
>> 
>> 
>> 
>> 
>> 
>> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Bugs in lisp/ob-lilypond.el
  2011-11-19 21:10   ` Martyn Jago
@ 2011-11-21 22:44     ` Martyn Jago
  0 siblings, 0 replies; 4+ messages in thread
From: Martyn Jago @ 2011-11-21 22:44 UTC (permalink / raw)
  To: emacs-orgmode

Martyn Jago <martyn.jago@btinternet.com> writes:
Hi Torsten
 
> Hi Torston
>
> Torsten Anders <torsten.anders@beds.ac.uk> 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 Org mode and noticed a few bugs
>>> in the Lilypond support of Org babel that have not been there in the
>>> previous version (so far I was still using version 7.6).
>>> 
>>> In general, there seems to be problems in parsing the line that starts #+begin_src lilypond. More specifically, 
>>> 
>>> - Global :noweb settings are now ignored
>>> - Any settings after the setting :file will be added to output file name!
>>> - Settings after :noweb yes cause trouble (disable this setting)
>>> 
>
> Thanks for the heads-up Torsten - there have been many changes to the
> bare-metal Org as you probably are aware. Your observations will come in
> very useful to sort out the transition to the new improved order (which
> I am totally in favor of by the way), and the details you provide will
> prove very useful.
>
> Certainly consider checking out a `less hot' release to get working
> again ( i.e. git checkout release_7.7 ). In the mean-time I will work on
> compatibility (tomorrow hopefully) - and better regression tests.
>
> Great to hear you're making use of ob-lilypond by the way!
>
> Best, Martyn
>
>>> Again, thanks for lisp/ob-lilypond.el in the first place.

(Apologies for miss-spelling your name previously).

I'm not seeing this. I've updated my examples to embrace the standard
source block syntax, and everything seems to be working for me - which
probably means I haven't considered your use-case. 

I've also moved my ob-lilypond documentation to Worg (but appear to have
broken the Worg build mechanism, so that is little help here), but it
would be useful to know if the examples at
http://github.com/mjago/ob-lilypond/examples work for you.

Some more detail would be useful - could you provide:
 -  a broken sample
 - Emacs version 
 - Lilypond version? 

Also are you using arrange-mode (C-h v ly-arrange-mode . Nil is no).

Regarding the `standard source block syntax', ensure that any #+srcname
or #+source commands are replaced with #+name, and update to the very
latest Org if you leave space in a `:var something = something-else'
assignment as I tend to do.

Best, Martyn
 
>>> 
>>> Best wishes,
>>> Torsten
>>> 
>>> --
>>> Dr Torsten Anders
>>> Course Leader, Music Technology
>>> University of Bedfordshire
>>> Park Square, Room A315
>>> torsten.anders@beds.ac.uk
>>> http://strasheela.sourceforge.net
>>> http://www.torsten-anders.de
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-11-21 22:45 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-11-19 15:22 Bugs in lisp/ob-lilypond.el Torsten Anders
2011-11-19 15:23 ` Torsten Anders
2011-11-19 21:10   ` Martyn Jago
2011-11-21 22:44     ` Martyn Jago

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).