Forum Replies Created
Turns out it was the display adapter driver. Went back to an old version and all is well.
Strangely enough it’s happening again. I have no idea why it seems to happen sometimes and not others.
Thanks Yutaka. I updated my display driver and it appears to have resolved the issue.
that’s perfect for what i need thanks :)
I agree with that breakdown/description of the issues with the exception of the fact that, unlike Criss, I still see “Flickering of text when outline guide is enabled” in 7.00.2 RC 1.
Don’t know why, but I still see the same flickering issue with the outline plugin. I noticed that even the text in the outline sidebar flickers. As Criss noted, the flickering of the current line behavior without the outline plugin enabled remains for me as well. :(
Sent it with explanation in comments at the top of the file. Let me know if you have any questions.
EditPlus provides this feature. It passes the selected text (or the whole buffer if nothing is selected) to stdin and replaces the selected region or entire buffer with whatever is returned to std out. It’s very useful. You can undo the changes because the buffer is modified not the actual file on disk.
On the bright side. You can accomplish the same thing using macros. It works just as well and provides even more control. I can post an example if it is helpful.
There seem to be a few threads on this issue (some focused on the outline plugin) and some not. I thought I would add an additional entry since I still see this problem with the latest release (7.00.1). At some point during the version 7 beta process this problem went away… and then it resurfaced. What I have found is that when the outline plugin is not active, only the current line is affected (e.g. the text flickers when typing quickly). When the outline is enabled, other lines are affected. The easiest way to reproduce is to open a text file, type as fast as possible (e.g. aldskfja;dlkfjad;lkjdsa;lk) or hold down the delete key. It’s much more prevalent when the outline plugin is enabled.
I don’t think it’s a hardware problem. I have seen this on multiple machines. Laptops, yes, but new Thinkpads (t60, t61) with fast processors and discreet, higher-end graphics.
Please let me know if there is any information I can provide to help troubleshoot.
My mistake. I confirmed that it has nothing to do with the outline plugin, but the effect is the same as was for that issue. When typing very quickly, the text on the current line “flickers”. It’s purely cosmetic and minor, but a little distracting.
So basically, the scenario is something like this.
1) create a new file
2) paste text
3) run a macro that processes the contents of the file and prints output to the output bar that refers back to lines in the unsaved file buffer
Right now, there is no way to make the references to the lines in the unsaved buffer work because a file name is required. Since the the buffer is not saved, it has no file name.
It would be nice to have a way to have EmEditor jump to the referenced line in whatever file/buffer is currently displayed rather than a specific file.
Hope that makes sense. I actually use this functionality a lot to do quick processing on pasted text from other apps but I don’t want to have to save to a file every time I do it.
Works in Beta 12 :) Thanks.
Figured it out. It’s the outline plugin. I have the outline plugin enabled even when the bar is not displayed. When the outline plugin is enabled, triple-click to select line doesn’t work.
I uninstalled EmEditor and removed all my settings. I reinstalled it and it worked. I then proceeded to add back all of my settings (uggh). Now it doesn’t work again. There is a setting somewhere that prevents this from working. I haven’t figured out which one. I’ll keep trying to figure it out.
Still doesn’t work for me in Beta 9. Does this work for others? I saw a post somewhere that led me to believe that it does actually work for some people.
Funny. Triple click doesn’t work for me at all. Is there a setting somewhere to turn on/off?
I just noticed the other day, very nice :)
Fixed in Beta 4 :)
elements still take on a different syntax color in xml documents, but I assume this is intentional. Not sure why.
Appears to be fixed in Beta 3 :)
I respectfully disagree. When the background for a keyword type is not specified (e.g. set to default) the current line highlight color should not be replaced with with the default color for a non highlighted line.
For example, there is no way to do this in EmEditor:
It looks like this:
Note that the cursor is on line 5 in both cases. I don’t have white set explicitly for the background color of strings for example. If I am missing something, please explain.
Do you have an estimate on when version 7 might be available??
Any ETA on Version 7? Anxiously waiting :)
FWIW, I just realized, based on another forum post, that the outline plugin causes this issue.
I have this same issue, although for me, I didn’t think it was limited to when I was using the outline plugin. I’ll have to check that.
It turns out that for me it is just the outline plugin as well. I never realized that this was caused by the outline plugin (since I always have it running).
It also would be nice if there was a way to make “tag jump” go to a line in the current active file. Right now, there’s no way to do a tag jump to a buffer that is not yet saved. Something like …
(100): some text
… would work.
I wrote a macro that writes output with tag jump information to a temp file and then calls a macro to write the temp file contents to the output bar. It’s a hack to get around the lack of any way to write to the output bar via a macro, but it works just fine for files that have been saved. Unfortunately, it doesn’t work for unsaved buffers.