Symlinked preview CSS doesn't work?
Completed
I've found, to my surprise, that I can't use a symlinked CSS file as a preview stylesheet for nvUltra. I tried to move my customized stylesheet into another directory (I'll explain why later) and symlink it back into the nvUltra CSS directory, and while I can select the symlink from the nvUltra Preview CSS menu, the styles don't apply. Using an identical copy that's not a symlink, it works fine. Is this intended behavior, or a known issue?
Here's some detail, to either prove that I'm not crazy or hopefully to pinpoint something I've missed:
[1101 12:39 Library/Application Support/MultiMarkdown Software/CSS/] ls -l Custom*
-rw-r--r-- 1 xxxxxxxx staff 8256 Apr 17 12:33 Customized-actual-file.css
lrwxr-xr-x 1 xxxxxxxx staff 44 Apr 17 12:30 Customized.css -> /Users/xxxxxxxx/.dotfiles/src/Customized.css
The stylesheet works if I choose "Customized-actual-file.css" but not if I choose "Customized.css".
The symlink is valid and the files are identical:
[1102 12:39 Library/Application Support/MultiMarkdown Software/CSS/] ls -l Customized-actual-file.css /Users/matthias/.dotfiles/src/Customized.css
-rw-r--r-- 1 xxxxxxxx staff 8256 Apr 15 20:31 /Users/matthias/.dotfiles/src/Customized.css
-rw-r--r-- 1 xxxxxxxx staff 8256 Apr 17 12:33 Customized-actual-file.css
[1103 12:43 Library/Application Support/MultiMarkdown Software/CSS/] diff Customized-actual-file.css /Users/matthias/.dotfiles/src/Customized.css
<no diff>
(If it's not obvious what was going on here, I'm trying to move my nvUltra customized themes and CSS into a repo where I keep config files that I want to use across multiple machines. Ordinarily I symlink files from that repo to the actual location, and it usually works fine. If this isn't fixable, I'll have to add an option to copy some files instead of linking.)
-
The issue is not symlinking, it's trying to access a file that nvUltra does not have access to (due to macOS sandboxing).
0 -
Oh, of course! I didn't realize nvUltra was sandboxed.
I'm inferring from the fact that you didn't mention a workaround that there will be no workaround from the app, so I'm looking at alternatives. I'm not sure whether the issue is that nvUltra isn't set up to ask for home directory access (because why would it), or if the sandbox blocks access to dot files. I can experiment.
Thanks for the explanation — and again, please get to 1.0 so I can give you money! I already know nvUltra is worth far more to me than you're likely to charge for it.
0 -
(Of course, the fact that the nvUltra configs are in `Group Containers` ought to have tipped me off...)
0 -
Applications should not generally be asking for permission for your entire home directory (starts to defeat the purpose of sandboxing....)
Sandboxing doesn't block dot files per se, but it restricts access to folders that "belong" to the App (e.g. certain folders in the Library), or other specific folders (such as Downloads, Pictures, Music, Movies).
There are technically some ways around this, but I don't recommend them and they would make me nervous that if there were a bug in nvUltra it could cause havoc, so I won't describe them.
And yes, we want to get to 1.0 soon as well! We're working out a few kinks related to App Store issues and hope to resolve those soon!
0 -
> (Of course, the fact that the nvUltra configs are in `Group Containers` ought to have tipped me off...)
Not everyone understands what that means, but yes.... :)
0 -
Certainly not, but I do!
0
Please sign in to leave a comment.
Comments
6 comments