n all these brackets as well
>
> --
> View this message in context:
http://lilypond.1069038.n5.nabble.com/Line-numbers-in-editor-window-tp181221p181245.html
> Sent from the User mailing list archive at Nabble.com.
>
I'm very happy to have discovered Frescobaldi as well! I h
As Simon explained with a click on the error message the cursor jumps to
the code ...
But if you still want line numbers you can get it with a mark in an
option field in the view pull down menu.
Am 16.09.2015 19:24, schrieb Simon Albrecht:
On 16.09.2015 18:05, David Kastrup wrote:
Urs Liska
ntext:
http://lilypond.1069038.n5.nabble.com/Line-numbers-in-editor-window-tp181221p181245.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On 16.09.2015 18:05, David Kastrup wrote:
Urs Liska writes:
Am 16.09.2015 um 17:39 schrieb Erich Neuwirth:
When compiling, error messages come with line numbers.
Is there a way of displaying the line numbers in the editor window?
of which editor?
The, debugging would be easier.
Indeed.
Bu
Urs Liska writes:
> Am 16.09.2015 um 17:39 schrieb Erich Neuwirth:
>> When compiling, error messages come with line numbers.
>> Is there a way of displaying the line numbers in the editor window?
>
> of which editor?
>
>> The, debugging would be easier.
>
> Indeed.
> But still easier is having th
Am 16.09.2015 um 17:39 schrieb Erich Neuwirth:
> When compiling, error messages come with line numbers.
> Is there a way of displaying the line numbers in the editor window?
of which editor?
> The, debugging would be easier.
Indeed.
But still easier is having the editor configured to make use
When compiling, error messages come with line numbers.
Is there a way of displaying the line numbers in the editor window?
The, debugging would be easier.
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
lilypond-user mailing li
