I just happened to come across trap, a wikiless tag in serious need of cleanup.
It looks like about a third of the questions are about the bash builtin command
trap, with a few more about the equivalent command in powershell and a couple about ruby. A bunch are about SNMP traps, while the remainder, about half of the total, are mostly about CPU interrupt traps.
As far as I see, most of the questions that don't fall into the above groups should simply have the tag removed, and the SNMP questions might deserve to be split off to their own tag (snmp-trap?).
However, that still leaves us the question of what to do about the shell commands vs. the CPU interrupts? They are sort of related, but not so closely that they'd really fit comfortably under the same tag. My first inclination would've been to declare trap to be about the interrupts, since those are the more fundamental concept of the two, but then what do we do about the shell questions? Or should we move the CPU trap questions under interrupt (which is kind of in need of cleanup itself) and leave trap for the shell commands?
Edit: To start with, I've simply removed the trap tag from the following questions:
- What techniques can be used to detect so called “black holes” (a spider trap) when creating a web crawler?
- What's the most insidious way to pose this problem?
- jQuery: Trap all click events before they happen?
- Determining if a point is “trapped” (enclosed) on a grid
- rcurl web scraping timeout exits program
- How not to run into the intellectual property trap on a daily basis?
- A* path finding: backed into a corner, now what?
- How do you trap when the user clicks on a ListPreference from the menu that pops up?
- How do I trap windows key, alt+tab, ctrl+alt+delete in C#?
- TextField:shouldChangeCharactersInRange:replacementString: return trap!
- Trap errors when eval string content to a hash p
- How can I trap the user in inputdlg()
- KeyDown/KeyPress and Indexing
- Nutch How to avoid crawl calendar webpage generated by CGI
- How to trap a PHP script error which dies (Perl has eval)?
I think that's most of the simply misplaced ones that don't belong to any of the groups described above.