See also Compiled Website TODO
NOTE - This whole page is made into a block of code, because I think perhaps I had inline examples which can't translate into a non-Compiled Website format.
This is duplicating some of the content:
- `\a` - `\007`
- `\a` - `\007`
- `\a` - `\007`
- Change the reference to a version number to current
- copy cdv() into a function which will update the `current` symlink
- could link
- <br>won't link because of the br tag. Duuh, there's no closing tag, and it's expecting one. Hanging html tags should be valid and not exempt the rest of the line.
=== lists make life hard for paragraphs ===
# Don't embed libraries!
-- Give a simple list of those dependencies, and link to their library-addon page.
# .. or always keep embedded libraries up-to-date!
-- An addon's source code repository should just fetch the current release for every library, and the author should test every new release with latest-version libraries.
How does a user recover from this madness?
Well, we can't.
Hack on each addon to link to the latest version of each library? This can cause major problems when the addon is expecting some specific library version or modification. See World of Warcraft AddOns via repositories for the nightmare I had.
It's best to bug the author about not using embedded libraries at all.
=== can't make sections with certain content ===
Try making an h1 with: `10.10 2011-07-07`
=== plain links in lists not working right ===
- A listing of stuff at the bottom of http://example.com/zfs-fuse.net
- Maybe https://drwetter.eu/old//blog/zfs_under_linux.en.html
- [http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide] ZFS Best Practices Guide
- http://example.com/zfs-fuse.net/wiki
-- If I need docs change permissions, ask: http://example.com/zfs-fuse.net/contact-info
however this works:
- A listing of stuff at the bottom of http://example.com
- Maybe https://drwetter.eu/old//blog/zfs_under_linux.en.html ?
-- Also quite "interesting" in terms of computer forensics is the [http://www.opensolaris.org/os/community/zfs/docs/zfs_last.pdf copy-on-write] mechanism. That means with carving techniques you'll probably find all "old" data unless the logic in ZFS decided to overwrite it at a certain point.
- [http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide] ZFS Best Practices Guide
- http://example.com/zfs-fuse.net/wiki
-- If I need docs change permissions, ask: http://example.com/zfs-fuse.net/contact-info
=== paragraphing is fucking up ===
If I have some text.
I can have a blank line and it is respected.
But if I have two spaces above here.
This one blank line is not respected!
I first saw this in bc shaman healer thoughts. I'm having trouble reproducing it. Argh!
=== expand tt ===
I cannot do (`man mount`).
=== some urls break lists ===
see hosting. .eu .pl .ru ?
=== questionmarks break links ===
[http://www.gp32x.com/board/index.php?/topic/58326-paintown/]
=== odd linking within pre blocks ===
[http://www.angstrom-distribution.org angstrom-distribution.org]
[http://www.linuxtogo.org/gowiki/Angstrom wiki] (APatheticCamelCaseWiki)
[http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users users mailing list]
[http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel developers mailing list]
=== . ===
http://www.mess.be works, but [http://www.mess.be] doesn't.
=== Italicization is funny ===
Dark tan / orange / gold:
Should not have italicization!
=== odd page names ===
Brackets: Quaker(R) Oatmeal Apple Crisp
HTML entities: Quaker® Oatmeal Apple Crisp
=== section html isn't working correctly ===
Not unexpected, but check out compiled website demo and go down the page. Notice how some sections begin bleeding out of the template.
=== auto-linking isn't working when an inner word exists ===
ruby software testing
ruby-software-testing
=== lists aren't being merged correctly ===
one and two are merged, but three isn't.
- one
- two
- three
=== fix list nesting ===
It should go down by two, but it's only going down by one.
- one
-- two
--- three
- FIXME: one
=== fix the table to re-add the left-hand dashed line ===
My dashed line on the left-hand side isn't appearing!
* My div stuff hasn't been figured out?
* I'm not using [[html tidy]] am I?
=== investigate the paragraph regex on plain links ===
My separator regex isn't being used correctly for plain links. For example, the ending `es` is being omitted from the code!
http://example.com/1es
=== remove [ [ and ] ] when the page exists ===
When a new link with [ [ and ] ] is found to exist, the original document doesn't have its [ [ and ] ] removed. Did I code that?
Shit, the {{ and }} was making a page called -and-.
=== new pages don't allow numeric starts ===
- [[2008-11-28-ramblings]]
How in the..
=== Multi-word links should take priority over single-word links ===
Auto-linking was supposed to be prioritizing properly.
- Linux Software
- linux
- Software
- linux-software does indeed exist!
So how come all of the following work as expected?:
- windows software
- compiled website
- compiled website to do
- compiled website demo
==== investigate strange autolinking ====
How come the /first/ occurrence isn't matched wholly?
Linux Software
- Linux Software
<!-- Just here to give some space in the source .asc
-->
= Low priority =
Some of these are just quirks of the way things are done.
=== explore encoding ===
- http://en.wiktionary.org/wiki/尺八
- https://en.wiktionary.org/wiki/%E5%B0%BA%E5%85%AB
The second link is the same as the first, just displayed in the original manner. This ought to be changed so that it's very literally linking to what it is shown as. Right?
=== allow multiple sections ===
A current limitation of sections is that at least one line has to be seen between them.
valid:
= one =
= two =
invalid:
= one =
= two =
This should be straightforward to fix.
=== busted linking ===
An old issue, build a test case and re-check with the new codebase.
- A exists
- B exists
- C does not exist
- A B exists
<nowiki><tt>[[A B C]]</tt></nowiki>
- A is plain text
- B is a link to B
- C is plain text
Also, probably related to the old issue..
This isn't really a big deal, but this should be noted somewhere.
- A exists
- B exists
- C you want to make
<nowiki><tt>[[A B C]]</tt></nowiki>
- A becomes red and the proper link to create C
- B is linked to B
- C is plain text
Last updated 2020-01-22 at 03:28:35
