X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=man%2Fxemacs%2Fframe.texi;h=e82d418d77c351b27f1e4f79c2cff18b4b10d6e1;hb=183f57a1b4551fc8c2cefb6488f2a426931d2766;hp=59198184d75b95c90482a0653c70fa378b8815fd;hpb=82f6d62ee211b1d36e8f45fed3ee3edde82b6916;p=chise%2Fxemacs-chise.git- diff --git a/man/xemacs/frame.texi b/man/xemacs/frame.texi index 5919818..e82d418 100644 --- a/man/xemacs/frame.texi +++ b/man/xemacs/frame.texi @@ -21,16 +21,16 @@ you can split the frame into two or more subwindows. If you are running XEmacs under the X window system, that means you can have several @dfn{XEmacs windows} inside the X window that contains the XEmacs frame. You can even have multiple frames in different X windows, each with -their own set of subwindows. +their own set of subwindows. @refill @end table -Each XEmacs frame displays a variety of information: +Each XEmacs frame displays a variety of information: @itemize @bullet @item The biggest area usually displays the text you are editing. It may consist of one window or of two or more windows if you need to look at two -buffers a the same time. +buffers a the same time. @item Below each text window's last line is a @dfn{mode line} (@pxref{Mode Line}), which describes what is going on in that window. The mode line @@ -78,12 +78,12 @@ visible in all XEmacs windows containing that buffer. @menu -* Point:: The place in the text where editing commands operate. -* Echo Area:: Short messages appear at the bottom of the frame. +* Point:: The place in the text where editing commands operate. +* Echo Area:: Short messages appear at the bottom of the frame. * Mode Line:: Interpreting the mode line. * GUI Components:: Menubar, toolbars, gutters. -* XEmacs under X:: Some information on using XEmacs under the X - Window System. +* XEmacs under X:: Some information on using XEmacs under the X + Window System. * XEmacs under MS Windows:: Some information on using XEmacs under Microsoft Windows. @end menu @@ -203,7 +203,7 @@ looking. @var{ch} contains two stars (@samp{**}) if the text in the buffer has been edited (the buffer is ``modified''), or two dashes (@samp{--}) if the -buffer has not been edited. Exception: for a read-only buffer, it is +buffer has not been edited. Exception: for a read-only buffer, it is @samp{%%}. @var{buf} is the name of the window's chosen @dfn{buffer}. The chosen @@ -214,7 +214,7 @@ currently selected buffer. @xref{Buffers}. @var{pos} tells you whether there is additional text above the top of the screen or below the bottom. If your file is small and it is -completely visible on the screen, @var{pos} is @samp{All}. Otherwise, +completely visible on the screen, @var{pos} is @samp{All}. Otherwise, @var{pos} is @samp{Top} if you are looking at the beginning of the file, @samp{Bot} if you are looking at the end of the file, or @samp{@var{nn}%}, where @var{nn} is the percentage of the file above the @@ -274,7 +274,7 @@ controls whether the mode line is displayed in inverse video (assuming the terminal supports it); @code{nil} means no inverse video. The default is @code{t}. For X frames, simply set the foreground and background colors appropriately. - + @node GUI Components, XEmacs under X, Mode Line, Frame @comment node-name, next, previous, up @section GUI Components @@ -294,6 +294,7 @@ function, and on a tab in the gutter to switch buffers. @menu * Menubar Basics:: How XEmacs uses the menubar. * Scrollbar Basics:: How XEmacs uses scrollbars. +* Mode Line Basics:: How XEmacs uses modelines. * Toolbar Basics:: How XEmacs uses toolbars. * Gutter Basics:: How XEmacs uses gutters. * Inhibiting:: What if you don't like GUI? @@ -336,7 +337,7 @@ Other menus which are typically available are the @samp{Options}, detailed descriptions of these menus, @ref{Pull-down Menus}. (In 21.2 XEmacsen, the @samp{Mule} menu will be moved under @samp{Options}.) -@node Scrollbar Basics, Toolbar Basics, Menubar Basics, GUI Components +@node Scrollbar Basics, Mode Line Basics, Menubar Basics, GUI Components @comment node-name, next, previous, up @section XEmacs Scrollbars @@ -355,7 +356,25 @@ may be customized by the user. By default a vertical scrollbar is present in all windows (except the minibuffer), and there is no horizontal scrollbar. -@node Toolbar Basics, Gutter Basics, Scrollbar Basics, GUI Components +@node Mode Line Basics, Toolbar Basics, Scrollbar Basics, GUI Components +@comment node-name, next, previous, up +@section XEmacs Mode Lines + +When used in a windowing system, the XEmacs modelines can be dragged +vertically. The effect is to resize the windows above and below the +modeline (this includes the minibuffer window). + +Additionally, a modeline can be dragged horizontally, in which case it +scrolls its own text. This behavior is not enabled by default because it +could be considered as disturbing when dragging vertically. When this +behavior is enabled, the modeline's text can be dragged either in the +same direction as the mouse, or in the opposite sense, making the +modeline act as a scrollbar for its own text. + +You can select the behavior you want from the @samp{Display} submenu of +the @samp{Options} menu. + +@node Toolbar Basics, Gutter Basics, Mode Line Basics, GUI Components @comment node-name, next, previous, up @section XEmacs Toolbars @@ -406,6 +425,13 @@ if the list is too long, the least recently used buffers are deleted from the list. By default up to 6 most recently used buffers with the same mode are displayed on tabs in the gutter. +This behavior can be altered by customizing +@code{buffers-tab-filter-functions}. Setting this variable to +@code{nil} forces display of all buffers, up to +@code{buffers-tab-max-size} (also customizable). More complex behavior +may be available in 3rd party libraries. These, and some more +rarely customized options, are in the @code{buffers-tab} Customize group. + @node Inhibiting, Customizing, Gutter Basics, GUI Components @comment node-name, next, previous, up @section Inhibiting Display of GUI Components @@ -488,15 +514,19 @@ The function @code{switch-to-buffer-other-frame} is just like in first. This is normally bound to @kbd{C-x 5 b}. @vindex default-frame-alist +@vindex default-frame-plist You can specify a different default frame size other than the one provided. -Use the variable @code{default-frame-alist}, which is an alist of default +Use the variable @code{default-frame-plist}, which is a plist of default values for frame creation other than the first one. These may be set in -your init file, like this: +your init file, like this: @example - (setq default-frame-alist '((width . 80) (height . 55))) + (setq default-frame-plist '(width 80 height 55)) @end example +This variable has replaced @code{default-frame-alist}, which is +considered obsolete. + @vindex x-frame-defaults For values specific to the first XEmacs frame, you must use X resources. The variable @code{x-frame-defaults} takes an alist of default frame @@ -509,7 +539,7 @@ When you create a new frame, the variable @code{create-frame-hook} is called with one argument, the frame just created. If you want to close one or more of the X windows you created using -@b{New Frame}, use the @b{Delete Frame} menu item from the @b{File} menu. +@b{New Frame}, use the @b{Delete Frame} menu item from the @b{File} menu. @vindex frame-title-format @vindex frame-icon-title-format @@ -549,4 +579,3 @@ with MS Windows. Where possible, native MS Windows GUI components and capabilities are used in XEmacs. -