Editor Settings
If on, text-dragging out of a TextView is only initiated if the CTRL-key is pressed
simultaneously.
Otherwise, a mouse-move with the left button pressed initiates a text-drag.
The default is to require the CTRL to be pressed.
When dragging a file from the desktop or another application into a text view (workspace, browser, etc.),
you are normally asked if the contents of the file or alternatively the name of the file is to be pasted.
This toggle disables that confirmation and enforces that the contents is always pasted.
Use this, if many files are to be dropped.
If on, text-search-boxes are modal. If off, they stay open as floating dialogs, for
easier incremental search operations.
The default is modal.
Toggles Tab Stops between multiples-of-4 and multiples-of-8.
When loading/saving code from/into a file, tab stops are always assumed to
be in multiples of 8.
If enabled, text selection via double click behaves as in ST80,
which is sligtly different
from ST/X's normal (word-select) behavior:
-
Double click at the very top of the document, selects the whole text.
-
Double click at the beginning of a line, selects the line.
-
Double click right after the quotes of a comment, selects the comment's text.
-
Double click right after the leftBrack of a block, selects the whole block.
If enabled, the text cursor behaves as in the ST80 textView (and also as in
many other editing systems), in that the cursors position is limited to the
actual dimension of the underlying text (the ``text-stream'' philosophy as in
the ''vi'' editor).
I.e. the text cursor cannot be positioned beyond the last character within a text line
and cannot be positioned beyond the last line vertically.
The default ST/X behavior is to treat editText as if it was a piece-of-paper,
where random-posioning is always posible, automatically adjusting the texts size
as required. (the ``piece-of-paper-WYSIWYG'' philosophy, as in the ''RAND'' editor.)
If enabled, word detection includes the underline character in text editor views.
This affects the double click behavior, when clicking into a word.
If on, words connected with underline characters are treated as a single word;
if not, they are treated as separate words.
Notice, that in a code-showing view, the underline character is always treated like
an alphanumeric character.
(Caveat: this should probably be a view-specific setting, instead of a global one).
If enabled, any non-Whitespace character is included in the selection when
performing a word-select.
This affects the double click behavior, when clicking into a word.
If on, non-space and non-letter characters such as comma, period etc.
will also be included in the selection.
if not, they are treated as separators.
The style to be used depends on your personal preferences and also on which
kind of text (documentation vs. code) is what you intend to work with
mostly.
(Caveat: this should probably be a view-specific setting, instead of a global one).
Copyright © 1999 eXept Software AG, all rights reserved
Doc $Revision: 1.9 $ $Date: 2009/09/25 09:21:45 $