Forum Replies Created
- Posts
Hi Patrick,
Could you clarify whether you searched for “aRefNEQ” before or after making that selection? If possible, please share the steps to reproduce the issue.
It also looks like you have Virtual Space enabled (on the General page of the configuration settings). Is that correct?
Lastly, could you try a fresh install of the latest preview portable version and let me know if you can still reproduce the issue?
Thank you,
You can’t add edit boxes to the dialog right now, but I’ll consider adding this feature in future versions.
The Output Bar doesn’t support clickable lists. To view clickable lines, clear the Output Bar in the Extract Options dialog box. The clickable lines will then appear as a new document in the editor.
If
(?^#_text_c==0)were ignored, the literal “a string” would also be ignored. One fix is to use the regex(?#_text_c==0)"[^/]*?".While we’re on the subject of the
(?#_text_c==n)and(?#_text_c!=n)syntax, are there any known issues with it?I think the Extract option in the Find dialog is what you’re looking for. You can also open Extract Options to fine-tune your settings.
Displaying the actual text can slow down EmEditor, especially when there are many bookmarks and the files are very large. For this reason, the actual text is not shown.
There’s already a similar feature available: the
MsgBoxmethod of thePopupMenuobject:https://www.emeditor.org/en/macro/popupmenu/msgbox.html
Would this work for your needs?
EmEditor v25.3 preview 1 (25.2.901) introduces experimental support for using special keywords in regex highlight strings to set additional conditions.
–
(?#_text_c==n)applies the highlight only if the text at the start of the match is already using color ‘n’.
–(?#_text_c!=n)applies the highlight only if the text at the start of the match is *not* using color ‘n’.Here,
nis an integer representing a specific color, as defined in plugin.h. For example:#define SMART_COLOR_NORMAL 0 #define SMART_COLOR_HILITE_4 17 // ...and so onTo set a condition, one of these keywords must appear at the very beginning of your highlight string.
For instance, instead of just writing
%%.*$, you could use(?#_text_c!=17)%%.*$to highlight lines starting with%%only if they don’t already use the color corresponding ton = 17(SMART_COLOR_HILITE_4).Hope this helps clarify how to use this new feature!
You can clear the “Automatically show the Markdown toolbar” check box on the Markdown page of the Customize dialog box.
I’m aware of this issue. Instead of clicking the “Properties” button, you can just double-click the selected item. The issue will be fixed on the next version.
If
%%always appears at the beginning of a line, you can use:^%%.*$Otherwise, I don’t think there’s a good way to write a regex for this case. I’ll consider adding an option to control how regex is applied in situations like this.
Thank you for bringing this to my attention.
The character count was correct because it included newlines (CR+LF) when the “Always insert newlines when copying multiple selections” option is enabled on the Edit page in Customize. However, I will change this behavior in the next version. The word and line counts will also be fixed in the next version.The previous requirement to select multiple lines before clearing the search range was intentional. However, I will modify this behavior as per your request in the next update.
