my apologies for that.

Please don’t - it was my responsibility to make sure it works before releasing it.
I was integrating Markdown into all zip packages then I realized it doesn’t deployed correctly by Installer in v7.6.3.

Anyway, it’ll be better now:
https://github.com/notepad-plus-plus/notepad-plus-plus/commit/dcd3942362306b9c36b849405d112e885c0a1f51

you’re welcome and many thanks back.

It’s crazy that no user report it, or it’s just me who is not aware of users’ complaint?

we did not get any complaints about the missing markdown udl at a fresh install either.

i personally did not notice it, because i’ve downloaded the predefined userDefineLang.xml manually, prior to release, on some of the clean testing instances.

and i did not pursue the missing markdown (default) udl on installs which already had existing udls, as we were prepared in advance with the info, that an already existing userDefineLang.xml will not be overwritten.
my apologies for that.

did you discover this by coincidence, or did you get any private complaint ?

Thank you for your very prompt test and confirmation.
It’ll be fixed in v7.6.4.
It’s crazy that no user report it, or it’s just me who is not aware of users’ complaint?

i can confirm.

the predefined userDefineLang.xml including Markdown (Default), is not copied to %AppData%\Notepad++ after the first run of notepad++.exe at user level, if it does not exist.

an %AppData%\Notepad++\userDefineLang.xml file will currently only be created if we create any dummy udl.

test platform:

i’ve taken a new, blank windows 10 vm and installed npp.7.6.3.Installer.exe.

debug info:

Notepad++ v7.6.3 (32-bit)
Build time : Jan 27 2019 - 17:20:30
Path : C:\Program Files (x86)\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : DSpellCheck.dll mimeTools.dll NppConverter.dll NppExport.dll

I just realized Markdown installed via installer doesn’t work in v7.6.3. Can anyone here confirm me Markdown doesn’t work in v7.6.3 installer’s version?

i was not able to reproduce any of the past instances, where a 32 bit installer was downloaded by gup of an 64 bit installation.

Even, I am not able to reproduce. But there can be two possibilities. May be in some corner case,

1. Either notepad++ is not able to identify whether it is running as 32 or 64 before launching GUP.exe
2. Or Notepad++ passes proper argument, but gup. is not able to parse properly.

https://github.com/notepad-plus-plus/notepad-plus-plus/issues/4090#issuecomment-466638137

thanks.
i was not able to reproduce any of the past instances, where a 32 bit installer was downloaded by gup of an 64 bit installation.
(at least not on the clean test systems, where each just has one notepad++ installed, either 32 or 64 bit.)

do you know of a specific way to reproduce that ?

However, users are getting triggered now.

7.6.3 auto update already has been taken down, set to a maximum of 7.5.9, confirmed and tested.

you can check this at your browser by simulating different versions with the following updater url’s:

7.5.8 updater: https://notepad-plus-plus.org/update/getDownloadUrl.php?version=7.58
7.5.9 updater: https://notepad-plus-plus.org/update/getDownloadUrl.php?version=7.59
7.6.2 updater: https://notepad-plus-plus.org/update/getDownloadUrl.php?version=7.62
7.6.3 updater: https://notepad-plus-plus.org/update/getDownloadUrl.php?version=7.63

note: examples are for the 32 bit versions

no problem at all, everything was nicely quiet and happy so far.

May be weekend, that’s why. However, users are getting triggered now.

https://github.com/notepad-plus-plus/notepad-plus-plus/issues/4090#issuecomment-466638137

Auto-updater will be triggered in the next version (v7.6.4).

issue: 7.6.3 update is repeatedly triggered.
can you confirm ?

I Confirm.
Thank you for the heads up.
I just stop it and see what’s wrong.
I will keep you posted.

issue: 7.6.3 update is repeatedly triggered.

i’ve noticed, that the update url response stays on
<NeedToBeUpdated>yes</NeedToBeUpdated>,
even if notepad++ 7.6.3 is already installed.

so every time you check for updates on a 7.6.3 installation, it will currently always prompt: “an update package is avaliable, do you want to download it”.

it stays the same if you reload and reinstall the same 7.6.3 version.
it will still present the same 7.6.3 download again.
(both tested on x86 and x64 installs)

can you confirm ?

thanks for the heads up 👍

Angry users incoming, angry users incoming.

😂😂😂

we will keep them happy 😉

So, this further highlights the usefulness of beta versions.

yes, that is why we have been given the opportunity to download any pre release versions at appveyor.

it is the quickest, simplest and most non intrusive method of a beta distribution, as we only have to download a new Notepad++.[architecture].Unicode Release.exe and place it into our current installation, or portable versions program folder, without the need of installing anything new.

once you have put this “beta” exe into your notepad++ folder, you can use it by double clicking on this Notepad++.[architecture].Unicode Release.exe.

best thing: after testing, you can still use your old notepad++, as this “beta” version has a different exe name, and (usually) does not modify your current installation (unless e.g. you play around with any settings). 👍

@V-S-Rawat said:

I think I will skip this version and shall update when plugins have found their final destination.

Recently, I saw a discussion on beta versions.

I think what I was doing was treating this 7.6.3 as beta version, and ignoring this till things settle down to a final shape. Then I will install the “final release”.

So, this further highlights the usefulness of beta versions.

1. Clear history “search and replace”
2. Open the folder with the installed plugins

In order to avoid erase defined UDL (file userDefineLang.xml), installer of this version checks if userDefineLang.xml exists. If not, then it copies DefinedLang-markdown.default.modern.xml to userDefineLang.xml.

However it will be good to have UDL file separately per language: a UDL folder beside of Notepad++ binary, *.xml in this folder will be loaded as UDL. It will be implemented in the future release.

Yes, @meta-chuh, easier, of course 😄

Cheers,

guy038

… or you can simply download and save userDefinedLang-markdown.default.modern.xml from >>> here <<<

Ha ha ! Don’t forget that the Installer .exe program is simply an archive, that you can just open as a true archive ;-))

So, the solution is elementary :

• Download the npp.7.6.3.Installer.exe. Note that, even if your system is 64 bits, you do not need to download the npp.7.6.3.Installer.x64.exe. Indeed, they contain the same files, regarding “Markdown”, anyway !

• Open the npp.7.6.3.Installer.exe file with, for instance, the 7-z Manager program

• You can see, that it contains two identical files, of 5,440 bytes !

  • userDefinedLang-markdown.default.modern.xml

  • userDefineLang.xml

• Finally :

  • Extract the userDefineLang.xml file in your portable NPP folder, if not present, yet

  • Insert the Markdown bloc <UserLang name="Markdown (Default)" ..............</UserLang> in your present userDefineLang.xml file

Done :-))

Best Regards,

guy038

userDefineLang.xml is the config file for user defined languages (udl).
this is where anyone can create his one “lexer” for any programming language that isn’t already available for notepad++.

you can also use it to highlight any text you have, like notes, to make them more readable for you.

here’s a screenshot of the markup udl:

please open another topic in general discussion, if you are interested in how to use udl, or have any further questions about it, so that we can focus about it separately.

What am I missing out by not having this file in my portable folder, and can I just copy the installer’s userDefineLang.xml file into my portable install? If so why go through all these extra steps and not just put this file in the portable version in the first place?