On Fri, 10 Apr 2015 13:34:35 -0700 (PDT)
Largo84 <[email protected]> wrote:
> Sorry for the Star Wars reference, I couldn't resist.
>
> I've been trying to follow the conversations about clones and
> bookmarks (or clones vs bookmarks), and it occurs to me that what
> attracted me to Leo to begin with was clones. However, I almost never
> use clones the way Edward uses them as a way to view a node out of
> it's @file context. What I like about clones is the ability to
> actually duplicate text and have it update automatically wherever it
> exists. I often create documents (mostly using LaTEx) that use a
> block of text repeatedly throughout. These text blocks become clones
> so that if I need to change or update them, I only need to do that
> once. Bookmarking won't do that.
True, bookmarks won't do that. I suspect your use of clones is what
many people find attractive about them. I'm not sure they're 100% safe
for that kind of use, clones across multiple external files, if you're
doing that, seems to have dependencies on file write order etc.
I would use
\newcommand{\ltext}{Long piece of text I don't want to write all the time}
Blah \ltext and then \ltext before \ltext.
for the LaTeX case.
Cheers -Terry
> I say all of that to suggest that I hope that clones don't go away to
> be replaced by something else that won't accomplish that. Maybe I'm
> the only one who uses clones in this way, but it has become an
> invaluable tool in my document creation workflow. Best regards,
>
> Rob.......
>
--
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/d/optout.
