Leo across devices

[Micah Joel]

In my use case, I bounce between a MacBook laptop, iOS phone, and Android tablet. If I want to have read/write access to a set of leo files across all three, what are some scenarios people are currently using?

If a leo file is hosted on a sync service like dropbox, how does leo-editor handle the case then the on-disk file changes out from underneath the running app?

I have more questions, but I'll start with these two. :)

Micah

[Matt Wilkie]

There's a leo_cloud plugin written by Terry Brown. Link to Github source here for quick reading but it will be in your local install (don't need to download).

I used it for a couple years happily. I stopped because my Dropbox habits changed and not because of any particular issues with the plugin.

-matt

[jkn]

I do something like this, but with Owncloud/Nextcloud  rather than dropbox.

In theory, things should I think be fine - but I have hit occasional problems and TBH I am not convinced that things are seamless. I don't find the prompts that Leo gives when it detects this kind of thing very helpful, and I have hit what seems (to me) be be occasional mis-syncs. Usually this is related to 'derived' files using @file etc. I have another, more standard, file editor that I use in a similar way (for a daily diary file), and that seems to be pretty solid.

It is possible that my problems are caused by use of both Windows and Linux machines, and the way timezones are setup differently on some of my machines.

Edward has given some pointers on the general 'reloading from disk' etc. situation in the past, but like I say, it has never seemed quite solid to me. My current workflow is basically to ensure I am only editing on one machine at a time. This is liveable-with for me ATM, but I would like to have more confidence in the general setup.

I would appreciate more input from others on this topic.

    Jon N

[Matt Wilkie]

I do something like this, but with Owncloud/Nextcloud  rather than dropbox.

In theory, things should I think be fine - but I have hit occasional problems and TBH I am not convinced that things are seamless. I don't find the prompts that Leo gives when it detects this kind of thing very helpful, and I have hit what seems (to me) be be occasional mis-syncs.

As I understand it, Terry's plugin uses the cloud provider API to update the contents, thereby sidestepping issues with filesystem automatic syncing changing contents without Leo noticing the change. Note: This might be dropbox only. I'm not sure plugin knows about other provider APIs.

The safe method to do it manually is turn off or pause the syncing daemon while working and then resume it after done.

On the same topic: it's risky to put a Git or Hg repo in a Dropbox or Nextlcoud monitored folder. That way corruption lies and if it's private repo you might lose all history. I learned the hard way!

-matt

[jkn]

On Saturday, February 29, 2020 at 1:17:11 AM UTC, Matt Wilkie wrote:

On the same topic: it's risky to put a Git or Hg repo in a Dropbox or Nextlcoud monitored folder. That way corruption lies and if it's private repo you might lose all history. I learned the hard way!

Agreed - I have experienced the same sort of thing, with different work. I think many people's eyes light up at the idea ... but it really doesn't work well.