@Louis-Windsor said: The AIs both confirmed my conclusions. WHY are you still relying on AI in this case, when it’s OBVIOUSLY wrong most of the time? I know that if you don’t have any knowledge in a specific field and then someone comes along claiming to know everything about it, you might be tempted to believe them, but if you get a different answer from someone else that’s essentially factual, you should really consider whether AI can actually help here. F-strings were introduced in Python 3, so I think it’s nonsense that YOU tested 2.1 and 2.7 with them. Shortcuts are possible and are used. For a script to be recognized as a “PythonScript script” it must be created via the “New Script” menu item. It doesn’t work to simply write Python code, save it, and then hope that it will be automatically ‘registered’ by the PythonScript plugin. “New Script” is the method specified by PythonScript that must be followed. If it doesn’t work for you, please describe exactly what you’re doing, step by step, so that someone else can reproduce the issue. And… really… your AI is… well… just bad or poorly prompted.

@Alan-Kilborn said in New feature: Allow additional line on each search results: @Coises I can’t tell if you’ve considered this, but one way to do it would be in conjunction with hiding lines. You could hide lines that don’t meet the criterion of -M through +N, where M would be a user-chosen number of lines before the hit, and N a user-selected count of lines after the search match. At first thought, I believe that would be significantly easier to implement than doing it in the search results window. As a plus, it (or a close approximation) could even be available after the search with something like an “expand visible blocks” command. The downside is that Show commands only work on the current document; you can’t show in all open documents (and it wouldn’t even make sense for find in files, whenever I finally get that done). At present, my use of hidden lines (using Scintilla’s function directly) and Notepad++’s way of doing it (keeping its own internal table, inaccessible to plugins, of what ranges are hidden) are at odds with one another, which causes any changes my plugin has made to hidden lines to be lost when any other tab is switched into the view. Thus far, I have not been able to devise any solution to this.

@Samir-Sumantlal-Shah said in Hopefully Notepad++ can display correctly ...: GujaratiMT Searching suggests that “Gujarati MT” is a Apple system font that is not available elsewhere. Are you by any chance using the new MacOS port of Notepad++? That port is not maintained or endorsed by the creator of Notepad++. You would have to raise issues with it in its own repository. We’re not going have a clue here.

Thank you Peter. Makes perfect sense. Much appreciated!

[image: 1777628352084-npp-working-rendering-modes-for-rdp.png]

@Shobansky , See my longer answer to you here. I’m not sure why you started a new Topic when you were already participating in a Topic about exactly the same thing, and when there was a Topic created 5 days ago that was essentially the same thing. (Also, naming a Topic “feature request” is not helpful to people looking through the titles of the recent posts, because it tells them nothing about the contents of said feature request. Titles should be meaningful if you want meaningful discussion.) Also, since I’m not sure you’ve seen it, our new feature FAQ explains that, while we can talk about ideas all we want in this Community of Notepad++ users, it isn’t an official Feature Request until you follow the instructions in that FAQ to post the Feature Request to the official Issues tracker for the project.

@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 и он всегда откроется правильно у вас. Вам не нужно автоматическое распознавание файлов, так как оно только для локальных файлов, которые у вас никогда не появятся с чужого заграничного компьютера.

@Shobansky , A few months after the original post was made, this FAQ was created, which explains how to use pork2sausage plugin (or the run menu, or the NppExec plugin) to transform text. And since things like Prettier or js-beautify exist, it makes more sense to pass formatting to an external utility that’s customized for a specific programming language, to make users of that programming language happy – rather than relying on limiting the formatting to whatever rules that one developer adds to the editor. (Given the arguments people have over the auto-indentation, and how the developer hasn’t been able to keep everyone happy even on that “simple” aspect of formatting, trying to get a generic formatter to the point that everyone is happy is virtually impossible.) I don’t understand why it doesn’t have some formatting capability like other editors… Every editor has strengths that it focuses its feature development on. Notepad++'s strengths are in the ease and availablilty of plugins and running external applications… so plugins specific to the language (like HTML Tidy) or plugins that launch external programs (like pork2sausage) are the way that Notepad++ made it easy to get formatting customized the way you want it, rather than restricting you to the ability of the N++ developer to support and implement. And the developer’s philosophy is that, unless it’s something that he wants to put his own stamp on, if it’s already been implemented well in a plugin or can be easily run through the run-menu/pork2sausage/nppexec, then he doesn’t want to waste his effort on doing something mediocre built-in when something good-to-great already exists. As someone with a full time job completely unrelated to Notepad++, he wants to focus his limited development time to things that he likes, he wants, or that he can add value to. Moreover, in the modern realm, things are moving toward LSP-based solutions – so if the languages you program in have LSP servers available, then (as was mentioned in this very similar question a few days ago) you can use one of the LSP plugins (the plugin by Kered or @Ekopalypse’s LSP client plugin) – so if your language’s LSP server has the code formatting feature, the LSP plugin you choose should be able to activate that.