Create a new document. If file with same name already exists, it is opened (and not rewritten). If file with the same name exists and is already open, it is displayed.
Open file. The File open dialog's initial directory is current working directory, or project files directory if there's active project.
Inserts selected file into currently active file at cursor position.
Saves active file. If backup option is enabled, creates backup copy (originalfile.ext~) of the original file.
Saves active file under different name.
Saves all open files.
Reloads original file's contents from disk.
Closes active file, giving an option to save changes, if it was modified.
Ends Wedit for Linux session.
Multiple (max 255 actions) undo. Please note that not all changes can be undone.
Cuts selected area from document, stores it in internal clipboard and provides it as X selection.
See also Clipboard section.
Copies selected area of document, stores it in internal clipboard and provides it as X selection.
See also Clipboard section.
Paste contents of internal clipboard, or X selection into the current document at the cursor position.
See also Clipboard section.
Shows list of functions within the current file and copy it.
Saves internal clipboard (or X Selection) to file. Please note that X selection may even come from different application than Wedit for Linux.
Displays nesting level to the left of editor window. Start of nested block is drawn in comment color (default grey), end of nested block in keyword color (default red).
Marks the block of code around cursor position. The behavior depends on language of current file. For C language, block is defined as starting with open brace '{' and ending with close brace '}', excluding braces in comments.
Sets bookmark. Number of bookmarks is not limited. To manage bookmarks, see menu item 'Search/Go to/Bookmark', or 'Search/Bookmarks'.
Transforms all space characters to tab characters (\t).
Number of spaces that make one tab stop can be defined in 'Project/Configuration/General'Transforms all tab characters (\t) into spaces.
Number of spaces that make one tab stop can be defined in 'Project/Configuration/General'Scrolls the viewport so that the line containing cursor is in the middle of it (vertically).
Edit description of current function.
Edit description of current sourcefile.
Please note that File description template is a generic one. If you develop licensed software, and especially open source licensed software, it is often required that you also put license-related text in every source file. See www.opensource.org for more info on the subjectShows all changes you've made to the current file since the last save.
Reformats the current source file. Wedit for Linux parses the file and replases it with pretty-printed version.
Please note that this function might not work if source file language is not supported by Wedit
Toggles whether Button bar should be displayed or not. Wedit for Linux remembers this setting for future sessions.
Search for specified string (or regular expression) in current file buffer (or all open buffers).
Search for next match.
Search for previous match.
Search for specified string in current file buffer (or all open buffers) and replace it with other string.
Search for strings contained within files.
Go to first line of the file.
Go to last line of the file.
Go to specified line number.
Go to the definition of selected function
Go to previous function in the source file
Go to next function in the source file
Go to bookmark. See also menu 'Search/Bookmarks'
Bookmark current cursor position.
Go to selected bookmark.
Go to next bookmark.
Delete selected bookmark.
Display list of functions in current file, optionally jump to selected function.
Search for, and display, all C structures defined in current file and (optionally) included header files.
Search for a file containing specified function definition.
Search for a definition of symbol under cursor.
Find all occurences of symbol under cursor in opened files. Hits are displayed in the status area at the bottom of Wedit for Linux window.
Write RCS ID tag to current file. It is useful when using revision control system like CVS. Every time a file gets commited, the contents of the string is automatically updated by CVS (or other system compatible with RCS-style keyword substitution). For more information about CVS, visit Pascal Molli's site.
CTAGS and ETAGS are programs that create a 'catalog' of symbols found in the specified source files. Symbols are tagged with the source file they belong to, location in the file, and, in some cases, additional information (class, type of symbol)
Wedit for Linux was tested with GNU Emacs etags version 20.3 and Exuberant Ctags version 4.0.2
CTAGS/ETAGS works with current project. If no project is defined, all curently open files are taken. Upon opening the CTAGS/ETAGS dialog, Wedit scans the project directory (current working directory) for one of these two files:
If the tag file is found, last modification time is displayed, tag file is parsed and displayed in a tree-like view. Depending on the tags program and source files language, up to 3 notebook pages are available:
All views are sorted alphabetically
'Generate' button calls appropriate tags program (ctags/etags, depending on the 'Options...' settings) and re-populates tree views.
'Options ...' dialog lets you choose what tagging program you want to use. Four options are available:
Please note that Wedit for Linux does not update the tag file automatically. You must use 'Generate' button to make sure that symbol views are up to date. This is especially important with ETAGS, which uses absolute symbol locations. CTAGS uses relative addressing (search strings), so you often should be able to use not-up-to-date tag file.
Main Wedit for Linux configuration dialog. Most settings in the Configuration dialog are project-specific. Some of them (Workspace settings, for example) apply even after current project is closed. These are 'global' settings which remain until other project's definitions override them.
General settings:
Column 1 2 3 4 5 6 7 8 9 10 i f ( t e s t ) { a = 5 ; b = 3 ; }after the first line, Wedit automatically places cursor on columns 5, 5, and, after the right brace is typed, it shifts if to position 1.
Vertical line scroll - this option is not used in Wedit for Linux
Tab size - is used when typing new tabs and converting tabs <-> spaces. Adjust this if your coding habits or existing code use tab width other than 4 (default)
Statistics:
OS Info - system information, equivalent to output of command 'uname -a'
Compiler path - path to the compiler executable. The actual compiler used is defined in Project/Configuration, Compiler tab, Compiler. Currently, Wedit for Linux supports GNU gcc(egcs) and lcc compilers.
Current directory - 'base' directory for working with source files. Utilities and helper programs are run with current directory as a working directory. Usually the same as project directory (Project/Configuration, Project tab, Sources Directory)
Projects in Wedit for Linux define set of source files, configuration settings and rules for building the project. Wedit is especially suited for projects in C language, but it can be used for wide range of tasks, from application development to HTML projects.
Project name - name of the current project. Once a project is assigned name, it cannot be changed easily. To change name of the project, you may:
Project type - type of project as defined in Project/Configuration, Linker Tab, Type of Output
Makefile generation - depending on the type of project, you may, or may not want Wedit to generate Makefile for your project. Reasons for not letting Wedit take care of the makefile are:
When you select Do NOT generate Makefile, you may specify:
If you decide to let Wedit maintain the Makefile, you must also choose what kind of Makefile you want in Type of Makefile selection:
Following settings related to Makefile generation may be adjusted:
Additional CFLAGS - arguments to the compiler that couldn't be set by controls in Compiler Tab.
<include> path - path to system include files, entries separated by ':'
Compiler - Wedit for Linux natively supports two compilers: GNU gcc(egcs) and lcc. Native support means that Wedit knows about compiler command line parameters and can parse compiler's error output. You can use different compilers, but you want be able to use all Wedit's features.
Code generation:
Debugging support level - debugging information can add significantly to the total size of executable and can sometimes hide errors (off-bounds memory access). Release applications should be compiled without this flag.
File for error messages - error output of compiler is stored in this file
Warning level - normal, all
Generate intermediate language files - not used in Wedit for Linux
You may define shortcuts for frequently typed pieces of text. For example, if you define Alt+I as '#include <', every time you press Alt+I in the editor, #include < get inserted at the current cursor position.
Please note that X Window Managers often grab lot of keyboard shortcuts for their own use. Keep this in mind when defining keyboard macros.
Wedit for Linux currently has a full support for GDB, the standard GNU debugger. All applications compiled and linked with STABS debugging information can be debugged.
Command line arguments to pass to the program - parameters the program should be started with
Executable to start - normally, executable name is the same as name of the project.
Trap all exceptions - not used in Wedit for Linux. Debugging stops after any signal is received
Terminal for program output - for every debugging session, the target executable is run in a terminal window, so that you can see standard input and output. If your system doesn't have xterm (default), or you want to use more sophisticated terminal, specify it here.
Please note that terminal application must support xterm-style command line switch -e, and optionally -T.
Output file name - normally, the name is the same as name of the project
Additional libraries - you can enter any additional switches to the linker here.
Please note that you have to specify full command line switch to link with an additional library. For example, to link with libm.a, type -lm
Do not include debug information - target executable will not contain STABS debug information
Type of output:
Library version - dynamic library only. Major and minor version of the library. If your library should have major version 2, and minor version 5.1, enter 2.5.1
Language tab controls Wedit for Linux support for programming languages. Wedit supports many programming languages, and level of support varies. All supported languages feature hilighting of keywords and comments. Colors used for syntax hilighting can be set in Project/Configuration, Workspace Tab.
Language drop-down list contains all programming languages supported by Wedit. In Keywords list, you can see all keywords for the selected language.
To add a keyword, exter it in the Keyword field and press Add. To delete a keyword, select it in the Keywords list and press Erase.
Language support enabled shows if current buffer contains source file in one of the supported programming languages.
In this tab, you can change colors of text elements and fonts used in Wedit for Linux editor.
Select text element from Change colors of list and click on Change color button. Reset Colors button reverts all colors to their default values.
Fonts opens font selection dialog.
New project is defined in several steps.
Every project's settings are stored in Wedit for Linux configuration files. Other menu items of 'Project' menu are used for project handling.
Displays list of already defined projects. After selecting new project to open, current project will be closed.
Closes current project
Displays list of defined projects. Selected project is removed from Wedit project repository
Please note that 'Erase' just removes project from Wedit project repository, leaving actual project files unchanged. If you want to remove project files as well, go to project directory and do it manually.Selected project's settings will be exported into a .prj file in current directory. Name of the file is the same as name of project. Exported project can be imported back to Wedit using Import.
Please note that only project settings are exported to .prj file, not actual project files.Import previously exported .prj file back to Wedit. Import is done in two steps:
Opens all files defined in the project in the editor.
Shows tree-like view of project files. For C source files also shows functions defined in respective modules.
For other programming languages, it is better to use CTAGS/ETAGS function to examine structure of the current project.
Makes the project. This usually involves calling make utility.
Opens 'Build' tab in the lower pane of Wedit for Linux window. This tab contains messages from the build process.
Links object files and creates executable. This usually involves deleting current executable (if exists) and calling make utility.
Generates makefile for the project.
Deletes executable and all intermediate (object) files, and performs Make.
Starts debugger. More on this topic in Debugger menu help.
Breakpoints are normally set and used in debugger mode. However, you can manage list of breakpoints for current project in edit mode as well.
Sets breakpoint to current line in current source file buffer.
Start executable made by current project. Executable is started in terminal window, as specified by Project/Configuration, Debugger tab.
Compile current source file. Usually, object file for this source file is deleted and make is called.
Execute external program.
Do a diff on two files or contents of two directories. Diff arguments need not be contained within current project.
Unless you specified generating of patch file, Wedit for Linux will open both input files in editor and let you iterate over differences. Matching part of source texts for every difference chunk are hilighted with yellow color.
Cfiles only. Function tree recursively examines all functions called from selected function. To generate function tree:
C files only. Strings function finds all C strings within the current file. Strings are tagged and can be saved to separate file either in rc format, or as a string table. Original occurences of strings may be optionally replaced by indexes to the generated table.
This function greatly simplifies e.g. locatization of source code.
C files only. Analyses current file generates various function-wise metrics.
In Data menu, you can choose from following metrics:
In the upper right corner, you see type of metric displayed and its maximum value. Clicking on bars in the chart shows values for respective functions in the bottom field of the dialog. Clicking on Select button, you get detailed information on the selected function.
Symbols ... button takes you to the symbols view for selected function
There are three sorts of symbols in this view:
Clicking on the symbol shows in the upper pane all lines of the function which contain selected symbol. This is useful for example for tracing variable usage throughout the function.
Subset of File metrics. Shows metrics for selected function only, not the whole file
C files only. Creates a file (usually header file .h) containing prototypes of C functions from current module.If Load into the editor is selected, generated file will be loaded into the editor after it has been generated.
C files only. For any selected function from current file displays which functions it calls, and by which functions it is called
C files only. Searches for all global symbols in the current file, optionally taking into account #include files
You may choose if globals search should descend to application and system include files, and optionally set system include files path.
Clicking on a global symbol in the right pane shows usage of the symbol in the project (if any) in left pane. You can restrict usage display to a specific function in the drop-down list in right-top corner of the dialog.
Displays all symbols used in selected function. Clicking on a symbol shows all lines of code of fuction that contain selected symbol. This dialog is the same as 'Symbols' in File metrics
C files only. Shows relations between two files. Lists all identifiers defined in the first file (and files included in it) that are used in the second file, and vice versa.
Creates Xref format auditting file for current source file
Applies patch to source file
Wedit for Linux has integrated frontend to the GDB debugger. Following menu items are used to control program execution and inspect data.
In debugger mode, several new tabs appear in the bottom pane of Wedit for Linux window:
Execute program. Program will stop due to one of following events:
Do one step of program execution. If current instruction is a fuction call, follow the call
Do one step of program execution. If current instruction is a fuction call, perform the call and stop immediately after it.
Run program until it returns from current fuction call. Stop immediately after return
Run to source file line under cursor.
Please note that if line does not contain code, debugger may stop on the closest line containing code to the line under cursor. Also keep in mind that line under cursor might not be reached during execution of the program.Leave debugger and go back to editor mode.
Opens window with machine state information (registers, flags, current stack frame, FPU registers, if available)
Shows Stack tab in the bottom pane of Wedit for Linux window.
Opens window that allows you to inspect arbitrary memory location. Right-click menu in the window allows change of display granularity (bytes, shorts, longs), and base (decimal, hexadecimal)
Opens window with assembler view of program being executed
Handle watches that can be inspected in Watches tab in bottom pane of Wedit for Linux window.
Evaluate any valid C expression. Result is added to Watches tab.
Information about memory image of program being executed
Stop debugging and restart from the beginnning.
Break program execution.
Toggle breakpoint on the line under cursor.
Handle breakpoints.
Handle watches in the Watches tab.
Display help index. All Wedit for Linux help files are in HTML format.
Go to the online bug reporting form at Wedit for Linux Home Site.
Display about box, that among other things, contains version of running copy of Wedit for Linux.