On Tue, Mar 12, 2019 at 2:55 PM Rob wrote:
> Well, that certainly makes sense, thanks!
Glad to hear it.
> Now that I think of it that way, it reminds me that I do much the same
thing w/ LaTeX commands (macros) for repeatable blocks of text.
Excellent.
Edward
--
You received this message
Well, that certainly makes sense, thanks!
>
> You typically don't need clones if your language can define a function.
> Just call the function.
>
> Edward
>
Now that I think of it that way, it reminds me that I do much the same
thing w/ LaTeX commands (macros) for repeatable blocks of text.
On Sun, Mar 10, 2019 at 7:18 PM Rob wrote:
> Thanks, Edward. However, I don't understand why it matters that html and
> css 'lack functions'.
>
You typically don't need clones if your language can define a function.
Just call the function.
Edward
--
You received this message because you are
Thanks, Edward. However, I don't understand why it matters that html and
css 'lack functions'.
Imo, in your use case it's ok to use cross-file clones. The normal rules do
> not apply because html and css lack functions.
>
>
Thanks to everyone who 'weighed in' with comments; it appears that in
As I understand it, using cross-file clones is somewhat safer if the clones
are *underneath* @file/@clean nodes and not the @file nodes themselves. (I
got myself into a pickle before by cloning @file nodes under different
@path parents; don't remember the specifics now).
Matt
--
You
On Sat, Mar 9, 2019 at 11:00 AM Rob wrote:
> Suppose I have a xxx.leo file in which I write multiple web pages (or
> other document types, same question).
>
>- Each document is a separate @file (or @clean) external file.
>- Inside each web page are sections (nodes with or without
I have used html templates before in the context of CMS systems which
already had the templating engines in place and would automatically replace
the templates with the substitutions. However, that's not really what I
need. I create html 'fragments' in Leo which are then copy/pasted into
other
On Sat, 9 Mar 2019 10:49:19 -0800 (PST)
vitalije wrote:
> For HTML and CSS there are a lot of pre-processors for example: pug
> for HTML and sass for css. Both of them have more than one way to
> define some section once and use it anywhere you like it. Basically
> you write source files in pug
Hmm, unfamiliar with those tools, will check them out. Thanks!
On Saturday, March 9, 2019 at 1:49:19 PM UTC-5, vitalije wrote:
>
> For HTML and CSS there are a lot of pre-processors for example: pug for
> HTML and sass for css. Both of them have more than one way to define some
> section once
For HTML and CSS there are a lot of pre-processors for example: pug for
HTML and sass for css. Both of them have more than one way to define some
section once and use it anywhere you like it. Basically you write source
files in pug and sass format, and then compile those source files into the
Thanks for clarifying, Vitalije. Yes, I'm the only one who would edit them
and I don't use external editors, so clones would certainly be the easiest
way to do that. I use \include{file.tex} for LaTeX documents, but don't
know about a similar mechanism for html or css documents. Any of the
>
>
>- I could easily do that with cloned nodes. However, we are strongly
>encouraged *not* to create cross-file clones.
>
> Any suggestions on how to accomplish that without using clones?
>
>
As long as you are not using any other editor to edit those files and you
are the only
Suppose I have a xxx.leo file in which I write multiple web pages (or other
document types, same question).
- Each document is a separate @file (or @clean) external file.
- Inside each web page are sections (nodes with or without children)
that all need to be the same content (perhaps
13 matches
Mail list logo
