Expose underlying wiki markup on new support pages

Discussion related to "Everything" 1.5.
lifu
Posts: 49
Joined: Tue Jun 15, 2021 11:04 pm

Expose underlying wiki markup on new support pages

Post by lifu »

I've noticed that some of the support pages have been migrating to https://www.voidtools.com/support/everything and I've also noticed that the elements in the HTML have ids and classes that start with "wiki", which makes me think that this is wiki markup being compiled into static HTML.

If so, would you please consider putting the raw wiki markup into a
<script type="text/plain">…</script>
element so it can easily be used to do things like converting it to Markdown with tools like pandoc? Converting HTML is always so much messier.

I'd really appreciate it.
void
Developer
Posts: 20362
Joined: Fri Oct 16, 2009 11:31 pm

Re: Expose underlying wiki markup on new support pages

Post by void »

https://www.voidtools.com/support/everything uses my own wiki-like language.

I've updated makevoidtools which includes the most recent raw wiki.
I'll update this again when it's ready for translating.

I will consider embedding the raw wiki in the HTML.

Claude AI is really good at making scripts to convert the raw wiki into anything you like.

Everything 1.4 User Guide / Manual as HTML/PDF / Offline Help
lifu
Posts: 49
Joined: Tue Jun 15, 2021 11:04 pm

Re: Expose underlying wiki markup on new support pages

Post by lifu »

void wrote: Wed Sep 16, 2026 1:13 am https://www.voidtools.com/support/everything uses my own wiki-like language.

I've updated makevoidtools which includes the most recent raw wiki.
I'll update this again when it's ready for translating.

I will consider embedding the raw wiki in the HTML.
Much appreciated.

void wrote: Wed Sep 16, 2026 1:13 am Claude AI is really good at making scripts to convert the raw wiki into anything you like.
Yeah I know, but I'd have to redo that every time there's an update, and it's just easier to have something consistent that I can simply use regular 'ol dumb scripts to convert.
lifu
Posts: 49
Joined: Tue Jun 15, 2021 11:04 pm

Re: Expose underlying wiki markup on new support pages

Post by lifu »

void wrote: Wed Sep 16, 2026 1:13 am https://www.voidtools.com/support/everything uses my own wiki-like language.
Hey, are you aware that aliases aren't currently being fully populated?

https://www.voidtools.com/support/every ... _functions

The id for them all is there, but only some of them are being listed. Here's an example, the
location:
function, which has
pp:
,
loc:
,
path-part:
, and
pathpart:
. Only the
loc:
alias is listed:

Code: Select all

<span id="pp"></span><span id="loc"></span>
<span id="path-part"></span><span id="pathpart"></span>
;location:
Matches files and folders whose parent folder path contains the specified text.

The location is the folder that contains the item (for example, the location of `c:\windows\notepad.exe` is `c:\windows`).

Aliases: `loc:`

For example:
`location:c:\windows` = matches items inside `C:\Windows` or its subfolders (does not match the `C:\Windows` folder itself)
`location:"c:\program files"`
`location:win` = matches items whose parent path contains "win" (for example, `c:\windows\notepad.exe`)

See also: [[#full-path|full-path:]]
Hopefully this wasn't an intentional decision, since it's going to make it more difficult for me to refer back to the documentation on how certain things in my macros function if the alias I'm using is no longer listed.
void
Developer
Posts: 20362
Joined: Fri Oct 16, 2009 11:31 pm

Re: Expose underlying wiki markup on new support pages

Post by void »

I want to avoid bloating aliases on the support wiki.
partpath: and pp: only existed in the Everything 1.5 alpha.

All aliases can be found with the span ids.

All aliases can be found here:
Search Functions
I will maintain this page too.