[climacs-cvs] CVS update: climacs/Doc/climacs-user.texi
Robert Strandh
rstrandh at common-lisp.net
Wed Oct 19 18:03:08 UTC 2005
Update of /project/climacs/cvsroot/climacs/Doc
In directory common-lisp.net:/tmp/cvs-serv7293
Modified Files:
climacs-user.texi
Log Message:
Added a chapter describing a proposal to change the buffer/pane
relations. This chapter will disappear once the proposal is
implemented, and the description of the existing key bindings will be
altered.
Date: Wed Oct 19 20:03:08 2005
Author: rstrandh
Index: climacs/Doc/climacs-user.texi
diff -u climacs/Doc/climacs-user.texi:1.6 climacs/Doc/climacs-user.texi:1.7
--- climacs/Doc/climacs-user.texi:1.6 Sat Sep 24 20:53:48 2005
+++ climacs/Doc/climacs-user.texi Wed Oct 19 20:03:07 2005
@@ -44,6 +44,7 @@
* Kill ring::
* Advanced editing commands::
* Getting help::
+* Proposal for new buffer/pane relations::
* Key Index::
* Concept Index::
@end menu
@@ -604,6 +605,41 @@
bound to an order, that order will displayed in the minibuffer.
Otherwise, a message indicating that the command is not bound to any
order will be displayed.
+
+ at node Proposal for new buffer/pane relations
+ at chapter Proposal for new buffer/pane relations
+
+There is a proposal on the table to make the way @climacs{} manages
+buffers and panes incompatible with that of Emacs, and in the process
+thus cleaning up 30 years of baggage.
+
+The proposal is to no longer allow buffers without panes. Instead, a
+buffer will always be associated with at least one pane, though that
+pane could be adopted or disowned to make it visible or invisible.
+The advantage of this organization is that a buffer will no longer
+contain a point. Also, panes can contain other things that buffers
+such as buffer lists, debugger applications, etc.
+
+For this to work, we need to define how the effect of certain
+commands related to buffers and windows will be altered. The proposal
+is:
+
+C-x 2 creates an additional pane with its own point and that shares
+the buffer of the current pane. It also adopts the new pane by the
+same mechanism used now (creating a vbox pane containing the two. C-x
+3 is similar except that it uses a hbox instead.
+
+C-x 0 does not destroy the pane, but just disowns it (by replacing the
+rack it is in by the pane itself).
+
+C-x 1 does the equivalent of C-x 0 on all other visible panes.
+
+C-x k kills the current pane. If that happens to be the last pane
+containing a particular buffer, then the buffer is lost as well.
+
+C-x b replaces the current pane by some arbitrary pane displaying the
+buffer that has been requested (or creates a new buffer and a new pane
+if the buffer requested does not exist?).
@node Key Index
@unnumbered Key Index
More information about the Climacs-cvs
mailing list