@martin-honnen , Please be careful when forking and keeping the original name for an apparently-abandoned plugin. Sometimes, it turns out it wasn’t as abandoned as thought – something like that happened with NppConsole plugin (as obliquely mentioned in a recent Topic here): a few years ago, it appeared abandoned, so a regular here took the source code, and made their own fork, but kept the original name (thinking it would be safe, because it appeared to be no longer supported in the original channel); but then, fast forward a few more years, and the original author did provide their own upgrades to the original plugin – so now there are two competing development paths, each having version numbers not present in the chain for the other, which will make any future questions in the forum confusing, as to which NppConsole plugin is actually being talked about. Similarly, if morbac ever decides to come back to the plugin, then your fork and the original could have conflicting and/or confusing version numbers and naming. I would highly recommend coming up with your own name for your product, if you are planning to continue development and support on your version of the plugin. If it’s really just a one-off thing, and you aren’t planning on future bugfixes/improvements/support, then it’s up to you whether it’s worth the rename; but if you want to continue to work on the plugin, then I’d suggest the rename. OTOH: if you can get permission from @morbac to take over completely, then it’s safe to keep the original name, because you’ve got the permission. (It’s most clear, in cases like that, if you can get write permission to the original repo – @chcg was able to do with @bruderstein’s PythonScript, and that sense of continuity makes it more obvious that his is still the “official” PythonScript.)

@Steve-Plumlee said in Flickering screen on the latest edit that i've made (like a preview of current and previous state): @GM-Bobby-B Hi I am having the same experience. I suspect this is a new “Feature” but I have been unable to determine where the setting is to turn it off. Did you ever figure it out? @Lycan-Thrope Appreciate your FAQ items but I think this is a feature that was added. Maybe one of the dev’s can answer that Forum search didn’t result in any other posts so maybe it’s a plugin or something? No, if the video that the original poster put in reddit last year is realy what you’re seeing, it’s not a “feature”. @Lycan-Thrope linked to the FAQ because the original poster didn’t give enough version information to be any help. And despite thanking him for the link to the FAQ, neither did you. Share your ?-menu’s Debug Info to let us know what version you are using, and many other things that are often relevant to debugging uncommon problems. That user has never come back to this forum since the original post, so never even saw @Lycan-Thrope’s answer. And the people in Reddit just found that changing the caret blink rate in the preferences “fixed” it for them… though that should have nothing to do with what Notepad++ displays. My guess is that it was really a plugin causing the problem, or that the underlying cause is actually something slowing down the entire computer, causing it to refresh Notepad++'s screen at odd times. If you think it might be a plugin, we’ve got a different FAQ which has a section on diagnosing “Possible Culprit: Plugin”: you should follow the steps included there.

@shodanx2 See HERE.

@Martin-Bishop said in Notepad++ not responding:. I followed the steps above and was certain it was a new plugin I installed earlier in the day, but the removal of plugin, creating a backup Notepad++ folder in %AppData% and completely uninstalling NP++ before reinstalling it hasn’t fixed anything. For now, the only way to start it is to use the -noPlugin command line argument on my usual shortcut to the program. If using -noPlugin makes it work, that means it’s one of your plugins, or an interaction between multiple plugins, causing the issue. Our freeze/crash/plugin FAQ explains how to try to isolate which plugin is the culprit.

@JW I suggest adding an option to select the AI module.

@dz15mlru Disable automatic encoding recognition. For Windows-1251 encoded Russian, auto-recognition will always open as Macintosh. If you start editing files, you will have two encodings, or rather garbage from two encodings, which will be difficult to fix manually, since you will have to re-read all the texts (this is a module for spoiling files). When you disable automatic encoding assignment, you will only have ANSI, UTF-8, UTF-16. WindowsXP-7-8-10-11 it will always open the ANSI file correctly, in 1251 encoding, as this is the default encoding. The remaining UTF-8 and others will also open automatically correctly. You will get rid of the problem forever. The automatic text encoding recognition module is needed if you open files in Arabic in ANSI, but in reality you will never do this, since a Russian-speaking person has only Russian-language files on their computer. People who want to make the file available to all people on earth save the file in UTF-8 encoding and it will always open correctly for you. You don’t need automatic file recognition, as it’s only for local files that you’ll never get from someone else’s computer abroad. Отключи автоматической распознавание кодировки. Для русского языка в кодировке Windows-1251 автораспознавание всегда будет открываться как Macintosh. Если начать редактировать файлы, то у вас будет две кодировки, точнее мусор из двух кодировок, который будет трудно исправить вручную, так как вам придётся перечитать все тексты (это модуль для порчи файлов). Когда вы отключите автораспозначание кодировки, то у вас будет только ANSI, UTF-8, UTF-16. WindowsXP-7-8-10-11 всегда откроет файл ANSI правильно, в кодировке 1251, так как это кодировка по умолчанию. Остальные UTF-8 и прочие откроются также автоматически правильно. Вы навсегда избавитесь от проблемы. Модуль автоматического распознавания кодировки текста нужен если вы открываете файлы на арабском языке в ANSI, но в реальности вы никогда этого не сделаете, так как у русскоязычного человека на компьютере есть только русскоязычные файлы. Люди, которые хотят сделать файл доступным для всех людей на земле сохраняют файл в кодировке UTF-8 и он всегда откроется правильно у вас. Вам не нужно автоматическое распознавание файлов, так как оно только для локальных файлов, которые у вас никогда не появятся с чужого заграничного компьютера.

@Jeff-Esposito said in Notepad++ VERY slow to open: e gotten my new computer Notepad++ takes 40-50 seconds to launch. I have removed all plugins and don’t check recent file history at launch is checked. There are no open unsaved tabs, even though that is how I want to use it and use it on my old pc and my work laptop. the install It becomes slow when using “Show Folder As Workspace” (which displays the workspace folder on the left side). It starts quickly when this option is turned off.

Yeah, this usually happens with non-breaking spaces (U+00A0) or other Unicode space characters that look invisible but behave differently from normal spaces. Using \xA0 in regex was the right fix 👍 If you face this again, you can: Use \x{00A0} or \s to detect space variants Check in hex editor to identify exact character Then replace all in one go Also, if you’re unsure which invisible character it is, you can test different ones using tools like espaço invisível before applying them in your editor.

Honestly, this cleared up a big confusion for me. I used to think fonts were saved with the file itself, but it makes sense now that it’s just the editor displaying it differently. Also didn’t realize enabling global font overrides can mess with syntax highlighting—good catch. I’ve been tweaking text styles a lot lately while testing name formats on font generator, so this helps keep things consistent

Yes—Notepad++ doesn’t automatically strip HTML, but copying through plain-text mode (like Notepad or Reader View) removes all tags. To retain <p> and <br>, avoid pasting via plain text—either paste directly into Blogger’s HTML view and clean unwanted code manually, or use an HTML cleaner tool to keep only specific tags instead of stripping everything.