Re: [tw] Re: Saving in Safari

2017-07-24 Thread Eneko Gotzon
On Mon, Jul 24, 2017 at 1:33 PM, Jeremy Ruston wrote: > I’ve been studying the “Downloads Overwrite Existing Files” sample… >> > ​Thank all you ​for all your work. ​Take care. -- Eneko Gotzon Ares enekogot...@gmail.com -- You received this message because you are

Re: [tw] Re: Saving in Safari

2017-07-24 Thread 'Mark S.' via TiddlyWiki
Hi Ton, Not sure what you're saying. Yes, you can change the download directory. But I keep my TW files in directories far away from the download directory. So I would either have to change the downloads directory whenever using TW or constantly be moving downloaded files out of the TW

Re: [tw] Re: Saving in Safari

2017-07-24 Thread @TiddlyTweeter
Ciao Ton If you have only one TW, or are happy to have them all in one dir, this will work great. I sometimes feel spoiled with Tiddlyfox in FF with 7 TW all in very different places. But *SHOULD* I? Or should I feel pissed-off that in the future keeping MY structure is gonna become a PITA?

Re: [tw] Re: Saving in Safari

2017-07-24 Thread @TiddlyTweeter
Ciao Mark S. Be glad you can get it to save to a (sort-of) user designated directory ... the last implementation *only* allowed saving to the default download directory. I'm referencing here the actual add-on at Chrome Webstore

Re: [tw] Re: Saving in Safari

2017-07-24 Thread Ton Gerner
Hi Mark & All, > If it only saves to a sub-directory of the downloads directory, that would be inconvenient. Linux Mint 17.3, Chrome 59, Extension "Downloads Overwrite Existing Files". Chrome saves to my own directory set in Advanced settings. Cheers, Ton -- You received this message

Re: [tw] Re: Saving in Safari

2017-07-24 Thread 'Mark S.' via TiddlyWiki
The current download saver promises to remember the last download directory. But the chrome extensions may limit you to the download directory and subdirectories. At least one of those in the link says .. Absolute paths, empty paths, and paths containing back-references ".." will be ignored.

Re: [tw] Re: Saving in Safari

2017-07-24 Thread Jeremy Ruston
> It’s not quite that bad: TiddlyFox will stop working in the latest versions > of Firefox, but those download overwriting plugins will still work. > > > Do you have links for those plugins?, that are tested with latest FF or > nightly FF? I’ve been focusing on Chrome extensions, on the basis

Re: [tw] Re: Saving in Safari

2017-07-24 Thread @TiddlyTweeter
Ciao PMario & Jeremy I believe Jeremy was referring to the Chrome Overwrite Saver IF its a Web Extension that would be good news. *If its an "app", it too will be retired if Google go ahead

Re: [tw] Re: Saving in Safari

2017-07-24 Thread PMario
On Monday, July 24, 2017 at 11:22:25 AM UTC+2, Jeremy Ruston wrote: > > In addition you should note that ALL standard browsers will cease simple > overwrite saving by early 2018. > > > It’s not quite that bad: TiddlyFox will stop working in the latest > versions of Firefox, but those download

Re: [tw] Re: Saving in Safari

2017-07-24 Thread Jeremy Ruston
Until sometime in the last few months, Safari didn’t support directly downloading changes; instead one had to right click and save a base64 generated URL. Safari does now handle the downloads properly, so the standard HTML5 fallback saver now works OK on Safari. > As far as I am aware, Safari

[tw] Re: Saving in Safari

2017-07-24 Thread TonyM
Sergie, I have not attempted to get tiddlywiki to save on safarie but I have just installed firefox and the plugin tiddlyfox on my mac mini and that works. Also I installed node.js on the MAC and that should work from within safari, Regards Tony On Monday, July 24, 2017 at 1:04:40 AM UTC+10,

[tw] Re: Saving in Safari

2017-07-23 Thread Sergei Gerasenko
The problem is that Safari appends -1, -2, etc on each save, which is bad when working with TiddlyWiki. I would like the original wiki file to be overwritten. On Sunday, July 23, 2017 at 10:02:43 AM UTC-5, Sergei Gerasenko wrote: > > Hi, > > I'm running Safari 10.1.1. According to this Saving