Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Han-Wen Nienhuys
Jan Nieuwenhuizen wrote: Han-Wen Nienhuys writes: columns TAB is set in the user's editor. Several broken editors allow setting TAB to a different value than 8. I can add an "dont-expand-tabs" option. Is that sufficient? I don't understand, then you can have two PDFs with different locat

Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Jan Nieuwenhuizen
Han-Wen Nienhuys writes: >> columns TAB is set in the user's editor. Several broken editors allow >> setting TAB to a different value than 8. > > I can add an "dont-expand-tabs" option. Is that sufficient? I don't understand, then you can have two PDFs with different location encodings? Is that

Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Han-Wen Nienhuys
Jan Nieuwenhuizen wrote: Han-Wen Nienhuys writes: Disagree. We're talking about _column_ numbers, not character numbers. Maybe that's a bad idea, because lilypond cannot know at how many columns TAB is set in the user's editor. Several broken editors allow setting TAB to a different value

Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Bertalan Fodor
We're talking about column numbers, but how many columns does one TAB character in the source make? Eight? Why eight and not four or two? Now when lilypond finds a TAB, it assumes 8 columns and hard-codes it into the PDF. That is not correct, because all editors' TAB width can be set by users.

Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Jan Nieuwenhuizen
Han-Wen Nienhuys writes: > Disagree. We're talking about _column_ numbers, not character numbers. Maybe that's a bad idea, because lilypond cannot know at how many columns TAB is set in the user's editor. Several broken editors allow setting TAB to a different value than 8. > You could rightly

Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Han-Wen Nienhuys
Bertalan Fodor wrote: Sorry, I meant 4:2, if we the first character is indexed 1. Bert Disagree. We're talking about _column_ numbers, not character numbers. You could rightly file a related bugreport for ClickEdit.app, though, because it doesn't do tab conversion. -- Han-Wen Nienhuys -

Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Bertalan Fodor
Sorry, I meant 4:2, if we the first character is indexed 1. Bert c2 % BEGINS WITH TAB, reported as position 4:8 how should it be reported? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilyp

Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Bertalan Fodor
4:1 c2 % BEGINS WITH TAB, reported as position 4:8 how should it be reported? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: 2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Han-Wen Nienhuys
Bertalan Fodor wrote: %BUG: Point-and-click positions count one TAB character as 8 SPACE character. Because of this, editors are called with wrong horizontal position. \version "2.5.27" \relative { c2 % BEGINS WITH TAB, reported as position 4:8 how should it be reported? d } __

2.5.27 point-and-click bug (IMHO critical)

2005-06-06 Thread Bertalan Fodor
%BUG: Point-and-click positions count one TAB character as 8 SPACE character. Because of this, editors are called with wrong horizontal position. \version "2.5.27" \relative { c2 % BEGINS WITH TAB, reported as position 4:8 d } ___