any ideas Rob?
The question is why is it looking in the
lib-bkp folder.
:point_up: January 15, 2017 3:34 AM
Yip, if it is an embedded package, with just contents, Chocolatey will wipe out the folder on uninstallation
Chocolatey is a tad bit smarter than that. On uninstall it removes all unchanged files and leaves files that have changed. If you uninstall with force, it will wipe all files, including files created and user changed files. Same goes for upgrade.
@RickStrahl @gep13 chocolatey/choco#1139 for the uninstall issue - it looks like something was running and locking the folder, so when it moves the files to lib-bkp and later attempts to delete them, it fails because the locked files are now there.
:point_up: January 15, 2017 4:26 AM for the push hang. I push up 7MB and don't run into this very often. Let me see if maintenance can clear this up.
@ferventcoder I did run from a local folder install for testing though - not sure if that would make a difference. I give it another try now after reboot.
This is a portable install and shouldn't need any admin rights to install. No admin tag in the nuspec.
@ferventcoder @gep13 Shouldn't I be able to install from a non-elevated prompt with this portable install?
The default installation directory is locked down to admins only with modify access
we highlight that in the more options section oh the install page. Also on the security page
@ferventcoder Ok, fair enough. I was under the impression that Chocolatey could run under limited rights, because that's what several people were asking for. So when I don't specify Admin rights on the installer does it run the installer under Admin as well or under user account? I thought this was the whole point of a portable, non-admin capable install.
We probably should move this over to @chocolate.org group :-)
In 1.1.20 of Markdown Monster. No more @Razor code block required to figure out the file name.
That feature needs a little more work - like it should also capture a title from FrontMatter.
will give that a try as well
hmm, when I try the above, I get...
signing off for just now, but will try again later
thanks again for all your help!
Ah yes, it's in 1.1.20.1 (from Web site only)
it's actually very naive
With regards to that issue, I noticed that there is no concept of opening a folder, which makes my point loose a lot
Any thoughts on adding a concept folder/project concept to MM?
I'm not sure if I want to go down the path of building a new 'editor' that treats folders like projects for the main editor. That adds a lot of complexity. Maybe in the future. But again an Addin can easily handle that with keeping a base folder and it's own set of configuration settings for each 'project'.
There have been a bunch of requests for adding folder display support. I think it's something that I might do a little later for a 2.0 version, but for now I want the main editor to focus on core editing related stuff.