Forum Replies Created
- Posts
You will need the last parameter strFilesToIgnore.
So the correct code is:
editor.FindInFiles("xxx", "C:web*.txt", eeOpenDetectUTF8, eeEncodingSystemDefault, "");
dorwins wrote:
I tried this, but it’s a 22meg file being loaded over a network share. It just ends up continually reloading. Thank you for adding it to the wishlist! :-)
Have you tried changing the “Monitor Interval [sec]” drop-down list in the File tab of configuration properties? The default is 2 seconds, and it might be too short in your case.
The new Projects plug-in allows only once instance of the tree displayed at once. This is because if you modify a project in one group of windows, and modify another project in another group, then your modifications would not be synchronized. The limit of one instance is necessary to avoid this confusion.
The syntax for VBScript for EmEditor is exactly same as VBScript. I am not very familiar with VBScript, so you might want to refer to VBScript reference books or sites.
Please use only English in this forum and do not write any other languages except when necessary to use in sample code.
You might want to explain what “Monitor Clipboard” does. Do you want something like clipboard history or “Copy Append” (Copy the selection and add to the current clipboard content)? By the way, some of these functions can be done using macros or plug-ins, and you can assign any macros or plug-ins to toolbar buttons.
dorwins wrote:
This isn’t a bug that’s new to 7.0, but when opening a log file that keeps growing emeditor puts up the notification dialog asking if you’d like to update the file so fast, it’s impossible to close the file without going to the task manager and killing emeditor. Maybe a button should be added to allow you to close the file.What I’d really love, however, is the ability to have emeditor tail the file. This would be very nice!
Thanks!
Dorwin
If you haven’t done so yet, how about selecting “Auto-Reload” for “Changed by Another Program” drop-down list in the File tab of Configuration Properties.
I will add your request “tail the file” to our wish list.
Rohit wrote:
I’m using EmEditor Professional 6.00.4, with all the Plug-ins installed.There appears to be a series of steps that causes EmEditor to crash, in a reproducible manner.
The steps are:
1. Open an HTML file in EmEditor.
2. Launch the WebPreview plug-in.
3. Right-click in the WebPreview pane, and choose “Properties” from the popup menu.
4. From the drop-down list displayed, change the value for the Custom Bar Position.
5. Press the OK button.
Result => EmEditor crashes.Some further observations, after the crash:
6. Launch EmEditor again
7. Open an HTML file in EmEditor
8. Again launch the WebPreview plug-in.
Result => The WebPreview pane appears in the new position (the one chosen just before the crash).I hope this helps. Please let me know if I can help in diagnosing the problem.
My machine’s information is:
* OS: Windows XP SP2 Professional
* Internet Explorer version 7.0.5730.11.
* RAM: 512 MB
* Locale: en-US.Best regards,
RohitP.S.: I really enjoy working with EmEditor, and am looking forward to version 7. :-)
This bug will be fixed on version 7 beta 22. Thanks!
Garrett wrote:
Each time when I press PrintPreview EmEditor ask me the question ” Portions of lines may continue is set… “.
Even if I have created the new file and has written there “qwerty” this question all the same is set.
It is impossible it to set only then when in the file there are really long strings, for example more than 80 characters?I have just fixed that on beta 21. Thanks!
danderson wrote:
Love the new OutputBar macro object. I have two suggestions that I think would make it even better:1) Add a means to specify how lines should be parsed to determine the file and line for “jumping” to relevant text. It’s a bit limiting as it is now since few external tools output in the “file(line):” format.
2) Add some way to allow jumping to a buffer that has never been saved. For example, if I want to paste some text into a new buffer and run a macro that produces “jumpable” lines, they will not work.
I understand your first suggestion. I am not sure about your second suggestion. Please describe more in details. Thanks!
You can now vote for features which should be included in future versions at the top page of this site. You can select multiple items, but you can vote only once. If your requested feature is not listed here, please reply here to have yours included before you vote since you can vote only once.
For this reason, on Version 7, you can use the new method “QueryStringByID” of the Editor object to figure out which command ID is for particular plug-in name.
Vlad wrote:
This is a new bug only in version 7.
My actual script, which was ok with version 6, looks like this:#language="Python"
if 0:
pass
else:
Window.alert('ok')
It has windows line endings and ends with 3 newlines
Now this gives error message:
invalid syntax
Line 8Line 8 is the end of file. Remove the last line and it runs fine. Other variations of the number of trailing line endings and indents give errors similar to the first post. This is quite mysterious.
I reproduced this bug, and it will be fixed on beta 20. There was a bug where dealing with the end of file in macros. Thanks!
Vlad wrote:
This macro:#language="Python"
Window.alert('ok')
results in error after successful alert display:
Traceback (most recent call last):
File "<Script Block >", line 2, in <module>
d
NameError: name 'd' is not definedThe macro file has Windows line endings and ends with a single newline (rn).
There is no error if the macro ends with two newlines.
If the macro has three newlines at the end, the error is:Traceback (most recent call last):
File "<Script Block >", line 4, in <module>
c
NameError: name 'c' is not definedConvert the last macro to Unix line endings. It ends with 3 newlines (n). Error:
Traceback (most recent call last):
File "<Script Block >", line 4, in <module>
d
NameError: name 'd' is not definedIs this a new bug only in version 7, or existed from version 6?
Garrett wrote:
Beta 17 & 18
1. Esc in PrintPreview close EmEditor instead return to editor!!!2. In version 7 missing small bar for split window(above vertical scrollbar)
I wont press Ctrl-F12 and remove vertical splitter.
I need only horizontally split.1. I cannot reproduce the issue with ESC in PrintPreview. Do you open any plug-ins at the same time thatmight cause the issue?
2. The small bar is missing for simplicity. You might want to use F12 to open only horizontal split window.
I am sorry there is no information at Help about this option yet. It only means that if you check “Right Side” check box for a particular highlight word, the highlight will be in effect at the right side up to the window border (if no wrap or wrap by window is selected) or specified width or page width. If this is not checked, the right side highlight will occur only up to the word wrapped position. You should try it to see how it works.
Vlad wrote:
Mouse triple click selects view line. It should select logical line instead. There is also a line selection mode command (Ctrl-P). It also selects view lines. I think users want to work with logical lines most of the time.Minor glitch: if the text has no terminating newline, selecting last characters also selects end-of-file mark. Not a bug, just looks strange.
This minor glitch should be fixed on beta 17. I will add the mouse triple click behavior option to our wish list. Thanks!
xxx_pic wrote:
Sometimes, I typed something and the document’s Caption displayed a “*” , but the “Save” command on the toolbar or menu still disabled !I have not had this issue before. When you see next time, please let me know how you can reproduce this problem. I need to reproduce your problem on my machine too to fix this. Thanks!
In EmEditor, there is no limit in length of a line, so there is no message box needed. I guess you should try with “No-Wrap” mode and also disable any highlight (uncheck “Highlight These Words” on the Highlight (1) tab of properties). If you still have the issue, please zip the sample file and email to [email protected] as an attachment. Thanks!
