[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

1 The XEmacs Frame

Frame

In many environments, such as a tty terminal, an XEmacs frame literally takes up the whole screen. If you are running XEmacs in a multi-window system like the X Window System, the XEmacs frame takes up one X window. See section Using XEmacs Under the X Window System, for more information.

Window

No matter what environment you are running in, XEmacs allows you to look at several buffers at the same time by having several windows be part of the frame. Often, the whole frame is taken up by just one window, but 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 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.

Each XEmacs frame displays a variety of information:

You can subdivide the XEmacs frame into multiple text windows, and use each window for a different file (@pxref{Windows}). Multiple XEmacs windows are tiled vertically on the XEmacs frame. The upper XEmacs window is separated from the lower window by its mode line.

When there are multiple, tiled XEmacs windows on a single XEmacs frame, the XEmacs window receiving input from the keyboard has the keyboard focus and is called the selected window. The selected window contains the cursor, which indicates the insertion point. If you are working in an environment that permits multiple XEmacs frames, and you move the focus from one XEmacs frame into another, the selected window is the one that was last selected in that frame.

The same text can be displayed simultaneously in several XEmacs windows, which can be in different XEmacs frames. If you alter the text in an XEmacs buffer by editing it in one XEmacs window, the changes are visible in all XEmacs windows containing that buffer.


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

1.1 Point

When XEmacs is running, the cursor shows the location at which editing commands will take effect. This location is called point. You can use keystrokes or the mouse cursor to move point through the text and edit the text at different places.

While the cursor appears to point at a character, you should think of point as between two characters: it points before the character on which the cursor appears. Sometimes people speak of “the cursor” when they mean “point,” or speak of commands that move point as “cursor motion” commands.

Each XEmacs frame has only one cursor. When output is in progress, the cursor must appear where the typing is being done. This does not mean that point is moving. It is only that XEmacs has no way to show you the location of point except when the terminal is idle.

If you are editing several files in XEmacs, each file has its own point location. A file that is not being displayed remembers where point is. Point becomes visible at the correct location when you look at the file again.

When there are multiple text windows, each window has its own point location. The cursor shows the location of point in the selected window. The visible cursor also shows you which window is selected. If the same buffer appears in more than one window, point can be moved in each window independently.

The term ‘point’ comes from the character ‘.’, which was the command in TECO (the language in which the original Emacs was written) for accessing the value now called ‘point’.


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

1.2 The Echo Area

The line at the bottom of the frame (below the mode line) is the echo area. XEmacs uses this area to communicate with the user:


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

1.3 The Mode Line

Each text window’s last line is a mode line which describes what is going on in that window. When there is only one text window, the mode line appears right above the echo area. The mode line is in inverse video if the terminal supports that, starts and ends with dashes, and contains text like ‘XEmacs: something’.

If a mode line has something else in place of ‘XEmacs: something’, the window above it is in a special subsystem such as Dired. The mode line then indicates the status of the subsystem.

Normally, the mode line has the following appearance:

--ch-XEmacs: buf      (major minor)----pos------

This gives information about the buffer being displayed in the window: the buffer’s name, what major and minor modes are in use, whether the buffer’s text has been changed, and how far down the buffer you are currently looking.

ch contains two stars (‘**’) if the text in the buffer has been edited (the buffer is “modified”), or two dashes (‘--’) if the buffer has not been edited. Exception: for a read-only buffer, it is ‘%%’.

buf is the name of the window’s chosen buffer. The chosen buffer in the selected window (the window that the cursor is in) is also XEmacs’s selected buffer, the buffer in which editing takes place. When we speak of what some command does to “the buffer”, we mean the currently selected buffer. @xref{Buffers}.

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, pos is ‘All’. Otherwise, pos is ‘Top’ if you are looking at the beginning of the file, ‘Bot’ if you are looking at the end of the file, or ‘nn%’, where nn is the percentage of the file above the top of the screen.

major is the name of the major mode in effect in the buffer. At any time, each buffer is in one and only one major mode. The available major modes include Fundamental mode (the least specialized), Text mode, Lisp mode, and C mode. @xref{Major Modes}, for details on how the modes differ and how you select one.

minor is a list of some of the minor modes that are turned on in the window’s chosen buffer. For example, ‘Fill’ means that Auto Fill mode is on. Abbrev means that Word Abbrev mode is on. Ovwrt means that Overwrite mode is on. @xref{Minor Modes}, for more information. ‘Narrow’ means that the buffer being displayed has editing restricted to only a portion of its text. This is not really a minor mode, but is like one. @xref{Narrowing}. Def means that a keyboard macro is being defined. @xref{Keyboard Macros}.

Some buffers display additional information after the minor modes. For example, Rmail buffers display the current message number and the total number of messages. Compilation buffers and Shell mode display the status of the subprocess.

If XEmacs is currently inside a recursive editing level, square brackets (‘[…]’) appear around the parentheses that surround the modes. If XEmacs is in one recursive editing level within another, double square brackets appear, and so on. Since information on recursive editing applies to XEmacs in general and not to any one buffer, the square brackets appear in every mode line on the screen or not in any of them. @xref{Recursive Edit}.

XEmacs can optionally display the time and system load in all mode lines. To enable this feature, type M-x display-time. The information added to the mode line usually appears after the file name, before the mode names and their parentheses. It looks like this:

hh:mmpm l.ll [d]

(Some fields may be missing if your operating system cannot support them.) hh and mm are the hour and minute, followed always by ‘am’ or ‘pm’. l.ll is the average number of running processes in the whole system recently. d is an approximate index of the ratio of disk activity to CPU activity for all users.

The word ‘Mail’ appears after the load level if there is mail for you that you have not read yet.

Customization note: the variable mode-line-inverse-video controls whether the mode line is displayed in inverse video (assuming the terminal supports it); nil means no inverse video. The default is t. For X frames, simply set the foreground and background colors appropriately.


[ << ] [ < ] [ Up ] [ > ] [ >> ]         [Top] [Contents] [Index] [ ? ]

1.4 Using XEmacs Under the X Window System

XEmacs can be used with the X Window System and a window manager like MWM or TWM. In that case, the X window manager opens, closes, and resizes XEmacs frames. You use the window manager’s mouse gestures to perform the operations. Consult your window manager guide or reference manual for information on manipulating X windows.

When you are working under X, each X window (that is, each XEmacs frame) has a menu bar for mouse-controlled operations (@pxref{Pull-down Menus}).

XEmacs under X is also a multi-frame XEmacs. You can use the New Frame menu item from the File menu to create a new XEmacs frame in a new X window from the same process. The different frames will share the same buffer list, but you can look at different buffers in the different frames.

The function find-file-other-frame is just like find-file, but creates a new frame to display the buffer in first. This is normally bound to C-x 5 C-f, and is what the Open File, New Frame menu item does.

The function switch-to-buffer-other-frame is just like switch-to-buffer, but creates a new frame to display the buffer in first. This is normally bound to C-x 5 b.

You can specify a different default frame size other than the one provided. Use the variable default-frame-alist, which is an alist of default values for frame creation other than the first one. These may be set in your init file, like this:

  (setq default-frame-alist '((width . 80) (height . 55)))

For values specific to the first XEmacs frame, you must use X resources. The variable x-frame-defaults takes an alist of default frame creation parameters for X window frames. These override what is specified in ‘~/.Xdefaults’ but are overridden by the arguments to the particular call to x-create-frame.

When you create a new frame, the variable 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 New Frame, use the Delete Frame menu item from the File menu.

If you are working with multiple frames, some special information applies:


[Top] [Contents] [Index] [ ? ]

About This Document

This document was generated on December 6, 2024 using texi2html 5.0.

The buttons in the navigation panels have the following meaning:

Button Name Go to From 1.2.3 go to
[ << ] FastBack Beginning of this chapter or previous chapter 1
[ < ] Back Previous section in reading order 1.2.2
[ Up ] Up Up section 1.2
[ > ] Forward Next section in reading order 1.2.4
[ >> ] FastForward Next chapter 2
[Top] Top Cover (top) of document  
[Contents] Contents Table of contents  
[Index] Index Index  
[ ? ] About About (help)  

where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:


This document was generated on December 6, 2024 using texi2html 5.0.