Bug 94459 [Undo] - should refactoring undo work when text undo limit is 0?
Refactoring undos are not showing up in the package explorer undo menu when the text undo limit is set to 0. Technically the refactoring operation should be permitted on the workspace undo context history. The history should just be removing the text context from the operation. One could argue this is a correctly working "feature" but need to check why it's happening and resolve the behavior as a bug or document as expected outcome.
bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/operations/DefaultOperationHistory.java
Assert.isNotNull(operation);
		/*
		 * If we are in the middle of executing an open batching operation, and
		 * this is not that operation, then we need only add the context of the
		 * new operation to the batch. The operation itself is disposed since we
		 * will never undo or redo it. We consider it to be triggered by the
		 * batching operation and assume that its undo will be triggered by the
		 * batching operation undo.
		 */
		if (openComposite != null && openComposite != operation) {
			openComposite.add(operation);
			return;
		}
		if (checkUndoLimit(operation)) {
			synchronized (undoRedoHistoryKey) {
				undoList.add(operation);
			}
			notifyAdd(operation);
			
			IUndoContext[] contexts = operation.getContexts();
			for (int i = 0; i < contexts.length; i++) {
				flushRedo(contexts[i]);
			}
		}
	}
	/**
	 * <p>
	 * Add the specified approver to the list of operation approvers consulted
	 * by the operation history before an undo or redo is allowed to proceed.
	 * This method has no effect if the instance being added is already in the