2

I've noticed that @Drew, especially, ends up spending a lot of time removing the elisp tag from questions, and pointing out its definition to users.

I don't feel that there's any other tag which gets incorrectly used with such frequency, and it strikes me that all the editing is quite the waste of time, if the issue could be reduced somehow.

Related meta questions:

Because it happens so often, I would be in favour of adding some UI text (to whatever extent is possible), to firmly dissuade users from using this tag casually.

The tag description is:

for questions about Emacs Lisp as a language, compared to other languages, in particular, compared to other Lisp dialects. That is, it is for questions *about the language* itself. *DO NOT USE IT* for questions about *using* Emacs Lisp. Emacs Lisp is the scripting and programming language that the Emacs editor is built on.

Yet the "*DO NOT USE IT*" notice appears too late for it to be visible to anyone asking a question -- the amount of text shown in the editing UI doesn't get much past "for questions about Emacs Lisp as a language, compared to other languages" -- which is doubtless enough for some users, but not as clear as I now think it needs to be.

I'd suggest prepending something like:

*ONLY* for questions about Emacs Lisp as a language ...

Secondly, the form field for entering tags has a placeholder attribute, such that the initial empty field says:

e.g. (spacemacs org-export package)

(Side note: I'm not sure why there are parentheses in that text. That seems wrong?)

This seems like a reasonable place to include something like:

e.g. spacemacs org-export package -- but NOT elisp, unless you've checked

And perhaps there's other places where we have control over the text, which might be used to further highlight the issue?

I realise this is making a special case of this one tag, but I feel that it needs it.

I don't expect these changes to entirely stop it from happening, but it might help it to happen less often, to some helpful degree?

| |
3

I've added the "ONLY" part to the front end of the tag as requested. I believe everything else (updating the placeholder, adding a tag warnings) requires intervention by a SE employee.

| |
2

There's a little known feature called tag warnings which could be used for this. Some sites in the network have them enabled for a few tags; they have to be added by one of the Community Managers. They are more 'in your face' than the tag excerpt which is easily ignored.


(new style)


(old style)

| |

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .