since some time, the lines numbers are missing for the common "used 
before defined" errors.  for instance:

instr 1
  aBla ntrpol a1, a2, 0
endin

returns this error message:

error:  Variable 'a1' used before defined
  from file /home/jh/Desktop/test2.csd (1)
error:  Variable type for a1 could not be determined.
  from file /home/jh/Desktop/test2.csd (1)
Parsing failed to syntax errors

for bigger csd files it would be very helpful to see the line number 
immediately.

thanks -

o you meanlike tis?

STARTING FILE
Creating orchestra
Creating score
rtaudio: pulseaudio module enabled
rtmidi: ALSA Raw MIDI module enabled
error:  Variable 'a1' used before defined
Line 5
  from file def.csd (1)
error:  Variable type for a1 could not be determined.
  from file def.csd (1)
Parsing failed to syntax errors
Stopping on parser failure
cannot compile orchestra
end of score.              overall amps:      0.0
            overall samples out of range:        0
1 errors in performance
Elapsed time at end of performance: real: 0.001s, CPU: 0.001s


Will commit


On Sun, 11 Jun 2017, joachim heintz wrote:

> since some time, the lines numbers are missing for the common "used before 
> defined" errors.  for instance:
>
> instr 1
> aBla ntrpol a1, a2, 0
> endin
>
> returns this error message:
>
> error:  Variable 'a1' used before defined
> from file /home/jh/Desktop/test2.csd (1)
> error:  Variable type for a1 could not be determined.
> from file /home/jh/Desktop/test2.csd (1)
> Parsing failed to syntax errors
>
> for bigger csd files it would be very helpful to see the line number 
> immediately.
>
> thanks -
> 	joachim

yes exactly.  please commit, i will try out.
thanks!
	joachim


On 11/06/17 16:02, jpff wrote:
> o you meanlike tis?
>
> STARTING FILE
> Creating orchestra
> Creating score
> rtaudio: pulseaudio module enabled
> rtmidi: ALSA Raw MIDI module enabled
> error:  Variable 'a1' used before defined
> Line 5
>  from file def.csd (1)
> error:  Variable type for a1 could not be determined.
>  from file def.csd (1)
> Parsing failed to syntax errors
> Stopping on parser failure
> cannot compile orchestra
> end of score.              overall amps:      0.0
>            overall samples out of range:        0
> 1 errors in performance
> Elapsed time at end of performance: real: 0.001s, CPU: 0.001s
>
>
> Will commit
>
>
> On Sun, 11 Jun 2017, joachim heintz wrote:
>
>> since some time, the lines numbers are missing for the common "used
>> before defined" errors.  for instance:
>>
>> instr 1
>> aBla ntrpol a1, a2, 0
>> endin
>>
>> returns this error message:
>>
>> error:  Variable 'a1' used before defined
>> from file /home/jh/Desktop/test2.csd (1)
>> error:  Variable type for a1 could not be determined.
>> from file /home/jh/Desktop/test2.csd (1)
>> Parsing failed to syntax errors
>>
>> for bigger csd files it would be very helpful to see the line number
>> immediately.
>>
>> thanks -
>>     joachim
>>

this works, wonderful.

would it be possible to quote the offending line in addition (as it is 
done for wrong opcode arguments)?
then the error message would be in this case:

Line 5
 >> aBla ntrpol a1, a2, 0
  from file def.csd (1)
error:  Variable type for a1 could not be determined.
  from file def.csd (1)

this would be very helpful, too.

thanks and regards -

	joachim


On 11/06/17 16:07, joachim heintz wrote:
> yes exactly.  please commit, i will try out.
> thanks!
>     joachim
>
>
> On 11/06/17 16:02, jpff wrote:
>> o you meanlike tis?
>>
>> STARTING FILE
>> Creating orchestra
>> Creating score
>> rtaudio: pulseaudio module enabled
>> rtmidi: ALSA Raw MIDI module enabled
>> error:  Variable 'a1' used before defined
>> Line 5
>>  from file def.csd (1)
>> error:  Variable type for a1 could not be determined.
>>  from file def.csd (1)
>> Parsing failed to syntax errors
>> Stopping on parser failure
>> cannot compile orchestra
>> end of score.              overall amps:      0.0
>>            overall samples out of range:        0
>> 1 errors in performance
>> Elapsed time at end of performance: real: 0.001s, CPU: 0.001s
>>
>>
>> Will commit
>>
>>
>> On Sun, 11 Jun 2017, joachim heintz wrote:
>>
>>> since some time, the lines numbers are missing for the common "used
>>> before defined" errors.  for instance:
>>>
>>> instr 1
>>> aBla ntrpol a1, a2, 0
>>> endin
>>>
>>> returns this error message:
>>>
>>> error:  Variable 'a1' used before defined
>>> from file /home/jh/Desktop/test2.csd (1)
>>> error:  Variable type for a1 could not be determined.
>>> from file /home/jh/Desktop/test2.csd (1)
>>> Parsing failed to syntax errors
>>>
>>> for bigger csd files it would be very helpful to see the line number
>>> immediately.
>>>
>>> thanks -
>>>     joachim
>>>
>>

>>>>> "joachim" == joachim heintz  writes:

 joachim> would it be possible to quote the offending line in addition (as it is 
 joachim> done for wrong opcode arguments)?
 joachim> then the error message would be in this case:

 joachim> Line 5
 >>> aBla ntrpol a1, a2, 0
 joachim>   from file def.csd (1)
 joachim> error:  Variable type for a1 could not be determined.
 joachim>   from file def.csd (1)

 joachim> this would be very helpful, too.

 joachim> thanks and regards -

 joachim> 	joachim


i do not think the the text is stored anywhere so this would require a big rewrite

How about adding the following hack in ~/.bashrc as a workaround for
quickly checking what the offending line is?

function cs_debugline { sed -n "$(csound $1 | sed -n 's/Line
\(.*\)/\1/p')"p "$1"; }


On 11/06/17 13:36, joachim heintz wrote:
> this works, wonderful.
>
> would it be possible to quote the offending line in addition (as it is
> done for wrong opcode arguments)?
> then the error message would be in this case:
>
> Line 5
> >> aBla ntrpol a1, a2, 0
>  from file def.csd (1)
> error:  Variable type for a1 could not be determined.
>  from file def.csd (1)
>
> this would be very helpful, too.
>
> thanks and regards -
>
>     joachim
>
>
> On 11/06/17 16:07, joachim heintz wrote:
>> yes exactly.  please commit, i will try out.
>> thanks!
>>     joachim
>>
>>
>> On 11/06/17 16:02, jpff wrote:
>>> o you meanlike tis?
>>>
>>> STARTING FILE
>>> Creating orchestra
>>> Creating score
>>> rtaudio: pulseaudio module enabled
>>> rtmidi: ALSA Raw MIDI module enabled
>>> error:  Variable 'a1' used before defined
>>> Line 5
>>>  from file def.csd (1)
>>> error:  Variable type for a1 could not be determined.
>>>  from file def.csd (1)
>>> Parsing failed to syntax errors
>>> Stopping on parser failure
>>> cannot compile orchestra
>>> end of score.              overall amps:      0.0
>>>            overall samples out of range:        0
>>> 1 errors in performance
>>> Elapsed time at end of performance: real: 0.001s, CPU: 0.001s
>>>
>>>
>>> Will commit
>>>
>>>
>>> On Sun, 11 Jun 2017, joachim heintz wrote:
>>>
>>>> since some time, the lines numbers are missing for the common "used
>>>> before defined" errors.  for instance:
>>>>
>>>> instr 1
>>>> aBla ntrpol a1, a2, 0
>>>> endin
>>>>
>>>> returns this error message:
>>>>
>>>> error:  Variable 'a1' used before defined
>>>> from file /home/jh/Desktop/test2.csd (1)
>>>> error:  Variable type for a1 could not be determined.
>>>> from file /home/jh/Desktop/test2.csd (1)
>>>> Parsing failed to syntax errors
>>>>
>>>> for bigger csd files it would be very helpful to see the line number
>>>> immediately.
>>>>
>>>> thanks -
>>>>     joachim
>>>>
>>>

Yeah, I totally forgot about csound and stderr:

function cs_debugline { sed -n "$(csound $1 2>&1 >/dev/null | sed -n 's/Line \(.*\)/\1/p')"p "$1"; }


On 11/06/17 18:12, Guillermo Senna wrote:
> function cs_debugline { sed -n "$(csound $1 | sed -n 's/Line

ok — then for the current state the line number is a big improvement for 
the users.

for future, i will try to make a list as a suggestion, which error 
messages might be ideal for people learning and using csound, from my 
experience (mainly looking at my students).

best -
	joachim


On 11/06/17 22:16, jpff wrote:
>>>>>> "joachim" == joachim heintz  writes:
>
>  joachim> would it be possible to quote the offending line in addition (as it is
>  joachim> done for wrong opcode arguments)?
>  joachim> then the error message would be in this case:
>
>  joachim> Line 5
>  >>> aBla ntrpol a1, a2, 0
>  joachim>   from file def.csd (1)
>  joachim> error:  Variable type for a1 could not be determined.
>  joachim>   from file def.csd (1)
>
>  joachim> this would be very helpful, too.
>
>  joachim> thanks and regards -
>
>  joachim> 	joachim
>
>
> i do not think the the text is stored anywhere so this would require a big rewrite
>
>
> ==John ffitch