Hello all,
I've been using Virgil's Notepad++ code to easy-reference the wiki. However, when using refread and/or refwrite, it directs to a "nonexistent" page.
Given that this page is already specific to the CRPL subsection, could it include a link to the CRPL reference (http://knucklecracker.com/wiki/doku.php?id=crpl:crplreference) page?
Currently it's largely a dead end, unless you go back to the wiki's global start page, or have recently been browsing other commands.
Of course, it's a minor change (I would think), but seemed worth a mention.
I really don't understand. Is there problem in the wiki, the page links, or somewhere else? And what needs to be done to fix it?
Can you provide a sample that works and a sample that doesn't?
In the forum, under Even NEWER CRPL Docs (http://knucklecracker.com/forums/index.php?topic=12428.0), Virgil gave this code for easy-referencing the wiki from Notepad++:
http://knucklecracker.com/wiki/doku.php?id=crpl:docs:$(CURRENT_WORD)
This works well. The issue I have is that, while it works wonderfully for a command such as Delay or GetScriptVar; if you use it on refread (<-! in the code) or another name which doesn't exist on the wiki, it brings up a page such as this (http://knucklecracker.com/wiki/doku.php?id=crpl:docs:triggerer). (That page found by referring to a fictional command.)
I was wondering if it is possible to add a link to that page (I think it is specific to unfound CRPL commands?) to the CRPL reference (http://knucklecracker.com/wiki/doku.php?id=crpl:crplreference).
The problem is more complex, I think. The wiki does not support page names in the format "<-!"
So neither you nor I can create that page.
You will see that your fictional triggerer command allows you to create the page, the Refread page does not
It may be possible by fiddling with aliases or some other workaround, but I don't exactly have a clear idea if it is possible at all.
I feel your pain, but technology is at it's limits here. :)
Just to be clear, do you want a wiki page with the following URL:
http://knucklecracker.com/wiki/doku.php?id=crpl:docs:<-!
Because (for me anyway) it gives the option to create the page. I haven't tried saving the page yet because the top-right tab thing says crpl:docs instead of crpl:docs:<-!, and I worry that saving it will overwrite the docs index.
Quote from: planetfall on July 23, 2016, 09:42:32 PM
Just to be clear, do you want a wiki page with the following URL:
http://knucklecracker.com/wiki/doku.php?id=crpl:docs:<-!
Because (for me anyway) it gives the option to create the page. I haven't tried saving the page yet because the top-right tab thing says crpl:docs instead of crpl:docs:<-!, and I worry that saving it will overwrite the docs index.
That's precisely the point. You can't create http://knucklecracker.com/wiki/doku.php?id=crpl:docs:<-!
As I said, it's not major, but it might be useful to link to the reference.
Since the Notepad++ language definition doesn't highlight real commands when typed, this might also help when someone types GetAllEnemyUnits, and wonders what went wrong.
I'm suggesting that "Command not found" might have a link to the reference. No more, no less.
If you can figure a way to do it, I'd be more than happy to provide you assistance implement it. If you think a wiki update will fix it, then you (as any other user) should have access to update the wiki pages.
The issue is that's a generic "page not found," not "command not found." This (http://knucklecracker.com/wiki/doku.php?id=cw2:FakeWikiPage) gives the exact same page. In order to modify that message, and to make a special case for crpl:docs:FakeCommand that doesn't show for a nonexistent page elsewhere on the wiki, I'd suspect one would require the ability to modify the wiki software.
In that case it's probably more trouble than it's worth. I had thought that page to be specific to the CRPL namespace of the wiki.
Well, maybe this might partially sove the problem for the unsupported character name pages.
I just created the page: http://knucklecracker.com/wiki/doku.php?id=crpl:docs
See if your original problem is now resolved?
No such luck.
Never mind, it's not a major issue.