On Wed, 23 Oct 2013 11:04:26 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Wed, Oct 23, 2013 at 10:54 AM, Terry Brown <[email protected]>wrote: > > > Current defaults > > > > @string shadow_prefix = x > > @string shadow_subdir = .leo_shadow > > > > > so editing README.TXT with @shadow will put .leo_shadow/xREADME.TXT > > *in the same folder* as README.TXT. Don't want it there, if @shadow is > > the key to collaboration, I don't want to make weird .folders in the > > shared space. > > > > So @string shadow_subdir = ~/.leo/shadow > > > > works ok, but now ~/.leo/shadow/xREADME.TXT from one project will clash > > > > with the same from another project. > > > > So can we hash the file content and include that in the file name in > > shadow_subdir? The caching mechanism already does something like this. > > > > I agree, that *if* .leo_shadow folders are unpleasant then something like > this is needed. > > A cleaner solution might be to have a single root .leo_shadow directory, > and compose subdirectory names within it. > > I'll consider it if there is a request from somebody who actually needs it. :-) um, me? The timing vs. the other team usage thread was just coincidence, I'm using @shadow to edit shared .R files and I don't want to make .leo... folders in the shared space. Not urgent though, the collision issue isn't likely to bite me right now, so @string shadow_subdir = ~/.leo/shadow works for now. I think file content hashes would be more robust than any attempt to generate paths in the shadow folder. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
