| [wiki editor] line end vs. long wrapped lines [message #490589] |
Fri, 09 October 2009 06:03  |
Eclipse User |
|
|
|
hi folks,
i love the wiki editor, thx for that but this is what drive me nuts lately, and i bet there must be setting for this but i cant seem to find it.
1. long lines are wrapped automatically, good
2. hitting the end key; command: editing text/line end will bring it to the char before the line feed and not the end of the current line as usual.
this is very bothersome when you edit longer paragraphs!!!
plz safe my life and tell me the setting or add it ASAP.
|
|
|
|
|
| Re: [wiki editor] line end vs. long wrapped lines [message #599690 is a reply to message #490589] |
Tue, 13 October 2009 13:30  |
| Eclipse User |
|
|
|
Thomas,
As you observed the end key (or Command-Right Arrow on a Mac) corresponds to the 'Line End' command. This command takes
you to the end of the line as you observed. The line end is determined by the position of the EOL character(s) in the
document. The line-wrap that you're observing in the editor depends on the size of the viewable area in the editor, and
does not correspond to the end of line. I believe that this is how all text editors in Eclipse behave. If you feel
that this is a bug, feel free to file a bug against Eclipse UI. Otherwise feel free to create an enhancement request
for a command that will position the caret at the end of the line as displayed in the source viewer considering line-wrap.
Regards,
David
thomas menzel wrote:
> hi folks,
> i love the wiki editor, thx for that but this is what drive me nuts
> lately, and i bet there must be setting for this but i cant seem to find
> it.
>
> 1. long lines are wrapped automatically, good
> 2. hitting the end key; command: editing text/line end will bring it to
> the char before the line feed and not the end of the current line as usual.
>
> this is very bothersome when you edit longer paragraphs!!!
>
> plz safe my life and tell me the setting or add it ASAP.
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.04291 seconds
Home