bug#53910: [External] : bug#53910: 29.0.50; context-menu-mode breaks help in read-only buffers

[martin rudalics]

> I think I understand why you say that but the interactive spec only
> allows passing nil as argument, so maybe calling `bury-buffer` with
> a nil argument should not be done from Elisp, but if calling
> `bury-buffer` *in general* should not be done for Elisp, then we can
> simplify the docstring ;-)

'bury-buffer' violates referential transparency in the sense that it
does not allow allow a caller to substitute nil for (current-buffer) and
vice versa without also changing its semantics.  This is against what
all other functions with an optional BUFFER-OR-NAME argument do and can
only lead to confusion.

martin