Hello,

There are few features that I would like to see in the Lazarus editor:

1. Multiple spliting (and close the split) the editor to horizontal and vertical views
2. VIM keyboard support
3. Ability to have a way to fold code by using comments with special chars (like (* {{{ *) (* }}} ) that VIM allows)
4. Multi linguistal spell checkers for strings and comments
5. Color code with errors with special underline or some color that the user can select that will help to locate where the problem is.
6. Ability to keep the string mark (that added to 0.9.27) as permanent with a toggle of a menu item/key/toolbar
7. Inline help for a command/reserve word that the mouse cursor/keyboard caret are under that word (not instead of the tooltip).
8. When pressing on CTRL above a file/variable/type etc.. that we are trying to load, it will place a tooltip telling what is going to be opened (the file + the line number)

What do you think on this features ? Should I add them to mantis as a wishlist ?

Thanks,

Ido

If you talk about the highlight of the current-word-under-caret: try ALT-M or configure your keyboard, it's in the section with the selection-commands

when Martin implement this it will look as {$REGION 'region name'}{$ENDREGION} or similar

Add them to the wiki page with ideas and explain them there more detailed: http://wiki.lazarus.freepascal.org/Feature_Ideas

Best regards,
Paul Ishenin.

When you have written a patch to implement the features, you can add them to Mantis.

Vincent

There are few features that I would like to see in the Lazarus editor: 1. Multiple spliting (and close the split) the editor to horizontal and vertical views

Better: multiple edit windows, as Delphi has.

2. VIM keyboard support 3. Ability to have a way to fold code by using comments with special chars (like (* {{{ *) (* }}} ) that VIM allows)

When shall such comments be evaluated?

4. Multi linguistal spell checkers for strings and comments

Only on demand.

5. Color code with errors with special underline or some color that the user can select that will help to locate where the problem is.

Only if it doesn't slow down the editor.

What?

Currently I only have three wishes:

- Multiple edit windows.
- Make the editor faster.
- More help texts.

DoDi

That can work, the thing is, that I really hate jamping using bookmarks, and I like to see things in front of me to work better. Duplicate tabs like with Delphi does not solve it, however it can be done, if you are capable in doing what the split does (update all fo the editors with the same content of the file). I tried to do it a while back, but I wasn't able to achive what I wanted to do.

On the wiki page, I've placed a better way (chars) to do it.

> 4. Multi linguistal spell checkers for strings and comments Only on demand.

You can install/activate it on demand if you wish, but such a feature can be helpful imho.

CodeTools already does this, I mean, evaluate the code, but it requires to communicate with the editor to paint such data properly.

On 0.9.27, if you activate a new feature, and you stand on a string, it marks all of the matching strings in the same file. It can be very helpful if I could fixate such string when I'm looking at the code and moving to see where the string in my context appears without the need to use search.

Ido

It also works with the block selection.

And they key to toggle it is Alt-M (configurable in the options)

more options under "Automatic Features" in the option dialog

I work better when I can place independent windows across the entire desktop, including multiple monitors. Splitting a window is not a solution.

DoDi

I agree, multiple windows with code is way better than split panes. When debugging code (whether mine or others), I have had occasion to use 3 or 4 windows of the same file for reference - one may be showing an enumeration, a couple showing related functions and then the last is the one I actually move about and type in. I've found debugging without this in Laz to be more cumbersome.

Alas, I've not delved into the code to look at ways to solve it, and it would require some time to be able to assess what contribution I could make, by which time those who are more familiar with the code will probably have sorted it!

[I'm not using that as a cop out for not contributing! I'm close to putting up a patch to solve an LCL issue :-)]

DSP