word wrap about frescobaldi HOT 11 CLOSED

2.0.4 has View->Line Numbers. You can give it a keyboard shortcut in the settings.

Do you mean automatic word-wrap (i.e. just visually break lines to fit in the window width) or real line wrapping (e.g. wrap text or music at a certain width)?

Visual word wrap has not been implemented yet because it acts strange when the same document is open in multiple views (e.g. a split window or a second main window): when a text window is resized, the line wrapping changes also in the other view on the document.

A real line wrapping feature certainly could be useful but it should be implemented carefully not to mangle scheme code or tweak or override commands.

I'm more in favor of some general reformat command (it's already implemented but it could be made smarter). It would put override commands on one line, break lyric lines in a sensible way, break music lines to have one measure per line, etc). The current 'reformat' implementation just adds linebreaks after { or << and before } or >> when there are linebreaks inside the music fragment, and then runs the indenter.

But indeed to simple format html or latex text (when writing lilypond-book documents) a normal linewrapping feature is needed!

from frescobaldi.

+1 for general reformat command. I've been thinking about clearly defining "style" that would be used - it would be good to have it accepted as general lily code formatting style.
Anyway, automatic word-wrap would be useful regardless of reformatting command.

from frescobaldi.

One more request for visual word-wrap. I don't want to have to scroll horizontally for long lines, and I don't want to have to insert line breaks that relate to my particular screen width.

I've dropped editors for lack of word wrap before—I hope I don't have to drop Frescobaldi for this! :)

from frescobaldi.

Don't want to object to the general request, but there are good reasons to keep line width small in source code like LIlyPond's.

from frescobaldi.

@uliska absolutely. But when i'm working on a small-screen laptop, and i want to see the music in more detail without having to zoom constantly, i'm left with the source view that is only about 50 chars wide :(

from frescobaldi.

Am 08.02.2014 22:55, schrieb Janek Warchoł:

@uliska absolutely. But when i'm working on a small-screen laptop, and i want to see the music instead of having to zoom constantly, the source view is only about 50 chars wide :(

OK, 50 characters is definitely less than a recommended line width.

How would you suggest the word wrap to behave then with respect to
indentation?
I always find it very annoying if word wrap doesn't respect indentation
(i.e. the wrapped line starts at the left edge of the editor area).

from frescobaldi.

@uliska:

there are good reasons to keep line width small in source code like LIlyPond's.

There are, but Lilypond syntax actually makes this difficult or impossible in certain cases involving complex tweak code or large markup blocks. Anyway, this is a red herring. The fact is that any good editor should support visual word wrap; it's even useful where the language syntax does make short lines easy.

It's long been an axiom of UI design that horizontal scrolling of text is awful and to be avoided at all costs, since it breaks context too much.

from frescobaldi.

@uliska:

How would you suggest the word wrap to behave then with respect to
indentation?
I always find it very annoying if word wrap doesn't respect indentation
(i.e. the wrapped line starts at the left edge of the editor area).

I'd prefer that it respect indentation, but any word-wrap would be preferable to none. This should probably ultimately be an Editor Preferences setting.

from frescobaldi.

Lilypond syntax actually makes this difficult or impossible
in certain cases involving complex tweaks or large markup blocks. Anyway,
any good editor should support visual word wrap

I see.
But I tend to write complex tweaks on their own line anyway (plus some indentation). This makes them easier to read and especially works better with version control.

[Still: I don't want to object against word wrap as a new feature}

from frescobaldi.

@uliska:

But I tend to write complex tweaks on their own line anyway (plus some indentation).

I do too, but the tweak syntax is so verbose that I've run across cases where the one line still was wider than my (wide) editing window, and there was no logical place to put a hard line break.

from frescobaldi.

@wbsoft Oh cool. Thanks!

from frescobaldi.