Allan Odgaard wrote:
On 20 Apr 2008, at 00:28, Sherwood Botsford wrote:
[...]
Suppose that markdown was clever enough to reference an external
file (in .markdownrc of course) for the resolution of LABEL.
Here’s a simple shell script to convert all markdown to HTML and using a
shared referenc
Lou Quillio wrote:
Suppose that markdown was clever enough to reference an external
file (in .markdownrc of course) for the resolution of LABEL.
NOW when I re-arrange the universe, I only have to change the reference in
this one file, NOT in every file that references it.
Good idea to token
On 20 Apr 2008, at 00:28, Sherwood Botsford wrote:
[...]
Suppose that markdown was clever enough to reference an external
file (in .markdownrc of course) for the resolution of LABEL.
Here’s a simple shell script to convert all markdown to HTML and using
a shared references file:
cd ~/M
> Suppose that markdown was clever enough to reference an external
> file (in .markdownrc of course) for the resolution of LABEL.
>
> NOW when I re-arrange the universe, I only have to change the reference in
> this one file, NOT in every file that references it.
Good idea to tokenize URL paths
One of the things I'm coming up against. Maintaining a non-small
web site with many internal links is a pain.
Consider:
Suppose that at one point I have
site/
Images
Business
Home
...
Later the site gets more complex, and Images has a bunch of sub
directories.
site/
Images
hea
