Forum Replies Created
- Posts
It’s possible at some point recently, the secondary window was placed on the TV (second monitor) And every time I attempted a Search/Replace the Search Dialog was being sent to the second monitor (even when the TV wasn’t on?) and even though the secondary EmEditor Window was on the current desktop…
Perhaps a sanity-check could be added to the Various EmEditor pop-up dialogs to force them onto the primary desktop – if the Editor-window in question is on the current primary desktop.
Sorry for the run-around, it was only after re-activating Stardock’s WindowFX-5 that I could see the “animation” of the Search dialog appear, do a little dance and then disappear. Prior to re-enabling WindowFX-5 – the search dialog, if it appeared at all before disappearing off the screen, was so brief as to be almost undetectable.
Window #1 (TOP) is the primary (1st) window.
Window #2 (Bottom) is the secondary window.When activating Window#2, pressing Ctrl+F||Ctrl+H opens a dialog (briefly) then it seems to go off the desktop – disappears.
When activating Window#1, pressing Ctrl+F||Ctrl+H opens the Search/Replace dialog.
After opening the Search replace dialog, I click on the 2nd window (bottom), then the Search Dialog – attempt a search.
The search is performed from the primary window – I assume since that is the window that opened the Search/Replace dialog?
Except the search should be performed in the 2nd (bottom) window – as it was the last active window before switching to the search/replace dialog.
Thus as it stands now, am unable to do search/replace from the Search Dialog in secondary windows — aside from using the inline Search-Toolbar.
I don’t use languages other than English, and I use a Dark Theme. You would be able to do this already like this:
1) Save your current Config/Theme to Dark-EN
2) Change the font for the current Config/Theme to your Japanese font of choice. Save the theme to Dark-JA.When you want to switch to an English document, choose the Dark-EN theme. When you want to switch to a Japanese Doc, choose the Dark-Ja theme.
What might be nice though, is the ability to change Themes from the Drop down menu’s directly. E.g.
“ToolsSelect Theme”Another Option, Further. Duplicate a given language’s highlighter and Name it LANGUAGE-NAME-JA, do the customizations as noted above.
Now you can toggle between something like “C” and “C-JA” directly from the “Tools/Select Configuration” menu.
Deipotent says:
The other thing WeBuilder does is to highlight the start and end tag of the current block you are in in a light green colour, and if one of them is missing it will highlight that tag in light red. This is useful as a quick visual indicator that tags are matched.
CodeLobster does this as well. Along with AutoComplete/Suggest for inline css style attributes and html attributes. They are invaluable. Especially since it is difficult to remember all of the “correct” attributes.
I’ve attempted numerous times, unsuccessfully, to setup a custom “brace matching/indentation” (code folding) for HTML, but since there are so many valid closing tags it’s not possible — thus one is limited to code folding only exactingly indented HTML.
The other aspect of tag matching, the tag is not matched when it is “closed” at the wrong depth, and is “mis-matched” when closed inside an open tag.
e.g. Appearance [Cursor NOT inside the div]:
some textmore text
e.g. Appearance [Cursor INSIDE the div]:
some textmore text
While EmEditor can’t necessarily be everything to everyone, this would definitely lessen my need for other Editors.
And code-folding inside matched tags that aren’t necessarily “properly” indented would be awesome — which I mention as it would be a side-effect that could be enabled if EmEditor counted the depth level of tags.
EmEditor Home » EmEditor Help » Dialog Boxes
> button
…
Multiline
Toggles between singleline and multiline of the drop-down list box (this command appears only in the Find dialog box and Replace dialog box).In a Regex string, a n is a newline.
As well as rn e.g. CRLFThe fact that my regex is a “single line string” is irrelevant. It contains multiple n newlines, and if you want it to work as intended —- which is to look on multiple lines for search matches/input, then you need to select “Multiline” from the dialog, as I mentioned previously.
Multiline is a regex option. You need to select it.
My Search regex is a multiline regex (it contains multiple newlines). You need to select “Multiline” from the pop-up menu that is available when you click [>]AH! Sorry :-)
Well given the following input:
34,George,Clooney,123456,LDL,356,mg
34,George,Clooney,123456,HDL,324,ml
34,George,Clooney,123456,VLDL,635,kgIf your file is tab delimited instead of commas, then you will need to replace all commas below with “t”
Step 1:
Search: ^(d+),([A-Za-z]+),([A-Za-z]+),(d+),(.*)
Replace: 1,2,3,4,n5Step 2:
Search: ^(d+,[A-Za-z]+,[A-Za-z]+,d+,)n[A-Z]+,(d+),([a-z]+)n1n[A-Z]+,(d+),([a-z]+)n1n[A-Z]+,(d+),([a-z]+)n
Replace: 12 3,4 5,6 7nFinal Output:
34,George,Clooney,123456,356 mg,324 ml,635 kg
With V11 Beta out now, is there any chance of updating the Highlighter rules to either:
1_) Allow to choose what piece of a regex to Highlight. OR
2A) Allow a Rule to Block any further matches for the string &
2B) Allow a Rule to ALLOW further matches for the string
—> Regardless if one is a regex and one is a simple string.Not sure if it is bad form or not, just bumping a few of my old requests since v11 beta is now out.
The command help/keyboard map shows a list of EmEditor functions and assigned keyboard shortcuts.
It would be helpful if we could sort that list by the non-modifier keys that make up that shortcut.
E.G. instead of:
[Category]___[Command]___[Current Keys]___[Description][Category]_[Command]_[Shortcut]_[Key]_[Description]
File Open Ctrl+O O Opens an existing file.The only change that would be required beyond the additional “Key” Tabstop, would be any commands that are assigned multiple shortcuts should likely appear multiple times in the list.
E.G.[Category]_[Command]_[Shortcut]_[Key]_[Description]
File Close Ctrl+F4 F4 Closes the current file.
File Close Ctrl+W W Closes the current file.Since from the Keyboard map we can double-click on an entry and go right to the change-shortcut option for that command.
With version 11 out, I’d just like to put another Vote in for the possibility of colorized search results — so you can tell from the results themselves when the Search String is contained within the current syntax hilighter’s comment.
The (? syntax is something entirely different.
Example, given the following Text
This is a test sentence
This is a test sentence
of a regex string
of a regex stringTry this regex:
Search: ^(.*)(?|(a test )|(a regex ))(.*)$
Replace: 3With the (?| syntax, there will only be 3 pieces, since the section inside (?|…) isn’t counted as a bracket set.
For the first line:
1: This is_
2: a test_
3: sentenceThe lines will be replaced with “sentence” and “string”.
Now without the (?| syntax, eg:
Search: ^(.*)((a test )|(a regex ))(.*)$ that regex would contain 5 pieces that would be matched with 1 thru 5, and some of them would be empty, depending on the line.For the first line:
1: This is_
2: a test_
3: a test_
4:
5: sentenceThe (? syntax becomes important if you utilize more complex regexes due to the nature of regex to match everything it absolutely can when things like “.*” are present.
Example 2A:
Search: ^(.*)( is a | a regex )?
Replace: 1_That regex will match the whole line, and the replace wont change anything — as the .* consumes the whole line, since the part in (brackets)? is optional, the greedy regex wont see it.
Example 2B:
Search: ^(.*)(?|( is a )|( a regex ))
Replace: 1_This regex will actually remove ” is a ” and ” a regex ” from the lines in question.
A lot of editors don’t even implement the full regex spec, e.g. Notepad2 does a small subset which doesn’t even handle the optional “?” correctly, and certainly doesn’t support the (?| syntax.
Here’s a non-internal solution:
Requires ResizeEnable by Digi Tallis, and AutoHotkey.Ctrl+ RightClick in the newly opened snippets properties dialog. And it will resize the window to nearly full screen.
Size is controlled by the line:
—> MouseClickDrag, Left,,, 1680, 1050, 100, RChange 1680, 1050 to width/height desired.
#SingleInstance, Force
#Persistent
#NoEnv
#MaxHotKeysPerInterval, 100
SetBatchLInes, -1
SetMouseDelay, -1
SetTitleMatchMode, Regex
DetectHiddenWindows, on
#ifWinActive, Properties ahk_class ^#32770$
{
^RButton::
{
parent:=QueryParent(WinActive("A"))
pClass:=WinGetClass(parent)
if( pClass == "EmEditorMainFrame3" )
{
WinMove, 10, 10
WinGetPos, xWin, yWin, wWin, hWin, A
CoordMode, Mouse, Screen
MouseMove, \% wWin + xWin - 2, \% hWin + yWin - 2, 10
Click
Sleep, 750
MouseClickDrag, Left,,, 1680, 1050, 100, R
}
return
}
return
}
WinActiveA( aWin="", winText="", notTitle="", notText="" )
{
return WinActive( (aWin+0 ? "ahk_id " aWin : aWin), winText, notTitle, notText )
}
WinGetClass( aWin="A", winText="", notTitle="", notText="" )
{
WinGetClass, wClass, \% (aWin+0 ? "ahk_id " aWin : aWin), \%winText\%, \%notTitle\%, \%notText\%
return wClass
}
QueryParent(childID, byRef ownerID=FALSE)
{
childID:=(childID + 0 ? childID : WinActive("A"))
retReal:=(ownerID ? TRUE : FALSE)
ownerID:=childID
while((ownerID:=DllCall("GetWindow", "uint", ownerID, "int", 4)) && (parent:=ownerID)) ; && grandParent
continue
return ( retReal ? parent : (parent ? parent : ownerID:=childID))
}
Not as good as an internal solution. And not as good as a custom solution. But a custom solution would entail moving each individual control a set amount (changing x/y coords, and width/height for each control).
You could do it with AHK, and possibly an EMEditor Macro/Script assigned to a hotkey.
Example command:
hh mk:@MSITStore:c:program filesAutoHotkeyAutohotkey.chm::/docs/commands/_AllowSameLineComments.htm
When viewing the helpfile in question, click on the ‘Go’ menu, and find the URL. If all the commands are within the same path, then it would just be a matter of generating the command to have the selected text.
It’s not exactly straight forward though, in my example, the actual command is “#AllowSameLineComments” – but it is stored in the path “_AllowSameLineComments”
Would it be possible with EmEditors internal scripting or macro?
You could redirect HtmlTidy’s Standard Error to a file TidyError.log.
Once the file is reloaded/changed in EmEditor – could you load the TidyError.log into the output bar?I do it so I can see at a glance that there is in fact a space being matched.
Regex strings are hard enough to look at as it is :-)
Functionally it is likely no different, but visually, and for working with them, much easier for me to figure out:
[ ]+ than
+I can’t reproduce what you are claiming in this case.
I’ve tried with both unix-LF and windows-CRLF files.AString
ANotherString
YetAnotherString
EvenMoreStringThis Search: ([[:alnum:]]+)n
Replace: 1,Results in:
AString, ANotherString, YetAnotherString, EvenMoreString
My Test file:
teststring
teststring
teststring
teststring
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32This regex,
: +([[:alnum:];.]+)n
Matches the first 3 ABCDE lines.
This regex,: +([[:alnum:];.]+)$
Matches all 4.
And with this file:teststring
teststring
teststring
teststring
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32This regex:
:[ ]+([[:alnum:];.])+$
Matches all 4 ABCDE’s.
And with this file:
teststring
teststring
teststring
teststring
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32
ABCDE: .abc3;.s32
This regex:
:[ ]+([[:alnum:];.])+n
Matches all 4 ABCDE’s.
I’m confused as to what you are searching for.
Especially since you are using multiple instances of “*”
— Which with regex are rarely necessary, and frequently will mangle your search results.[[:alnum:];.] —> means match *ANYTHING*
You haven’t escaped the period. and it will match any char.
Possibly you meant:
[[:alnum:];.]But then, this: ([[:alnum:];.])*
Means match any alphanumeric plus semi-colon plus a dot any number of times, or not at all. Meaning it will also match empty lines – that only have a carriage return.Possibly, what you meant as your regex:
: ([[:alnum:];.])+n
A way that I have seen it done in other Editors and File Managers is to have the Bar collapse down on the side:
[ ]|=============================
r |
e | Edit Area Here
r |
o |
l |
p |
x |
E |
[ ]|The Explorer word is rotated left 90′, so multiple Bars/Custom bars can be enabled/shown by clicking on the vertical tab.
When considering this, consider allowing new “Display” rules.
E.g. many IDE’s and Editors allow for setting colors for things like:HTML Tag
HTML Unknown Tag
HTML Attribute
HTML Unknown Attribute
HTML Value
HTML String
HTML Other Inside Tag
HTML Comment
HTML Entity
HTML Element TextPHP Default
PHP Start Tag
PHP Comment
PHP Keyword
PHP String
PHP Simple String
PHP Number
PHP Operator
PHP Variable
PHP String Variable
PHP Complex VariableIf you look at the actual .esy syntax files, EmEditor basically does this, but it doesn’t allow you to name the group of words — if it did then in the GUI one could view them like:
+HTML Tag
a
img
...
+ HTML attribute
color
width
....As opposed to a huge list of unrelated/unsorted words.
Then you could likewise define:
Words (and/or a Regex) for those Specifications.
E.g. 1) Words, AND a fall-back Regex that doesn’t match your words(Tags/Attributes).
E.g. 2) Only a Regex.It would just be really really nice, if we didn’t have to try and form a Regex to encapsulate HTML syntax properly
<div class=“begin”>
<?php echo“Some Text Here”;
$testVar='<div class=“inside”>TestVar Text</div>’
?>
<TAG attribute1=“Value” attribute2=“value”>Plain Text
<span class=“test”>Some Text</span></TAG></div>With possibly an option to display PHP strings that contain HTML code with the normal HTML tag/attribute coloring – but allow for a modified background.
I’m still not sure how enabling the “HTML Embedded” under [Highlight(2)] / Special Syntax really works.
How I would think it should work, is allow you to define your HTML rules based on Tag/Attribute definitions, etc.
And to allow CSS highlighters to be triggered:
1) inside the where you can define in-line CSS.
2) inside tags when style is indicated <div style=”width:100px”
Allow your defined PHP syntax highlighters to be triggered:
1) in between php start tags, e.g.Allow your defined Javascript syntax highlighters to be triggered, inside:
<!–
alert(document.forms[0].elements.length);
// –>
