<p>To fix this for new posts, you <strong>really</strong> want to stop using the ambiguous tag completely.</p>

<p>I suggest:</p>

<ul>
<li><code>[error terms]</code> for error terms</li>
<li><code>[error messages]</code> for program error messages</li>
</ul>

<p>Both will show up just fine when people start typing 'error'.  No re-training will be necessary when the old tag is made to stop popping up as an option (i.e. immediately)...except for the few people who have the power to create tags and don't know about the change.</p>

<hr>

<p>To fix this for old posts, there is going to be a lot of effort to re-tag things regardless, but there is an advantage to ceasing all use of <code>[error]</code>:</p>

<ul>
<li>It will be absolutely clear what posts remain to be tagged at any given time.  It will always be the case that all posts tagged with <code>[error]</code> remain to be processed.</li>
</ul>

<hr>

<p>As a side note, no matter what tag scheme is chosen, separately processing batches of questions tagged with program names should help a bit, since the rate of need for the two new tags will differ for those tagged with programs versus those that are not.  'Separately' could mean assigning a given person to only process program-tagged or non-program-tagged questions, or just sticking to one type on any given re-tagging spree.  You <em>may</em> even want to automatically tag program-tagged questions with the new program error message tag and non-program-tagged questions with the new error term tag.  It will be wrong, but it will be less wrong than what we have now.  ...and again, if you use my suggestion, you will still always know which questions' tags still need human vetting.</p>
