Thank @Scott-Sumner :
I was talking about the translation ID 43033 … 43043

<Item id=“43033” name=“1st style”/>

I renamed it as “jump up to 1st style”. That would removed the confusing things in Shortcut Mapper but the modifications was rejected by donHo.
See the PR and comments https://github.com/notepad-plus-plus/notepad-plus-plus/pull/2299

@jeffwestfahl
hard to tell without screenshot, but i remember a similar problem and possible solution posted here some time ago.
maybe (hopefully) just your windows dpi scaling was changed by the drivers.

to test this exit notepad++
run following command line, start menu search field, in the run menu or in cmd:

%windir%\System32\DpiScaling.exe

then check that you are on 100% scaling
restart notepad++

if it already was on 100% or it doesn’t get better, repeat and play around with a different dpi scaling % factor to see if you can get close to the tab/font size you were used to.

(also combine different dpi settings with switching the reduce tab bar option inside notepad++ off and on again)

What were you expecting to see in a text editor when opening this file? .dat files are generally data, specific to whatever application generated them. Often, they are binary – and it obviously looks binary based on your paste.

If you want to be able to edit some underlying textual data, you will have to determine what application created the .dat file, and find out whether there is a converter from that format to plaintext (it might be a converter, or an unzip-like utility, or a decompiler, or…). Once you have it in a text format, it will be easy to edit it with Notepad++. Once edited, you can use the same (or complementary) converter to get it back to the original format.

Notepad++ isn’t some magic program that can “read any file format, convert it to text for editing, and convert it back to the original encoded format when saving”. It’s an excellent text editor, and with the associated scripting and assuming an appropriate converter, it would be possible to automate the process of convert-on-load, convert-on-save, but it’s not going to be able to take an arbitrary binary format and magically know how to decode/decompile it.

Try View/Word wrap. It’s wrapping the lines to the width of the window without horizontal scroll bar.

@decoderman Thanks, reinstalling worked, now it’s not reappearing anymore!

Thanks alot guys! =)

Thank you, that solved the problem. I just had to copy and paste my old unsaved files into new unsaved files, and now they’re being created in the new backup folder and backed up by Dropbox.

Here is a better one:

Current One: https://imgur.com/a/wJg75

What it’s supposed to look like: https://imgur.com/a/b1nYd

It’s like it’s a different font and it looks like an old version. It’s kind of hard to see unless you make it full screen.

@Theo-Fondse

There is probably a better solution, but until you find it you could script turning Num Lock back on after Notepad++ starts up with the Pythonscript plugin.

Put the following code in startup.py and make sure Pythonscript’s “Initialisation” option is set to ATSTARTUP (under the Configuration menu option for the Pythonscript plugin). Note that Pythonscript is only 32-bit right now, so it will only work with 32-bit Notepad++.

I really hope you find a better solution and don’t have to resort to this !! :-D

If this (or ANY posting on the Notepad++ Community site) is useful, don’t reply with a “thanks”, simply up-vote ( click the ^ in the ^ 0 v area on the right ).

import ctypes def turn_on_numlock(): VK_NUMLOCK = 0x90 KEYEVENTF_EXTENDEDKEY = 0x01 KEYEVENTF_KEYUP = 0x02 GetKeyState = ctypes.windll.user32.GetKeyState keybd_event = ctypes.windll.user32.keybd_event if not GetKeyState(VK_NUMLOCK): keybd_event(VK_NUMLOCK, 0x45, KEYEVENTF_EXTENDEDKEY | 0, 0) keybd_event(VK_NUMLOCK, 0x45, KEYEVENTF_EXTENDEDKEY | KEYEVENTF_KEYUP, 0) turn_on_numlock()

@Scott-Sumner You are totally right, reg expression are still a mystery for me. I use it in a dummy way, chek email format, numbers. But to me is a pending issue. Thank you very much, you gave me more than I expect.

This appears to be a bug in Scintilla that has been there since the dawn of time. Coincidentally, this was patched a month ago. The bad news is that it can take a long time before NPP gets a new Scintilla engine. If it’s really vexing you, you could install the Poor Man’s T-Sql Formatter plugin. I think that comes with a custom language definition that doesn’t suffer from the same bug. It does some nifty automatic formatting for you too.