Forum Replies Created
- AuthorPosts
Yutaka Emura
KeymasterHello,
We are fixing the Issue 1, 2, and 3 on the next beta (v17.7.93).
I would like to clarify your questions.
As for Issue 4, I see the status bar shows correctly. For instance, if the total number of lines is 10, and only a word is selected, the status bar shows “1/10 lines”. Can you explain more details?
As for Issue 5, can you explain which page you are talking about, and how we should correct the page?
Thanks,
Yutaka Emura
KeymasterHello,
We fixed the Issue B and Issue 2-2-2 on the next beta (v17.7.93).
As for Issue A, the larger the dictionary is, the slower the speed becomes. In order to reproduce the issue, can you please let me know the dictionary you use (and its size)?
Thanks,Yutaka Emura
KeymasterI looked at both Boost.Regex and Onigmo syntax specs, but I couldn’t find information regarding the maximum number you can specify in {n,m}. However, EmEditor has the limit of 10,000 you can specify in the “Additional Lines to Search for Regular Expressions” text box. Please note that the larger you specify, the slower EmEditor becomes.
Yutaka Emura
KeymasterWe are fixing that issue on the next version (v17.7.93). Thanks!
Yutaka Emura
KeymasterHello,
I would like to clarify your question in order to help you.
Is the “Cat1…” line always immediately above the “Dog1…” line?
If so, set the Use Regualr Expression option, and replace(Cat.*?Cat2.*?)\n(Dog1.*?Dog2.*?)\n
with
\2\1\n
If not, please figure out the maximum number of lines that exist between the “Cat1…” line and the “Dog1…” line. If it is 10 lines, you can replace:
(Cat.*?Cat2.*?)\n{1,10}(Dog1.*?Dog2.*?)\n
with
\2\1\n
and also go to the Advanced button in the Replace dialog box, and enter “10” to the “Additional Lines to Search for Regular Expressions” text box.
I hope this helps.
Yutaka Emura
KeymasterOn the next beta (v17.7.92), we are adding the Never and Keep Original Text when Completes option to the Match Case drop-down list box in the Matching Criteria page of the Word Complete Properties. Thanks,
Yutaka Emura
KeymasterThanks for clarification. This issue will be fixed on the next beta.
May 27, 2018 at 11:32 am in reply to: "Filter in the Large File Controller custom bar" problems #23270Yutaka Emura
KeymasterThanks for your email. The issue will be fixed on the next beta.
Yutaka Emura
KeymasterWe fixed the Issue 2-2 on the next beta.
Thanks,Yutaka Emura
KeymasterIssue 1: We changed the behavior of Line Indent-related commands par your comment on the next beta. This change also applies to Tab/Shift+Tab commands. Please let us know if anyone believes this change should be an option.
Issue 2: We fixed this issue on the next beta.
Thanks,
Yutaka Emura
KeymasterThis issue will be addressed on the next beta. Thanks!
Yutaka Emura
KeymasterHello,
I would like to clarify your question.
What is the Application key? Is it the Alt key?
How did you assign your key?
Also, how did you assign Active String (“stings enclosed by double-quotation marks” – “Right Clicked”)?
Is “Active String” a path to a macro file? For instance, is it actually something like “C:\test\test.jsee”?
Thank you,Yutaka Emura
KeymasterThis issue will be fixed on the next beta. Thank you!
May 24, 2018 at 8:02 am in reply to: "Filter in the Large File Controller custom bar" problems #23247Yutaka Emura
KeymasterHello sky,
Does EmEditor display the same dialog box even if you open the entire file (or without Large File Controller)?
If the dialog box appears only when you specify a filter, then this might be a bug. In this case, would you please send me a sample file so that we can reproduce the issue?
If the dialog box appears both when you open the entire file and when you specify a filter, this is an intentional behavior, and cancelling the dialog box will close the file.
Thanks,
Yutaka Emura
KeymasterVersion 17.7.91 will fix the Issue 3-1 and 3-2, 4 and 5.
We will try to optimize for scrolling speed in the future.
Thanks,Yutaka Emura
KeymasterIssue 1 is actually an intentional behavior. Users can be distracted if red wiggly line appears while typing. However, the next version will show red wiggly line if the cursor moves from the bottom position to another position.
Issue 2: this will be fixed on v17.7.91.
Issue 3: I am not sure exactly what this means. Type “Capitl”, and do you want EmEditor to show “capital” instead?
Yutaka Emura
KeymasterYou can change or define a new delimiter in the CSV page of the Customize dialog box. Additionally, if you want EmEditor to detect CSV automatically, you can go to File page of configuration properties – “CSV files to detect” list box.
Yutaka Emura
KeymasterOn the next beta version (v17.7.91), we added the Use DirectWrite command, which can be accessible from the arrow button on the right side of the Fonts button on the toolbar.
Thanks,Yutaka Emura
KeymasterWe’ve changed the behavior. On the next beta version (v17.7.91), double-clicking a single space/tab will actually select that space/tab only.
Thanks,Yutaka Emura
KeymasterAs for Issue 1, the following macro can toggle the Directwrite option.
b = editor.GetProfileInt( eeRegCommon, "", "UseDirectWrite", 0 ); editor.WriteProfileInt( eeRegCommon, "", "UseDirectWrite", b ? 0 : 1 ); editor.RefreshCommonSettings();
We will also consider adding the command for this.
As for Issue 6, yes, the triangle node image is expected.
We will look into the other issues.
Thanks,
Yutaka Emura
KeymasterWe are fixing the first issue.
The Adjust Separator Positions (Visible Lines Only) command should adjust separator positions only on filtered text.
Thanks,May 22, 2018 at 3:36 pm in reply to: Using "Increase Line Indent" command when there's no selection causes crash #23219Yutaka Emura
KeymasterWe are fixing the crash problem.
The fact is both “Ignore” and “crash” buttons will crash anyway. The next version will include only “Crash” button when there is no choice. In some cases, “Ignore” will work during a file opening.
Thanks,Yutaka Emura
KeymasterThese background/foreground-color-inversed characters are similar to caret notations except that carets are replaced with inversed representation. Please see :
https://en.wikipedia.org/wiki/Caret_notationThis way the control characters are readable while still preserving the width of each character.
Thanks,
Yutaka Emura
KeymasterHi Yang Yang,
I reproduced the > symbols when opened as UTF-8 with EmEditor. Since the binary sequences can’t be decoded with UTF-8, invalid characters appear. Please use the Western European encoding or Binary (ASCII view) to open the file.
Thanks,Yutaka Emura
KeymasterHi Yang Yang,
It looks that the file was opened with a wrong encoding with EmEditor because the > symbol shouldn’t appear. What are those character code value(s)? Can you make sure if you use the same encoding to open the file as the other editor, and use the same font? Can you also please try opening the file with Binary (ASCII view) with EmEditor?
Thanks,- AuthorPosts