New NPP Install issues for UDL features install

PeterJones

For future reference, this priority is described in the manual:

Lycan Thrope

Thanks Peter. That’s where I thought I read that, of course, there was no mention of having to make that directory to mimic the system one, so it was a guess on my part plus I remember you saying to someone else to copy that directory into the AppData heirarchy.

Now…as I understand it, someone mentioned somewhere in my research in the forums posts, that there was going to be a feature in the next version that allows the AppData directory structure to be pointed somewhere else to avoid(?) issues with the AppData directory? Do you have any information on how that’s going to be accomplished, as it means I may have to add more error checking and filepath collection code in my installer app to accomodate the new feature.

I’m guessing, if it’s implemented, it’ll have an entry in the config.xml file that might still be in the AppData directory or some kind of redirection location to query. Thanks for any info in advance…especially since I just got this right and it’s working now after a year of creating and testing all of the UDL and fixing problems to make it work and also to finally get the installer written also, only to have to change it again :) Now I know how Don Ho feels. LOL

PeterJones

@Lycan-Thrope said in New NPP Install issues for UDL features install:

That’s where I thought I read that, of course, there was no mention of having to make that directory to mimic the system one, so it was a guess on my part plus I remember you saying to someone else to copy that directory into the AppData heirarchy.

I am adding a few new paragraphs in that section:

someone mentioned somewhere in my research in the forums posts, that there was going to be a feature in the next version that allows the AppData directory structure to be pointed somewhere else

The only such features I know about already exist: the Cloud option (which has been around as long as I’ve paid attention) and the -settingsDir command-line-option (added in v7.9.2). But I don’t stay on top of all the feature requests (this Forum keeps me busy enough), so it may well be that they are finally implementing the fixes to those to make them “complete” rather than just having some of the config files looked for there. (Or maybe reinventing that wheel again?)

Lycan Thrope

@PeterJones ,
Thank you for those new paragraphs. They explain the situation better, and I sure wish I’d been able to read that before I completely uninstalled my NPP to test the intaller. All I would have had to do was rename the folder and rename it back after the testing. ::sigh:: :)

Thanks for trying with regard that feature. I’ll try to see if I can find more about that cloud option/directory redirect on the off chance that there are folks using it, so I can modify the install routine to check and apply for it.

PeterJones

@Lycan-Thrope ,

If Cloud option is enabled, Notepad++ will create a folder in the install directory called cloud\, and that will contain a file called choice whose contents are the path to the cloud directory that will contain Notepad++ settings.

– https://npp-user-manual.org/docs/config-files/#other-configuration-files

So to look for that option, just look for the existence of <install>\cloud\choice

Lycan Thrope

@PeterJones ,

Thanks Peter. That helps immensely. I was searching the forums to see if I coud find that mention again, but can’t seem to find it, so no matter. Your info points me back to the documentation which I’ll have to go over that section Since I know we have a few developers that have been looking at using cloud resources, I figured I better look into that option now, to head off any complaints/suggestions about cloud usage or non AppData usage.

Lycan Thrope

@PeterJones ,

I was trying the Cloud setting, and I found that it didn’t create the cloud\choice directory and file in the install directory, it actually showed up in the AppData\Roaming\Notepad++\ folder, as per this screenshot.

And the file in this directory per this screenshot:

Just want to clear up and/or clarify what just happened. All I did was click the setting for the cloud here and selected a directory for it to put the files into that could represent a cloud directory as in this screenshot:

Then after closing NPP, this directory filled itself with the config files that the AppData\Roaming\Notepad++\cloud\choice file pointed to as shown in this screenshot:

Peter, I’m just trying to cross the t’s and dot the i’s :) to make sure I don’t make the same mistake with the directories again. :)

Lycan Thrope

@Lycan-Thrope ,
By the way, this is with this debug info:

Notepad++ v8.4.6   (64-bit)
Build time : Sep 25 2022 - 19:51:39
Path : C:\Program Files\Notepad++\notepad++.exe
Command Line : 
Admin mode : OFF
Local Conf mode : OFF
Cloud Config : C:\Users\<user>\Documents\Test Directory
OS Name : Windows 10 Home (64-bit) 
OS Version : 21H2
OS Build : 19044.2251
Current ANSI codepage : 1252
Plugins : 
    ComparePlugin (2.0.2)
    CSVLint (0.4.5.4)
    CsvQuery (1.2.9)
    mimeTools (2.8)
    NppConverter (4.4)
    NppExport (0.4)
    NppXmlTreeviewPlugin (2)
    PlantUmlViewer (1.3.0.7)
    PythonScript (2)

PeterJones

@Lycan-Thrope ,

You appear to be right.

I guess I had only experimented with local-config Notepad++ instances, or something changed.

The next edition of the User Manual will say,

cloud\choice file: If this folder and file are present, the file contains the path to the Cloud folder. This config file is created when you define the Cloud preferences. If you are in a normal installation, this config file will be %AppData%\Notepad++\cloud\choice; if it is deleted from there, Notepad++ will not look for <installdir>\cloud\choice. If you are in a portable / local configuration (doLocalConf.xml exists), it will be in <portable>\cloud\choice.

Lycan Thrope

@PeterJones ,

Thanks for those clarifications. I’m glad I’m not going mad. :)