Euphoria
Ticket #719:
new 4.1 defined words' description is not linked to via the javascript search engine.
-
Reported by
SDPringle
Oct 26, 2011
New defined words must be documented to what they are supposed to mean before we release 4.1. Were they obvious I would be able to tell you why we need both LONG32 and BITS32. I don't. The new defined words are:
X86, X86_64, ARM, BITS32, BITS64, LONG32, LONG64
Details
1. Comment by mattlewis
Oct 26, 2011
These are documented already in refman_2.txt under the heading "Architecture Definitions".
2. Comment by SDPringle
Oct 26, 2011
type them in to the javascript search bar. They don't come up.
3. Comment by SDPringle
Nov 16, 2011
You can look up things like 'while' and 'for' and 'HIGH_BITS'. These are not contained in EUPHORIA source files like the routines or constants are.
4. Comment by SDPringle
Nov 27, 2011
I have tried to put anchors into the text to make this work. It is an at symbol, left bracket, EU4, pipe and then a right bracket. If I type it here, it shows up invisible. It doesn't make it into the search engine. Things in .e files and headers get into the engine.
5. Comment by SDPringle
Nov 27, 2011
This is also a problem in 4.0, so I am remarking this as 4.0.
6. Comment by ne1uno
Nov 27, 2011
double brackets, @symbol|link double end bracket
leave link blank for invisible link any anchors should make it into the index by creole
[[@symbol|]] invisible link
[[@symbol|visible link]]
preview doesn't seem to work in the firefox I use here, the forum or wiki, but it does work in pasty.
7. Comment by DerekParnell
Nov 27, 2011
I'm a bit perplexed as to what the invisible link idea is supposed to achieve, because it is invisible there will never be anything for someone to click on, so why have it? Even if you want it to cause a search hit, where is the link supposed to go to when the user clicks the search result?
Or is it that the invisible link is expected to be associated with the most recent heading processed?
8. Comment by ne1uno
Nov 27, 2011
sorry, brain crash... I gota stop working from memory. it is
@[anchor|]
the browser is sent to after where the anchor is, instead of after the heading. so you do actually see the heading at the top of page.
9. Comment by SDPringle
Nov 27, 2011
The question is how do I make an anchor indexed by the search engine.
10. Comment by DerekParnell
Nov 27, 2011
I'm still unclear. Let's say that we get the anchor appearing in a search result ...
- What is to be actually seen by the user in the search result?
- Where does the user go to when they click the search result - the location of the anchor tag or the current heading that the tag appears in?
11. Comment by ne1uno
Nov 28, 2011
I assumed the anchors were naturally part of the index created but never actually verified it in the official html,
I've been patching a local copy of creole.ex to output it's bookmark sequence to a file and using that to make the eu4.chm Index.hhk
the anchors are in there, but probably skipped over when creating key_index.html for the official docs.
looks like a feature request now.
look in refman_2.txt
@[then|] @[else|]
@[elsif|]
=== if statement
this is so all keywords and builtins could be linked somewhere. though probably there is not 100% coverage yet.
GitHub