[Pmwiki-users] Feature Suggestion

John Rankin john.rankin at affinity.co.nz
Sun Mar 23 16:10:58 CST 2003

The encyclopedia has something similar as a local customisation, using the =
[[#anchor]] markup.

1. On the same page
Using the footnote markup as a guide, if an author writes [^#abc^] and =
somewhere on the page there is a reference to [[#abc]], the text between [[=
#abc]] and the end of the line is inserted in place of [^#abc^]. For =
example, we are listing external references at the bottom of a page, and =
using [[[^#abc^] text]] in the body of the page.

2. Across pages
We have a [[para:pagename#idref]] that inserts the paragraph named [[#=
idref]]. If #idref is omitted, it inserts the first paragraph. This works =
within groups and across groups.

This seemed to us a natural extension of both the [[#anchor]] and [^=
footnote^] markup. (If [[#idref]] is missing, it inserts 'idref not found')=
John Rankin
On Saturday, 8 March 2003 11:27 AM, Jonathan Scott Duff <duff at cbi.tamucc.=
edu> wrote:
On Fri, Mar 07, 2003 at 04:10:38PM -0600, Patrick R. Michaud wrote:
> To avoid the "line oriented" markup that Scott proposed, I'd counter-=
> markups such as:
>    [%Abbrev0 http://www.replacement.org/url/prefix0%]
>    [%Abbrev1 http://www.replacement.org/url/prefix1%]
>    =3Dintermap Abbrev0 http://www.replacement.org/url/prefix0
>    =3Dintermap Abbrev1 http://www.replacement.org/url/prefix1
> or something along these lines. =20

That first one works for me.

> I think this can probably be handled=20
> as a local customization w/o modifying pmwiki.php, although it
> may require some tricky handling of the $LinkPatterns array to make
> sure the patterns stay in the correct sequence.

Why not modify pmwiki.php and keep intermap.txt in the same format?

> For shortcuts:
> On a similar thought, and starting down a very slippery slope that
> I've been quite reluctant to examine, does PmWiki need author-defined=20
> generic abbreviation capabilities?  (Perhaps this is what Scott
> meant by "shortcuts"?) =20


> While writing the documentation
> trail pages and other pages I've sometimes found myself wishing to be=20
> able to simply write something like [%trail%] and have that be=20
> automatically converted to %trail%<<|PmWiki.DocumentationIndex|>>,=20

Heh, I was looking at those pages today and wishing that exact thing.

> but not have to hard-code this as a local customization to PmWiki.
> I.e., enable full-text shortcuts to be defined within a wiki page such =
> PmWiki.GroupHeader (as opposed to just intermap shortcuts=20
> But I'm *very* worried that this "macro" capability will be just the=20
> beginning of a very slippery slope that will ultimately lead to the=20
> exclusion of naive authors--i.e., in addition to learning the=20
> TextFormattingRules, they'd also have to be aware of all of the=20
> author-defined custom markups that were generated.

Hmm. Are you worried that they'll see the funny markup and wonder
"what's this?" Are you worried that they won't be able to find an
answer? What do you mean by "they'd have to be aware of all

Jonathan Scott Duff
duff at cbi.tamucc.edu

Pmwiki-users mailing list
Pmwiki-users at pmichaud.com

More information about the pmwiki-users mailing list