Node:ecb-layout, Next:ecb-compilation, Previous:ecb-analyse, Up:Customizable options
This group contains settings for the screen-layout of the ECB:
activate-before-new-frame-created-hook | User Option |
Normal hook run before the new ECB-frame is created if
ecb-new-ecb-frame is not nil (otherwise this hook is not
evaluated).
|
advice-window-functions | User Option |
Advice functions to be more intelligent if used with ECB. You can
choose the following functions to be adviced by ECB so they behave as
if the edit-window(s) of ECB would be the only windows(s) of the
ECB-frame:
For working most conveniently with ECB it is the best to advice all these functions, because then all the standard shortcuts of these functions are also usable with ECB without doing anything else. Also other packages can interact best with ECB if these functions are all adviced. If these adviced functions are called in another frame than the ECB-frame they behave all exactly like the not adviced versions! But please read also the following: Normally all packages should work correct with ECB and itīs adviced functions but if there occur problems with a package cause of some of these adviced functions ECB offers the following fall-back solution:
Here is an example: Suppose you must deactivating the advice for
|
advice-window-functions-signal-error | User Option |
Signal an error if an adviced function can not do its job. If not nil
then an error is signaled if one of the adviced functions (see
ecb-advice-window-functions ) can not do its job. So for example
if the user tries to split the compile-window or an ecb-tree-window or
if one tries to switch to another buffer in one of the
ecb-tree-windows. For details see the documentation of each of the
adviced functions to get info when an error is signaled.
If this option is nil then no error is signaled but the called adviced function does simply nothing. Default is nil but it can also be useful to signal errors - so you see when call a function in a situation which is not supported by this function. |
fix-window-size | User Option |
Fix size of the ECB-windows/buffers even after frame-resizing. The fix
type (valid values are nil, t, width and height) can either be set on
a layout-basis (means a different value for each layout) or one value
can be set for all layouts.
For a detailed description of the valid values see description of
Note1: Manually resizing the ECB-windows via Note2: The description of Note3: With current Emacs 21.2.X there seems to be no distinction
between Per default no window-size fixing has been done. |
hide-ecb-windows-after-hook | User Option |
Hooks run direct after the ECB windows have been hidden. Hiding was
done either by ecb-toggle-ecb-windows or
ecb-hide-ecb-windows .
IMPORTANT: Hiding the ECB-windows is internally done by calling
|
hide-ecb-windows-before-hook | User Option |
Hook run direct before the ECB windows will be hidden. Hiding is done
either by ecb-toggle-ecb-windows or
ecb-hide-ecb-windows . This means that at runtime of this hook
all the ECB-tree-windows of current layout are visible.
IMPORTANT: Hiding the ECB-windows is internally done by calling
|
ignore-display-buffer-function | User Option |
Adviced display-buffer ignores display-buffer-function .
This means, that the adviced version of display-buffer (see
ecb-advice-window-functions ) ignores the value of
display-buffer-function when called for the ecb-frame .
If this variable should not be ignored then the function of
display-buffer-function is completely responsible which window
is used for the buffer to display - no smart ECB-logic will help to
deal best with the ECB-window-layout! You can define if and when
display-buffer-function should be ignored:
|
ignore-special-display | User Option |
Ignore special-display-handling. This means, that all values of
special-display-function , special-display-buffer-names
and special-display-regexps are ignored
|
layout-always-operate-in-edit-window | User Option |
Adviced window functions work always in the edit-window. If we are in
an ECB special buffer (methods, directories, etc), and any of the
adviced windowing functions is called interactively (see
ecb-advice-window-functions ), we will select first an
edit-window according to the value of
ecb-mouse-click-destination . This is useful if you have any
functions that use such functions and you don't want them to fail with
an error complaining that the current buffer can not be split, or
something similar.
Because this may not be desirable in all situations and for all
adviced functions this can be enabled separately for every advicable
function (see also For Per default this is enabled for |
layout-debug-mode | User Option |
Write debug-information about layout-operations in the
Messages-buffer. Normally there should be no need to set this option
to true but if there are problems to display buffers in the
compile-window of ECB (e.g. buffers which should be displayed there
aren't or the temporally enlarging-mechanism does not do what you
think it should do etc...) then please do the following steps:
|
layout-name | User Option |
Select a window layout of ECB. Value is any arbitrary string. There are
four different types of layouts: left, right, top and left-right,
which means the location of the ECB-tree-windows in the ECB-frame.
Currently there are 20 predefined layouts; names see below. You can
savely try out any of them by changing this value and saving it only
for the current session. If you are sure which layout you want you can
save it for future sessions. To get a picture of the layout for name
<name> call `ecb-show-layout-help'. ecb-layout-function-9 .
Currently available layouts:
Regardless of the settings you define here: If you have destroyed or
changed the ECB-screen-layout by any action you can always go back to
this layout with |
layout-window-sizes | User Option |
Specifies the sizes of the ECB windows for each layout. The easiest
way (and also the strongly recommended way) to change this variable is
to change the window sizes by dragging the window borders using the
mouse and then store the window sizes by calling the command
ecb-store-window-sizes . Next time the layout is redrawn the
values stored in this option will be used.
If If this option is set "by hand" (i.e. not by
|
maximize-ecb-window-after-selection | User Option |
If not nil maximize current tree-window after selection. When selecting another not-tree-window after such an automatic maximizing all tree-windows of current layout are displayed again. But a tree-window is not maximized if either a node has been selected via primary- oder secondarc mouse-button or the popup-menu of that tree-buffer has been opened. |
maximize-next-after-maximized-select | User Option |
Maximizes the next logical tree-window after a maximized
node-selection. Selecting a node in a maximized tree-window is handled
very smart by ECB:
If a tree-buffer-name is not contained in this option then selecting a node in this maximized tree-buffer automatically "minimizes" that tree-window (i.e. displays all windows of the current layout) so the user can perform the next logical step (e.g. the next logical step after selecting a directory in the directories-buffer is to select a source-file - therefore the sources-buffer of current layout has to be displayed - if the current layout contains one; the next logical step of selecting a source-file is probably to jump to a certain tag via the methods-buffer). If a tree-buffer-name is contained in this option then selecting a
node in this tree-buffer automatically maximizes the next logical
tree-window (e.g. directories -> sources, sources/history ->
methods). But if the current maximized tree-buffer is also contained
in the option The tree-buffer-name can either be defined as plain string or with a
symbol which contains the buffer-name as value. The latter one is
recommended for the builtin ECB-tree-buffers because then simply the
related option-symbol can be used (e.g.
In future versions this option will probably also allow to define the next logical tree-buffer for a tree-buffer - currently this is hard-coded as follows:
|
maximize-next-after-maximized-select | User Option |
Maximizes the next logical tree-window after a maximized
node-selection. Selecting a node in a maximized tree-window is handled
very smart by ECB:
If this option is nil then selecting a node in a maximized directories- sources- or history-tree-buffer automatically "minimizes" that tree-window (i.e. displays all windows of the current layout) so the user can perform the next logical step (e.g. the next logical step after selecting a directory in the directories-buffer is to select a source-file - therefore the sources-buffer of current layout has to be displayed - if the current layout contains one; the next logical step of selecting a source-file is probably to jump to a certain tag via the methods-buffer). If this option is not nil then selecting a node in a maximized
directories- sources- or history-tree-buffer automatically maximizes
the next logical tree-window (directories -> sources, sources/history
-> methods). But if the current maximized tree-buffer is contained in
the option |
new-ecb-frame | User Option |
Create a new frame at activation time of ECB. |
other-window-behavior | User Option |
The behavior of ECB concerning getting an "other window". This has
an effect if either other-window or
other-window-for-scrolling is adviced by ECB, see
ecb-advice-window-functions . The following settings are
possible:
ECB will cycle through all windows of the ECB-frame or scroll simply
the next window in the ECB-frame, means it behaves like the original
ECB will only cycle through the edit-windows of ECB or only scroll
another edit-window. If the selected window is not an edit-window then
it behaves like with value
Like
With this setting ECB tries to choose the
If one of the special ecb-windows is selected then always the "next"
ecb-window is choosen (whereas the next ecb-window of the last
ecb-window is the first ecb-window). In the context of an
If the compile-window is selected then always the last edit-window
which had the point will be used unless If there is an active minibuffer: Regardless of the allowed values above ECB handles the situation of an
active minibuffer during a call to If the minibuffer-window is selected then ECB always chooses the
window If there is an active minibuffer but the minibuffer-window is not
selected then In addition to the allowed values above the value of this option can also be a function: A function: This function gets seven arguments:
The function has to return a window-object which is then used as
"other window" for the command |
redraw-layout-after-hook | User Option |
Hooks run direct before the ECB windows will be shown either by
ecb-toggle-ecb-windows or ecb-show-ecb-windows . This
means that at runtime of this hook the ECB-windows are already
visible.
|
redraw-layout-before-hook | User Option |
Hooks run direct before the ECB-layout will be redrawn by either
ecb-redraw-layout .
|
redraw-layout-quickly | User Option |
If non-nil, we will attempt to redraw the layout quickly. Please read
also carefully the documentation of ecb-redraw-layout .
|
select-edit-window-on-redraw | User Option |
Select the first edit window on ecb-redraw-layout .
|
show-ecb-windows-after-hook | User Option |
Hooks run direct before the ECB windows will be shown either by
ecb-toggle-ecb-windows or ecb-show-ecb-windows . This
means that at runtime of this hook the ECB-windows are already
visible.
IMPORTANT: Showing the hidden ECB-windows is internally done by
calling
|
show-ecb-windows-before-hook | User Option |
Hooks run direct before the ECB windows will be shown either by
ecb-toggle-ecb-windows or ecb-show-ecb-windows . This
means that at runtime of this hook the ECB-windows are still hidden.
IMPORTANT: Showing the hidden ECB-windows is internally done by
calling
|
split-edit-window-after-start | User Option |
Sets if and how the edit window should be splitted after ECB-start.
But be aware: This option determines only if and how the edit-window
should be splitted at start-time of ECB. There are five different
values allowed for this option:
Default value is Some remarks to the value |
toggle-layout-sequence | User Option |
Toggle sequence for layout toggling with ecb-toggle-layout .
Every element of this list has to be a valid layout-name i.e. either
one of the predefined layouts or one of the user-defined layouts.
You can add here as many layouts as you want but to use this option
most effective you should not add more than 2 or 3 layouts so every
layout can be accessed very fast by toggling with
Recommended values are for example:
See also option This option makes only sense if the value is a list with more than 1 element! |
windows-height | User Option |
The height of the ECB windows in lines for top-layouts. If the number is less than 1.0 the width is a fraction of the frame height. |
windows-width | User Option |
The width of the ECB windows in columns for left- and right layouts. If the number is less than 1.0 the width is a fraction of the frame width. |