Re: Question about 'back quote' in scheme markups within Documentation examples

2010-06-10 Thread James Lowe
Hello, On 09/06/2010 17:00, Carl Sorensen wrote: ... The back-quote means that any expression in the back-quoted list that is preceded by a comma will be evaluated. The regular single quote means that nothing in the list will be evaluated; the list will just be assembled. Thanks Carl, my quer

Re: Question about 'back quote' in scheme markups within Documentation examples

2010-06-09 Thread David Kastrup
Carl Sorensen writes: > On 6/9/10 7:34 AM, "James Lowe" wrote: > >> Hello, >> >> Going on from the 'curly quotes' problem that was resolved a couple of >> days back in our documentation, I noticed in the NR while scanning >> through another 'odd' single quote mark after the hash (#) character.

Re: Question about 'back quote' in scheme markups within Documentation examples

2010-06-09 Thread Carl Sorensen
On 6/9/10 7:34 AM, "James Lowe" wrote: > Hello, > > Going on from the 'curly quotes' problem that was resolved a couple of > days back in our documentation, I noticed in the NR while scanning > through another 'odd' single quote mark after the hash (#) character. > > \override #`(direction .

Re: Question about 'back quote' in scheme markups within Documentation examples

2010-06-09 Thread James Lowe
Thanks Jay. Jay Anderson wrote: On Wed, Jun 9, 2010 at 6:34 AM, James Lowe wrote: I wondered if anyone can tell me if this is a mistake or what the significance of the back-quote is vs the standard singe quote? It is intentional. Look up scheme's quasiquote and unquote functions. -Jay

Re: Question about 'back quote' in scheme markups within Documentation examples

2010-06-09 Thread -Eluze
pkx166h wrote: > > Hello, > > Going on from the 'curly quotes' problem that was resolved a couple of > days back in our documentation, I noticed in the NR while scanning > through another 'odd' single quote mark after the hash (#) character. > > \override #`(direction . ,UP) > > instead of >

Re: Question about 'back quote' in scheme markups within Documentation examples

2010-06-09 Thread Jay Anderson
On Wed, Jun 9, 2010 at 6:34 AM, James Lowe wrote: > I wondered if anyone can tell me if this is a mistake or what the > significance of the back-quote is vs the standard singe quote? It is intentional. Look up scheme's quasiquote and unquote functions. -Jay _

Question about 'back quote' in scheme markups within Documentation examples

2010-06-09 Thread James Lowe
Hello, Going on from the 'curly quotes' problem that was resolved a couple of days back in our documentation, I noticed in the NR while scanning through another 'odd' single quote mark after the hash (#) character. \override #`(direction . ,UP) instead of \override #'(direction . ,UP) See att