Re: [O] make doc fails on current head

2012-06-01 Thread Jonathan Leech-Pepin
I can confirm it's fixed And thanks for the answer, hadn't realized you could use @# and $# for references. On Fri, Jun 1, 2012 at 8:56 AM, Bastien wrote: > Nick Dokos writes: > >> Bastien wrote: >> >> >>> So what does @@#$2 really means?  Does the first "@" stand for "This is >>> a field coor

Re: [O] make doc fails on current head

2012-06-01 Thread Bastien
Nick Dokos writes: > Bastien wrote: > > >> So what does @@#$2 really means? Does the first "@" stand for "This is >> a field coordinate" and the rest for the coordinates range itself? > > @# is the current row number, so @@#$2 is a reference to the current row, > second column. Got it, thanks

Re: [O] make doc fails on current head

2012-06-01 Thread Nick Dokos
Bastien wrote: > So what does @@#$2 really means? Does the first "@" stand for "This is > a field coordinate" and the rest for the coordinates range itself? > @# is the current row number, so @@#$2 is a reference to the current row, second column. Michael has a couple of nontrivial examples (

Re: [O] make doc fails on current head

2012-06-01 Thread Michael Brand
Hi Bastien On Fri, Jun 1, 2012 at 9:48 AM, Bastien wrote: > So what does @@#$2 really means?  Does the first "@" stand for "This is > a field coordinate" yes > and the rest for the coordinates range itself? it is not a range, but as "@# and $# can be used to get the row or column number of the

Re: [O] make doc fails on current head

2012-06-01 Thread Bastien
Hi Jonathan, Jonathan Leech-Pepin writes: > Under the current git head (4144c55) I get the following error when > trying to run =make doc=. Fixed, thanks for reporting this. -- Bastien

Re: [O] make doc fails on current head

2012-06-01 Thread Bastien
Hi Michael, I just reverted my commit, thanks. Michael Brand writes: > but I can confirm that it should really compile to @@#$2 and not to > @#$2 or something else. So what does @@#$2 really means? Does the first "@" stand for "This is a field coordinate" and the rest for the coordinates rang

Re: [O] make doc fails on current head

2012-05-31 Thread Michael Brand
Hi Nick On Thu, May 31, 2012 at 11:58 PM, Nick Dokos wrote: > Just to make sure, you are saying that commit > 4144c55ec78a4fdf246c64a4130f807eec50a913 should be reverted - the four @ > signs in org.texi produce two @ signs in the produced info file, and > that's the way the info file should be. D

Re: [O] make doc fails on current head

2012-05-31 Thread Nick Dokos
Michael Brand wrote: > Hi Bastien > > On Thu, May 31, 2012 at 5:21 PM, Jonathan Leech-Pepin > wrote: > > If I revert to =git checkout HEAD~1= make doc succeeds as it had previously. > > Funny that just out of curiosity and without any suspicion I came > across this regression of one of the org

Re: [O] make doc fails on current head

2012-05-31 Thread Michael Brand
Hi Bastien On Thu, May 31, 2012 at 5:21 PM, Jonathan Leech-Pepin wrote: > If I revert to =git checkout HEAD~1= make doc succeeds as it had previously. Funny that just out of curiosity and without any suspicion I came across this regression of one of the org.texi lines written by me. The intentio

[O] make doc fails on current head

2012-05-31 Thread Jonathan Leech-Pepin
Hello, Under the current git head (4144c55) I get the following error when trying to run =make doc=. #+begin_src sh ~/build/org-mode $ make doc /usr/bin/make -C doc info make[1]: Entering directory `/cygdrive/d/Users/jleechpe/build/org-mode/doc' makeinfo --no-split org.texi -o org org.t