@patrick-danilevici ,

I previously said,

hardcoded SaveAs menu.

Good news: there is at least a workaround in the Save As menu. It turns out that wasn’t as hardcoded as I thought.

If you go to %AppData%\Notepad++\langs.xml, and edit it (following config-file-editing recommendations), adding

<Language name="Fake" ext="fak fake false"/>

… then save and restart, then File > Save As gets a new entry:
b460b6af-85bc-42d4-9302-6a53b3b677fd-image.png

It’s poorly named as “Normal text file” again, but it has a different list of extensions (and the original “Normal text file (*.txt)” at the beginning is still there, so you lose nothing).

By my experimentation, where you put that line in langs.xml will determine where in the SaveAs list it goes, so if you use it often, put it near the top. For example, if I move it from the end of the list to right after the normal “Normal”:

<Languages> <Language name="normal" ext="txt"/> <Language name="Fake" ext="fak fake false"/> ...

… then it will go right after the normal-“Normal” in the list:
a9d5a099-002d-41d8-86bd-324e8fb6f1da-image.png

So you would miss the name of the UDL in the Save As list, but that would at least have that extension list, and when you select that new entry, it will default to .fak appended to your filename. If you have your UDL set up to be automatically associated with .fak (that is, the user extensions box in the UDL setup shows as fak fake false to match my langs.xml entry), then once you save the file as something.fak, Notepad++ immediately changes the selected Langauge to your UDL.

Unfortunately, that doesn’t put it in the Settings > Preferences > New Document > Default language group, but it is a step in the right direction.

@peterjones said :

TL;DR Please post in English in this forum, as you have been asked multiple times.

Of course, the option exists for those that don’t post in English to reply to them with:

Please re-post that in English as this is an English forum; unless you do that your posting will be ignored and not replied to.

@peterjones Thanks alot,

That solved my issue.

@peterjones
I use NP++ as a better alternative for MS NP and I don’t use it as a programming text editor, just use for edit txt, srt, cue sheet, ini files.

You can see my NP++ settings in SS below (I don’t know why NP++ has such an odd behaviour with all “Persian” fonts! It shows the fonts illegible and thinner than they are with jagged edges!).

npSS.png

@edzilla2000 said in bak file as new default:

This is very inconvenient for us, as it adds useless .bak files to git repos and other unfortunate locations.

How horrible. I wonder if git has a configuration file to be able to ignore backup files; maybe they could call it semething unintuitive like .gitignore in the hopes that git users would never be able to find it with an internet search for “how do I ignore backup files in git?”

(Less sarcastically, I’ve been doing backup-file ignores in my subversion repos for over a decade, so it’s not like Notepad++ is the first product to ever create backup files. In fact, some installations of subversion default svn:backup to ignoring common backup and temporary files.)

Is it possible to set up a default configuration to override such per-user settings?

Yes. That setting, like all the others in the GUI, is stored in the config.xml file which goes in the %AppData%\Notepad++ folder for each user. So when you install, you could either make your own zip/self-extracting-zip which has the modified config.xml, or you could overwrite config.xml after doing the normal installation.

@mathlete2 ,

It’s not working because commentEnd must be non-blank if you want commentStart to work. If I set it to <Language name="batch" ext="bat cmd nt" commentLine="REM" commentStart="::" commentEnd="::REM">, save, exit, reload, then load a file in Batch, the Ctrl+Shift+Q will block-mode, where it puts :: at the beginning of the current selection and ::REM at the end of the current selection; but if I set commentEnd="", it will instead just use the commentLine for the block-comment commands as well, ignoring both commentStart and commentEnd. I tried some experiments, and even if you did something as simple as commentEnd=" " (where it uses a single space in the attribute value), it will use :: for the beginning and a space for the end.

But please note, if you do get it working that way: block comments are meant to allow for multi-line, and abusing cmd.exe’s label syntax (which is actually what :: is for) to be a pseudo-comment will not create a multi-line comment in cmd.exe syntax. It would just put :: at the beginning of the selection and whatever non-empty text you chose for the commentEnd at the end. Which means, if you have more than one line selected, only the first line would be commented out.

If you want to use :: as your line comment, then you should just change commentLine="::", and then line-comment will always use that (and block comments will instead apply the line-comment individually to all selected lines). But you cannot set it up in a way soas to have two different single-line comment syntaxes, as that is not how the comment-feature was designed.

(we literally just added the text These attributes can only define one type of line and block comments; if your language has multiple types of either, you will have to choose the _one_ type that you'd like Comment/Uncomment to work with. to the user manual: it hasn’t even had time to be released to the website yet. but it will be in the next revision of the website.)