Node:ecb-analyse, Next:ecb-layout, Previous:ecb-history, Up:Customizable options
| analyse-bucket-element-face | User Option |
|
Basic face for displaying elements of buckets in the
ECB-analyse-buffer. This defines the basic face for the elements of
category-buckets like Context, Prefix, Completions etc. in the
ECB-analyse-buffer.
Changes take first effect after finishing and reactivating ECB! |
| analyse-bucket-node-face | User Option |
|
Basic face for displaying a bucket-node in the ECB-analyse-buffer.
This defines the basic face for the bucket-nodes like Context, Prefix,
Completions etc. in the ECB-analyse-buffer.
Changes take first effect after finishing and reactivating ECB! |
| analyse-buffer-after-create-hook | User Option |
Local hook running after the creation of the analyse-buffer. Every
function of this hook is called once without arguments direct after
creating the analyse-buffer of ECB and it's local key-map. So for
example a function could be added which performs calls of
local-set-key to define new key-bindings only for the
analyse-buffer of ECB.
|
| analyse-buffer-name | User Option |
|
Name of the ECB analyse buffer. Because it is not a normal buffer for
editing you should enclose the name with stars, e.g. "*ECB
Analyse*".
If it is necessary for you you can get emacs-lisp access to the
buffer-object of the ECB-analyse-buffer by this name, e.g. by a call
of Changes for this option at runtime will take affect only after deactivating and then activating ECB again! |
| analyse-collapsed-buckets | User Option |
|
Buckets collapsed when displaying the current semantic analysis. The
semantic analyse-modul offers several categories of analysis which are
called buckets here. These are for example:
Context: The current context, which is the current function/method, variable, class etc. (what exactly depends on the programming language) point is in. This means not the current function/method/variable/class-name point stand on but the current surrounding context. Example: If point stays somewhere within a defun-definition in emacs-lisp or within a java-method then this defun rsp. method is the context. In object oriented languages this can be the full hierachy, i.e. not only the current method, but the current method, the class of this method, the superclass of this class and so on! Arguments: The arguments of the context if the context is a function/method. Local Variables: All accessible and bound local variables visible at current point. Prefix: The currently parsed prefix, which is mostly the current identifier point stands on. Assignee: See the semantic user-manual Function: Current function-name point stands on. Argument #: When point is located within a function-call then this is the number of the argument point stands on. Completions: All possible completions for current prefix (see above). This is probably the most helpful bucket. If one of these categories/buckets are not needed per default then add the bucket-name (s.a.) to this option and ECB will per default collapse this bucket. So most needed buckets are better visible in the analyse-buffer. |
| analyse-face | User Option |
Face used for highlighting current entry in the analyse buffer. If the
face ecb-default-highlight-face is used then the display of all
ECB-tree-buffers can be changed by modifying only the face
ecb-default-highlight-face.
Changes take first effect after finishing and reactivating ECB! |
| analyse-fontified-buckets | User Option |
Buckets whose elements should be fontified as in the methods-buffer.
If the name of a category/bucket is contained in this option then all
elements of this bucket will be displayed as in the methods-buffer -
at least if an element is a semantic-tag. This means if
ecb-font-lock-tags is not nil these elements will be fontified
and also displayed with an appropriate icon if possible. The default
value does this only for the Context-bucket because for most of the
other buckets this makes not really much sense.
For available buckets see For the faces used to display a bucket-node itself or bucket-elements
not fontified see the options |
| analyse-gen-tag-info-fn | User Option |
|
Which info should be displayed for a tag of the analyse-buffer. If nil
then the default information about a tag will be displayed. If a
function then this function gets as argument the tag for which
tag-information should be displayed. This function has to return a
string which will be then display as tag-info. This string has to be
fully formatted (e.g. must already include line-breaks if the tag-info
should be displayed in several lines).
See |
| analyse-general-face | User Option |
Basic face for the ECB analyse buffer. This defines the basic face the
whole history buffer should displayed with. If the face
ecb-default-general-face is used then the display of all
ECB-tree-buffers can be changed by modifying only the face
ecb-default-general-face.
Changes take first effect after finishing and reactivating ECB! |
| analyse-show-node-info | User Option |
|
When to display which node-info in the history-buffer. Define which
node info should displayed after moving the mouse over a node (or
after a shift click onto the node) in the history-buffer.
You can define "when" a node-info should be displayed: See
You can define what info should be displayed:
Do NOT set this option directly via setq but use always customize! |
| analyse-show-tag-info-fn | User Option |
How to display the tag-info for a tag of the analyse-buffer. The value
of this option is a function which will be called with the info-string
generated for the current tag of the analyse-buffer. This function
must do all things necessary for displaying this info. When this
function is called the window stored in
ecb-last-edit-window-with-point is the selected window!
ECB offers two builtin ways: Display the info in the echo-area (via
the function See also |