Reef Turner

@VivianSi233 Please open a new issue following the template, it will be important to include a minimal sample and steps to reproduce as required by the issue template.

I think its far easier to rename the portable "nvda" folder, or copy the contents somewhere new (eg one directory above) than it is to carefully delete only the nvda...

I think the users expectation is fairly arbitrary (for new users / those who haven't created a portable copy for a long time), after entering the path `e:\screenReader` some users...

I think what @Brian1Gaff suggests covers the use cases well: Where `` is all the files in a normal portable install and nvda.exe is a helper that just runs `./nvda_data/nvda.exe`...

That sounds good @Qchristensen, happy for that solution to be implemented.

@cary-rowen No, this isn't currently something we are focusing on. I'm happy to accept a community contributed pull request to address this.

This seems pretty clear. Going to label this as a feature. At this point we are not giving features priority ([see the wiki](https://github.com/nvaccess/nvda/wiki/Triage-process)) instead we will try to group them...

I have tried to explain the distinction on [the wiki](https://github.com/nvaccess/nvda/wiki/Triage-process), but perhaps this is not clear enough? Essentially, we are trying to separate the two. The issues with the label...

@DSkyNC Better to ask on the [NVDA developers mailing list](https://groups.io/g/nvda-devel/topics) to get assistance with these kinds of things. Discussion here should be specific to the GitHub issue.

P3. This seems like it would take a large amount of time to implement, and is not currently stopping primary use cases. It would however be very convenient. @jcsteh Perhaps...