So, would you please describe a real use case demand you're willing to support?

Now I want this for my XML inspections, so I can say "suppress for this section" where section is specfic to this file type.

• Suppressing inspections in XML should be available by default: IDEA-7652.
• Linking the suppression action + suppression recognition logic to the language sounds good.
• Having custom "Suppress for ..." QuickFixes doesn't sound good as it's too specific. An inspection should instead be able to pass arbitrary "quickfix options" to a ProblemDescriptor, possibly with some kind of anchor to specify where they should appear in the quickfix's "option menu".

If your case requires additional logic, a possibility to specify certain "option" actions per ProblemDescriptor that would appear in the same menu as the "Edit Inspection Settings" and "Suppress for ..." actions could of course provide that logic. I just think that the API should not imply that these option-actions suppress anything (they could actually do anything) as you originally suggested in the request.

If, however, a solution is favored that does call these actions "suppress actions", I think the API should require the imlementor of the inspection to also provide a way to determine if the inspection is suppressed:

public class CustomSuppressableInspection extends LocaInspectionTool {
  public abstract IntentionAction[] getSuppressActions(ProblemDesciptor p);

  public abstract boolean isSuppressedFor(PsiElement element);
}

Just my 2c

Thanks,
Sascha