Forum Replies Created
- Posts
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!
titieye wrote:
install EmEditor, click Menu – Tools – Export a portable version to a folder,
“d:MyPortableSoftwareEmEditor”.click Menu – Macros – Customize … Then New a Macro named “InsertSomeWords.jsee” .
(the full path of “InsertSomeWords.jsee” is in “d:MyPortableSoftwareEmEditorMacrosInsertSomeWords.jsee”)this InsertSomeWords.jsee couldn’t properly display on the macro bar,
when the macro icon clicked, OS will alert—————————
can’t find the file.MacrosInsertSomeWords.jsee
—————————now in “eeCommon.ini” – [Common] section
MacroFolder=.Macros
MacroFile=.MacrosInsertSomeWords.jseeso i think the portable EmEditor couldn’t properly deal with this,
maybe it replaces the absolute path with relative path somewhere needn’t.when comparing with the installed version of EmEditor’s regedit data.
i find the eeCommon.ini file lack of some information of macros in regedit data.I think this was fixed by beta 13. Please always try the latest version.
Sekka wrote:
Will this be a feature of EME7?Yes, the coloring “theme” feature will be included in beta 13.
yongfa365 wrote:
beta 12 also don’t see old search
only see long charyou changed findbar history list
this is Findbox or replacebox ‘s history listThis will be fixed on beta 13.
Sorry, you can choose “Custom” for the Word Type in the Matching Criteria tab of the Word Complete properties, and enter _ for the Mid Characters. The beta 12 will include _ for the Normal Words.
