view BUGS @ 110148:bcc7c00e9ef4

Remove cut buffer from documentation. * doc/emacs/frames.texi (Cut/Paste Other App): Remove vut-buffer text. * doc/lispref/text.texi (Low-Level Kill Ring): * doc/lispref/frames.texi (Window System Selections): Remove cut buffer documentation. * doc/misc/cl.texi (Basic Setf): Remove x-get-cut-buffer and x-get-cutbuffer. * lisp/term/x-win.el (x-select-text): * lisp/term/pc-win.el (x-selection-value): * lisp/term/ns-win.el (x-selection-value): * lisp/eshell/em-term.el: * lisp/w32-fns.el (x-get-selection-value): * lisp/mouse-sel.el (mouse-sel-set-selection-function): * lisp/frame.el (display-selections-p): Remove cut-buffer in documentation. * lisp/term.el (term-mouse-paste): Don't call x-get-cutbuffer. Remove cut buffer from error message.
author Jan D. <jan.h.d@swipnet.se>
date Thu, 02 Sep 2010 12:17:02 +0200
parents fb8bf24d2eb9
children ac52af4a044c
line wrap: on
line source

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-p in Emacs) to
make sure it isn't a known issue.