AutoHotkey Community

You are welcome.

The solution needs a more profound action. As the documentation says: "The color schemes have no effect on the syntax highlighting feature. To define or redefine the syntax highlighting for a type of file, edit the Coloration.hes file and follow instructions in the header."

To colorize parenthesis and other delimiters of an AHK file, open the Coloration.hes file, go to the line number 118 and change the value 0x01FFFFFF for the color of your choice. Remember that the HiEdit color format is #BBGGRR and not #RRGGBB.

To see the final effect, it is sufficient to disable and re-enable syntax highlighting through the View menu.

Regards.

_________________
Normand Lamoureux

New version available.
See the first post for the details.
Release notes are at the end of the first post.

_________________
Normand Lamoureux

Sympa

Tu pourrai aussi inclure le logiciel d'auto complétion que tu avais fais, non ? Il m'avait beaucoup aidé à l'époque ou j'ai commencé le "scripting" avec AHK, au lieu de passer par l'édition du fichier de remplacement.

enfin je présume que c'est toi : http://normandlamoureux.com/

Sinon il a été poster un super éditeur qui est trop vite tombé au oubliette:
http://www.autohotkey.com/forum/viewtopic.php?t=52583
C'est sans prétention, c'est juste si ça peut t'aider si tu veux pousser ton editeur plus loin.

Bref te voila des encouragements en français

This is a pretty nice editor. Congratulations for your good work!

In fact, this is the smallest and ONLY free editor I know that supports Lookahead (?=...), (?!...) and Lookbehind (?<=...), (?<!...) zero-width assertions based find and replace, which, I believe, is the most important and useful feature of PCRE. In fact, very few editors support the Lookahead and Lookbehind zero-width assertions. I know only of Editpad Pro, which supports it in the best way, and also UltraEdit, EmEditor and AptEdit, but they are not free.

Other editors, though they claim to "support" regular expression based find and replace, do not support lookahead and lookbehind. Even the integrated AHK editor SciTE does not support find and replace with Lookahead and Lookbehind feature, which is sort of ironical since AHK fully supports PCRE. In fact, none of the Scintilla based editors, eg, Notepad++ can do it at present.

If I may suggest, the following additional features will make this editor better:
- drag and drop support for opening files
- "Mark All" in find dialog box (like SciTe editor)
- automatic word wrapping
- for me, the Vic window flickers when resizing, a very minor issue

I think, though, that support for some of these features can be added only by the developer of HiEdit control.

If anyone knows of any other editor that fully supports PCRE based find and replace, please let me know.

I confirm that visuals are fixed now. The redraw flicker happens because of "r" flag in attach. "r2" flag will make it disappear but due to some reason HiEditor tab area doesn't get redrawn correctly.

I can think only of one last solution to completely enimilate flicker altho I don't see entire this thing as a problem rly. You could use OnAttach event handler to redraw entire window 100ms after resizing is finished. Thats what r2 does, but it does only for the HiEdit control.

BTW, all suggestions of arsan can be done except word wrapping.

_________________

Nice work I particularly like the regex search ability.

Couple of observations and things that I'd like to see:

1) The right click context menu opens at some random fixed offset from the current mouse position. I've tried on two different machines and I get the same behavior.

2) I use SciTE and one feature that I really like with that editor is the F5 key (Tools/Run).

3) I would like to be able to drop an .ahk file from my file manager onto the editor and begin work rather than having to navigate though the editor's own File/Open menuing.

4) One of the most common things that I do is "undo." It would be nice to have a menu bar with undo/redo (and a few other common actions).

5) Why is "Font" called "Police?"

@Zaelia
Bonne idée! Ce sera effectivement plus convivial ainsi. Merci pour la suggestion et les mots d'encouragement, Zaelia.

@arsan
The next version will supports drag and drop. I think that there are no fastest way to work in most situations. For the second suggestion, I am not sure to see how such a feature could be more useful than simply use F2 or F3 to reach the next or the previous occurrence.

Thanks for your good words and suggestions, arsan. I was very happy to read your remarks about the Find/Replace based on regular expressions. Maybe, this is the most original feature offered by Vic. The second, IMHO, is what we can do to work very quickly in HTML. Especially with the Tab key (see the documentation for details).

@majkinetor
Thanks for your confirmation for the visual fix and for your explanations about the flicker.

_________________
Normand Lamoureux

@gargoyle888

Thanks a lot. Today, you are the second to pointed out the Vic's regex possibilities and I really like it!

I am not able to reproduce the bug for the moment since I don't have mouse (all works well with my touch pad), but I will try to fix it for the next version.

Sorry, I am not sure that I want to implement such a feature for the moment.

The next version will supports drag and drop. Because in most situations, there are effectively no fastest way to open files.

For the moment, I don't planned to add a tool bar. BTW, I am not sure to see how to click on a tool bar can be fastest and more useful than simply use the standard commands Ctrl+Z to undo and Ctrl+Y to redo.

It is a mistranslation. It will be fixed in next version. Thanks to have reported that.

_________________
Normand Lamoureux

Please allow me to make myself clear. If you are perfectly sure about the text to find/replace, it is of course logical to simply use F2 or F3 to reach the next or the previous occurrence. However, if the text you want to operate upon is a regular expression and occurs multiple times in your document, you need to be careful. We all know regular expressions can be tricky. If you could have a broad view and can see all the text that match the regex that you've constructed, it really helps to decide about the validity of your regex construct. And many times regex construction is a job that requires multiple steps and attempts before you get it just right.

"Mark all" in the find dialog box will help for exactly this purpose.

To make my point clearer, please checkout the following screenshot of Editpad Pro showing all text matching the regex construct highlighted (similar to "Mark all", actually even better since it shows exact matches and not merely line bookmarks like SciTe).
http://www.regular-expressions.info/editpadpro.html

It really helps to make sure of the validity of your regex construct if you can see all the matching text this way. By the way, I'm not trying to promote a third party shareware product. I've mentioned it just to help make my point clearer.

@asan
Thanks for the precisions.

I forgot myself to say that if the text you search for is reached by a regular expression, then F3 will use this regular expression to reach the next occurrence (and F2 will use the same regular expression to reach the previous occurrence).

In each case, F2 and F3 just highlights the match if there is one. To replace an highlighted match by the replacing text, the user has to press F4.

For example, suppose I want to find all two digits occurrences in the expression "2010-01-17", suppose the last replacing text I use in the Find and replace dialog box is "16", and suppose my cursor is at the beginning of the text. I will proceed as following:

1. Press Ctrl+F to open the Find dialog box.
2. Type \d\d in the edit area (\d{2} is also OK).
3. Press Alt+X to check the Regular expression option.
4. Press Esc to destroy the Find dialog box (optional step).
5. Press F3 repeatedly (or Next button, if the Find dialog box still open). By doing so, I will get the following results, successively:

2010-01-17
2010-01-17
2010-01-17
2010-01-17
2010-01-17

At this point, if I press F4, I will finally get:

2010-01-16

Of course, the same behavior happens with a more complex regular expression and a longer text to search in.

At first sight, for the purpose we are talking about, Vic does the same thing as EditPad Pro except that it does it successively instead of simultaneously.

_________________
Normand Lamoureux

Well, I've already explored the regex handling capability of Vic in almost every way - and yes, I was talking about simultaneous highlight, which is a rare feature. Successive is very basic.

Actually, I try to regularly explore the regex handling capability of all the prominent editors found on the internet, shareware or freeware. And Vic compares very favorably among all in this respect - it's in top five! I've already named the other four in a previous post.

I hope you carry on with your good work of improving Vic. Best wishes from me.

A few corrections easy to implement:

- View -> Colors and View -> Language in the menu have the same shortcut key (Ctrl + L)

- the default escape character of AHK, ie, accent/backtick (`) is invisible in the 2nd color set. Color of accent must be changed from black to something else.

The first shortcut should be Ctrl+E. The second is Ctrl+L. This will be corrected in the next version. Thanks to have reported that.

You are right. It is an old bug related to HiEdit control itself. So, it's in HiEdit developer's hands. For the moment, there is no other solution than to choose a background that contrasts with black.

BTW, switching from one color setting to the other does not give always good results. In the next version, each color set will be related to its own syntactic coloration file. In this manner, we can have well contrasted colors when we are in black on white, and a different set of well contrasted colors when we switch to white on black.

_________________
Normand Lamoureux

As majkinetor said in the linked topic, that was a really great observation.

In the long list, I found only two characters available in the ordinary keyboard that are reported to stay black no matter what the color scheme. They are ~ and ` found on the same keyboard button. But our non English using friends will find many more such problem characters.

But the characters ~ and ` are nicely visible in AHK code comments in the 2nd color set with black background.

I think, therefore, that there must be a way to make these two characters visible by modifying the syntax coloring scheme.

Mhm, I was fast to say, that Mark All could be done in HiEdit. You can find all marks but I can't think of solution to highlight them. That would require some of the RichEdit bg/fg coloring capabilities which are not present in HiEdit or at least ability to do multipart selection that is so rare among editors.

It could be done as a coloring of a statusbar or as a window with list of all matches so that you can click on them to jump.

_________________