Hi, Keith.
Ordinarily I would be game to do this but unfortunately I’m a Mac App Store customer (it just seemed more convenient). I note in the beta section that its not recommended that those like me download it.
Tom S.
Hi, Keith.
Ordinarily I would be game to do this but unfortunately I’m a Mac App Store customer (it just seemed more convenient). I note in the beta section that its not recommended that those like me download it.
Tom S.
Hi Tom,
Ah, okay. Actually as of 2.0.6 it won’t make any difference - Mac App Store customers will be able to download betas too, because 2.0.6 will store your receipt in a special folder that the regular version will be able to check, but until 2.0.6 hits the Mac App Store it would be awkward to get it working.
Thanks,
Keith
Thanks, Keith. I’ve had this same problem and was just living with it. Nice to have the answer.
all best
David
Would it be possible to set a sticky preference in the <Add Link…> box to ? I am usually copy-pasting URLs from my browser into Scrivener, therefore having to change the default tick box to each time I add a URL is not really handy.
You don’t need to do that - if there is already an “http://” at the start of the pasted-in URL, Scrivener won’t add it again.
Been meaning to come back to this thread to report that this doesn’t work, at least not for me. Though I have carefully made Command-K (in my case) into the shortcut for both Add Link… AND Edit Link… (while of course assigning the old command-K function to another shortcut), nonetheless when I start in a project, I must first “baptize” the function by clicking on the Edit menu, otherwise the shortcut will not do anything. After that first-time menu click, though, the shortcut works fine. As before. It’s not a big deal, of course. And maybe this weirdness will go away in Lion. So: Just FYI.
Cheers
David
And you’re using the beta version, not 2.0.5, as explained above?
Oops, sorry. I didn’t grasp that that distinction was crucial. I’m on 2.5, will now switch and report back.
Apologetically
David
Oops, sorry. I didn’t grasp that that distinction was crucial. I’m on 2.5, will now switch and report back.
Apologetically
David
Should have said I WAS on 2.0.5.0, of course. I am now, as instructed, on 2.0.5.5. And the problem is gone. Thanks Keith, as ever.
David