Crunch CRiSP File Editor 6 Manual de usuario Pagina 39
- Pagina / 92
- Tabla de contenidos
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
Page 39
timer(pg.
45).
CriSP supports callbacks based on an elapsed real-time clock.
window(pg.
33).
A window is a character mode window with a view on to a buffer. A single screen
can contain multiple character mode windows.
→Buffers(pg. 33).
→Macros(pg. 41).
File Types -- Text files and Binary Files
CRiSP allows any file type to be edited, whether the file is binary or text. Editing binary files is allowed
although CRiSP does not contain any special facilities (yet) to perform editing on these files.
Binary files are identified by looking for non-printable characters in the first 100 or so characters of the file. If
there are too many, CRiSP reads the file in, but makes each line only 32 characters wide. This avoids
performance problems with CRiSP whereby if it did not do this, then it would read the whole file into a single
line, making editing and scanning difficult.
Editing binary files can be useful, e.g. as an alternative to the strings(1) utility, to look at the printable strings
in a binary. It can also be useful to make small edits to binary files. For example, to patch string literals in the
file. Care is needed when editing executable files, since the file size needs to be exactly the same before
editing the file as afterwards.
CRiSP notes buffers containing binary files, to ensure that an arbitrary newline character is not inserted at
the end of each 32-character line.
Backing up Files
Backups are created when a file is actually saved. Every time a new file is edited, the old file is renamed so
that even after writing a file away to the disk, the previous version of the file can be recovered. CRiSP can
be configured to create backup files in a separate directory (useful for doing mass deletions when disk
space is low) or for creating a '.bak' file in the current directory. To some users it may be distracting to have
lots of directories filled with .bak files.
In addition, CRiSP supports the ability to keep multiple copies of old backed up files. Again, this is
implemented via the set_backup() primitive. When this variable is set, crisp creates a set of sub-directories
in the main backup directory, named .../0, .../1, etc (the higher the number the older the backup). When a file
is written away, the most recent backup is put in the backup directory. The previous version in the backup
directory is moved to the .../0 sub-directory. That is, the backup directory contains the most recent backup,
.../0 contains the second most recent backup, and .../N-1 contains the oldest backup.
It is sometimes useful to turn off backup file generation for certain files, e.g. very large log files; you can tell
CRiSP to turn off creating a backup file for the current file by using the set_backup macro.
In addition to the above two features, CRiSP has a builtin facility to save buffers in an emergency. If CRiSP
detects an internal error (e.g. segmentation violation) all the currently modified buffers are written away to
the current directory, with filenames called BUFFER-0, BUFFER-1, and so on. This should never happen,
but bugs have a habit of laying dormant until the most unfriendly time.
To optimise performance, CRiSP uses the following algorithm when trying to backup a file:
1. If the file has multiple links to it, the file is copied to the destination directory. (See below). If the file has
only a single link, then it may be link()ed to the destination directory.
(Linking is much faster than copying because the actual contents of the file need not be copied -- just
the file name is changed).
2. For each directory in the backup directory list try to link() the file to the specified directory. This
operation may fail if the directory is on a different file system. (This step is skipped if the
BACKUP_SLOW flag is set).
3. If step 2 fails, then for each directory in the backup directory list, try and copy the file to the resultant
directory. This may fail because of permissions.
4. If steps 2 & 3 fail, try and create a file with a .bak extension. If the file has multiple links, then the old file
is copied to the new file. If the file has a single link, then it is link()ed to the .bak file.
Autosaving
- CRiSP File Editor 1
- Programmers Guide 1
- Introduction 7
- Disclaimer 7
- Writing your own macros 9
- Tools Overview 10
- <Alt-F10> 10
- File formats 11
- Specifying Directories 11
- Language Mapping switches 11
- General switches 11
- Output file format 12
- Filename filtering 12
- Language specifications" 13
- Languages 13
- The CRUNCH Language 14
- The crunch compiler 14
- Data types 15
- Scoping 17
- Argument Passing 18
- Variable argument lists 20
- The int data type 21
- The float/double data type 21
- The string datatype 21
- The list (array) datatype 22
- List assignment 23
- Making Lists 23
- Manipulating List Items 24
- Sorting Lists 24
- Searching Lists 24
- Informational Lists 24
- The declare datatype 25
- Structures 25
- Language Grammar 25
- Declarations 26
- Function definitions 27
- Expressions 27
- Testing expressions: if 29
- Selection: switch 29
- Debugging macros 30
- Macro tracing 31
- Debug applied to a function 32
- Debug on startup 32
- Debug buffering 33
- The vars() macro 33
- Buffers, Files and Windows 33
- Buffer Attributes 34
- Ansi Mode buffer attribute 34
- The Backup Flag 34
- The Binary Flag 34
- Character Maps 37
- Objects supported by CRiSP 38
- Backing up Files 39
- Autosaving 39
- Core dumping 40
- Regions and markers 40
- Global and Static macros 41
- Registered Macros 42
- Timer functions 45
- Color Support 46
- Character Escaping 48
- Character Class: [..] and 49
- Matching Line boundaries 49
- Repetition: @ and + 49
- Minimal and Maximal Matching 50
- Matching Direction 51
- GUI Based Objects 51
- Terminology 52
- Overview of an Object 54
- Creating a Dialog Box 55
- Object Types 56
- Geometry Layout 59
- Sub-groups 64
- Properties (private symbols) 65
- Dialog boxes and Callbacks 66
- Platform Specific Issues 67
- Keyword Builder 68
- Character classes 69
- Global attributes 69
- Keywords 69
- Creating a new colorizer 69
- Dialog box buttons 69
- .KWD Keyword File Format 70
- The flags= Directive 71
- Character Class Directives 72
- Keyword Directives 74
- Keyword Flags 75
- Keyword Regular Expressions 76
- Limitations of Colorization 76
- Colorization:limitations 76
- Case study #1: C colorizer 77
- IPC Mechanisms 79
- IPC Primitives 80
- IPC Callbacks 80
- IPC_TRIGGER_WRITE 82
- Pipe Communications 84
- PTY Communications 84
- PTYPseudo 84
- Server:DDE 85
- DDE Communications 85
- DDEProgram Manager 85
- Excel:invoking CRiSP 86
- Signals Communications 86
- Signal based communication 87
- Keyboard objects 87
- Keys and Keystrokes 88
- Character based terminals 88
- Scan Codes 89
- The cm compiler 90
Ari-armaturen RI21 EN manuals
Owner’s manuals and user’s guides for Equipment Ari-armaturen RI21 EN.
We providing 1 pdf manuals Ari-armaturen RI21 EN for download free by document types: User Manual
Comentarios a estos manuales