Yes, but I’m speaking of the list in the edit console. It’s scrollable, yes, but as you can tell from the length of the scroll handle there isn’t much to scroll. Just the tags I listed above.
The All Tags list seems to be complete. But I don’t see a way to access the All Tags list for editing.(?)
[Edit:] Just to be sure I deleted my browser cache. But this didn’t change nothing.
[Edit II:] Tried it in another browser (FF) and it‘s the same.
OK, I understand what you mean now. It seems to be limiting the scrolling list to the top 10 tags. However, if you start typing the name of a tag, it will still find it.
I'll have to check to see if we can increase the number of tags shown in the list.
@Tom, OK, the tag list shows all tags now (but you need to scroll) when creating or editing a topic. Check it out and let me know if you see any issues.
Yes, it’s fine. It’s a shame Discourse bumps the topics when you make tiny modifications to them, but that’s just the way it is - the same thing happens if you fix a typo in a topic or the like, but it’s better (I think) to make the site as a whole worthwhile than to worry about a temporary bump of a topic.
Besides, the topic may show up at just the right time for someone else to see, who knows…
Is the html-prompt tag only for topics where “building HTML prompts” is the main subject, or also for posted macros that contain (and demonstrate) a working HTML prompt?
The tools tag: is it meant for…
only scripting/macro tools (macro/scripting helpers like Accessibility Inspector etc.), or…
also for macros that work with command line tools, or/and…
First, the tag name uses an underscore, not a dash: html_prompt
We are trying to maintain consistency across all tags and use only the underscore to separate words in a tag name.
IMO, html_prompt refers to any macro, usage, or discussion about the KM Action Custom HTML Prompt.
IMO, it has a broad use/intention, but limited to KM. Basically any piece of standalone software that aids in the development of KM macros, or maintaining your KM app/setup/library. That could include a KM macro which, for example, maintains your KM Variables.
In one sense, all macros are a "tool" of some definition, in that they help us get some task done more efficiently. But we would not want to tag all macros with tools tag -- it would be come meaningless.
So, let's restrict the `tools" tag to those tools that specifically help us with KM in some way.
discourse_features
conventions (naming, documenting, etc)l
GUI (not ui_control – making GUIs, dialog boxes, palettes, etc. with KM)
palette
system_preferences
spotlight
mouse
trackpad
debugging
tip
feature_request
bug? (can you have a question mark in a tag?)
unusual
Text, text_processing or text_manipulation. I guess “regex” would automatically cover most instances, but we also have discussions about scraping text from web browsers or pdfs, which don’t always involve regex.
You should be able to use it on all future topics you create. If you find any existing topics that should have this tag, feel free to post a request here (and provide a link to the topic).