-
-
- General Startup preferences - -
- General Miscellaneous preferences
-
-
- Miscellaneous -
- Search -
- Projects -
- - Interface preferences
-
-
- Sidebar -
- Fonts -
- Miscellaneous -
- - Interface Notebook tab preferences - -
- Interface Toolbar preferences
-
-
- Toolbar -
- Appearance -
- - Editor Features preferences
-
-
- Features -
- - Editor Indentation preferences - -
- Editor Completions preferences - -
- Editor Display preferences - -
- Files preferences - -
- Tools preferences
-
-
- Tool paths -
- Commands -
- - Template preferences - -
- Keybinding preferences -
- Printing preferences -
- Various preferences -
- Terminal (VTE) preferences -
- Project management -
- Build menu
-
-
- Indicators -
- Default build menu items
-
-
- Compile -
- Build -
- Make -
- Make custom target -
- Make object -
- Next error -
- Previous error -
- Execute -
- Stopping running processes
-
-
- Terminal emulators +
- Preferences
-
+
- General Startup preferences -
- Set build commands +
- General Miscellaneous preferences -
- Build menu configuration -
- Build menu commands dialog
-
-
- Substitutions in commands and working directories -
- Build menu keyboard shortcuts -
- Old settings +
- Interface preferences
-
+
- Sidebar +
- Fonts +
- Miscellaneous +
+ - Interface Notebook tab preferences + +
- Interface Toolbar preferences
-
+
- Toolbar +
- Appearance +
+ - Editor Features preferences
-
+
- Features +
+ - Editor Indentation preferences + +
- Editor Completions preferences + +
- Editor Display preferences + +
- Files preferences + +
- Tools preferences
-
+
- Tool paths +
- Commands +
+ - Template preferences + +
- Keybinding preferences +
- Printing preferences +
- Various preferences +
- Terminal (VTE) preferences
- - Printing support -
- Plugins
-
-
- Plugin manager +
- Project management -
- Keybindings
-
-
- Switching documents -
- Configurable keybindings
-
-
- File keybindings -
- Editor keybindings -
- Clipboard keybindings -
- Select keybindings -
- Insert keybindings -
- Format keybindings -
- Settings keybindings -
- Search keybindings -
- Go to keybindings -
- View keybindings -
- Focus keybindings -
- Notebook tab keybindings -
- Document keybindings -
- Project keybindings -
- Build keybindings -
- Tools keybindings -
- Help keybindings +
- Build menu + +
- Printing support +
- Plugins + +
- Keybindings
-
+
- Switching documents +
- Configurable keybindings
-
+
- File keybindings +
- Editor keybindings +
- Clipboard keybindings +
- Select keybindings +
- Insert keybindings +
- Format keybindings +
- Settings keybindings +
- Search keybindings +
- Go to keybindings +
- View keybindings +
- Focus keybindings +
- Notebook tab keybindings +
- Document keybindings +
- Project keybindings +
- Build keybindings +
- Tools keybindings +
- Help keybindings
- - Configuration files
-
-
- Configuration file paths
-
-
- Paths on Unix-like systems -
- Paths on Windows +
- Configuration files
-
+
- Configuration file paths -
- Tools menu items -
- Global configuration file -
- Filetype definition files
-
-
- Filenames -
- System files -
- User files -
- Custom filetypes
-
-
- Creating a custom filetype from an existing filetype +
- Tools menu items +
- Global configuration file +
- Filetype definition files
-
+
- Filenames +
- System files +
- User files +
- Custom filetypes -
- Filetype configuration
-
-
- [styling] section
-
-
- Using a named style -
- Reading styles from another filetype +
- Filetype configuration -
- Special file filetypes.common -
- Filetype extensions -
- Filetype group membership -
- Preferences file format
-
-
- [build-menu] section +
- Filetype extensions +
- Filetype group membership +
- Preferences file format -
- Project file format
-
-
- [build-menu] additions +
- Project file format -
- Templates
-
-
- Template meta data -
- File templates
-
-
- Adding file templates +
- Templates
-
+
- Template meta data +
- File templates -
- Customizing templates
-
-
- Template wildcards -
- Customizing the toolbar -
- Plugin documentation
-
-
- HTML Characters
-
-
- Insert entity dialog -
- Replace special chars by its entity
-
-
- At typing time -
- Bulk replacement +
- Plugin documentation
-
+
- HTML Characters -
- Save Actions -
- Contributing to this document -
- Scintilla keyboard commands
-
-
- Keyboard commands +
- Contributing to this document +
- Scintilla keyboard commands -
- Tips and tricks
-
-
- Document notebook -
- Editor -
- Interface -
- GTK-related +
- Tips and tricks -
- Compile-time options
-
-
- src/geany.h -
- project.h -
- filetypes.c -
- editor.h -
- keyfile.c -
- build.c +
- Compile-time options -
- GNU General Public License -
- License for Scintilla and SciTE +
- GNU General Public License +
- License for Scintilla and SciTE
@@ -1997,6 +2004,8 @@ created by the geany -g +++Pipe-separated format
The Pipe-separated format is easier to read and write. There is one tag per line and different tag attributes are separated by the pipe character (|). A line looks like:
@@ -2016,8 +2025,9 @@ empty but the pipe separator must appear for them. Just save them in your tags directory, as described earlier in the section Global tags.-+Generating a global tags file
+Generating a global tags file
You can generate your own global tags files by parsing a list of source files. The command is:
@@ -2039,10 +2049,13 @@ don't want to specify the CFLAGS environment variable.
geany -g wxd.d.tags /home/username/wxd/wx/*.d
-Generating C/C++ tag files:
-For C/C++ tag files, gcc and grep are required, so that header files -can be preprocessed to include any other headers they depend upon.
-For C/C++ files, the environment variable CFLAGS should be set with +
++Generating C/C++ tag files
+You may need to first setup the C ignore.tags file.
+For C/C++ tag files gcc is required by default, so that header files +can be preprocessed to include any other headers they depend upon. If +you do not want this, use the -P option described above.
+For preprocessing, the environment variable CFLAGS should be set with appropriate -I/path include paths. The following example works with the bash shell, generating tags for the GnomeUI library:
@@ -2051,27 +2064,18 @@ CFLAGS=`pkg-config --cflags libgnomeui-2.0` geany -g gnomeui.c.tags \
You can adapt this command to use CFLAGS and header files appropriate for whichever libraries you want.
-Replacing the default C/C++ tags file:
-Geany currently uses a default global tags file c99.tags for -C and C++, commonly installed in /usr/share/geany. This file can -be replaced with one containing tags parsed from a different set -of header files. When Geany is next started, your custom tags file -will be loaded instead of the default c99.tags. You should keep a -copy of the generated tags file because it will get overwritten when -upgrading Geany.
-Generating tag files on Windows:
-This works basically the same as on other platforms but you need to make -sure you have grep installed and Geany can find it, i.e. it must be -in the PATH environment variable. To test this, open a console window -and type grep and see whether it is executed. -If it is, then you can create a tags file like the following:
++Generating tag files on Windows
+This works basically the same as on other platforms:
"c:\program files\geany\bin\geany" -g c:\mytags.php.tags c:\code\somefile.php
-C ignore.tags
+C ignore.tags
You can ignore certain tags for C-based languages if they would lead to wrong parsing of the code. Use the Tools->Configuration Files->ignore.tags menu item to open the user ignore.tags file. @@ -2105,7 +2109,7 @@ Exuberant Ctags.
-Preferences
+Preferences
You may adjust Geany's settings using the Edit --> Preferences dialog. Any changes you make there can be applied by hitting either the Apply or the OK button. These settings will persist between Geany @@ -2122,10 +2126,10 @@ when restarting Geany.
comes after the screenshot of that tab.-General Startup preferences
+General Startup preferences
-Startup
+Startup
- Load files from the last session
- On startup, load the same files you had open the last time you @@ -2137,7 +2141,7 @@ used Geany.
-General Miscellaneous preferences
+General Miscellaneous preferences
-Miscellaneous
+Miscellaneous
- Beep on errors when compilation has finished
- Have the computer make a beeping sound when compilation of your program @@ -2198,7 +2202,7 @@ goto line fields and the VTE.
-Interface preferences
+Interface preferences
-Sidebar
+Sidebar
- Show sidebar
- Whether to show the sidebar at all. @@ -2250,7 +2254,7 @@ to perform some common operations such as saving, closing and reloading.
-Fonts
+Fonts
- Editor
- Change the font used to display documents. @@ -2261,7 +2265,7 @@ to perform some common operations such as saving, closing and reloading.
-Miscellaneous
+Miscellaneous
- Show status bar
- Show the status bar at the bottom of the main window. It gives information about @@ -2271,10 +2275,10 @@ modifications were done, the file encoding, the filetype and other information.<
-Interface Notebook tab preferences
+Interface Notebook tab preferences
-Editor tabs
+Editor tabs
- Show editor tabs
- Show a notebook tab for all documents so you can switch between them @@ -2294,7 +2298,7 @@ when double-clicking on a notebook tab.
-Tab positions
+Tab positions
- Editor
- Set the positioning of the editor's notebook tabs to the right, @@ -2309,11 +2313,11 @@ right, left, top, or bottom of the message window.
-Interface Toolbar preferences
+Interface Toolbar preferences
Affects the main toolbar underneath the menu bar.
-Toolbar
+Toolbar
- Show Toolbar
- Whether to show the toolbar. @@ -2325,7 +2329,7 @@ This is useful to save vertical space.
-Appearance
+Appearance
- Icon Style
- Select the toolbar icon style to use - either icons and text, just @@ -2338,10 +2342,10 @@ The choice System default uses whatever icon size is set by GTK.
-Editor Indentation preferences
+Editor Indentation preferences
-Indentation group
+Indentation group
See Indentation for more information.
- Width @@ -2428,10 +2432,10 @@ meanings in different contexts - e.g. for snippet completion.
-Editor Completions preferences
+Editor Completions preferences
-Completions
+Completions
- Snippet Completion
- Whether to replace special keywords after typing Tab into a @@ -2488,7 +2492,7 @@ updated upon document saving.
-Auto-close quotes and brackets
+Auto-close quotes and brackets
Geany can automatically insert a closing bracket and quote characters when you open them. For instance, you type a ( and Geany will automatically insert ). With the following options, you can define for which @@ -2508,11 +2512,11 @@ characters this should work.
-Editor Display preferences
+Editor Display preferences
This is for visual elements displayed in the editor window.
-Display
+Display
- Invert syntax highlighting colors
- Invert all colors, by default this makes white text on a black @@ -2537,7 +2541,7 @@ Otherwise you can scroll one more page even if there are no real lines.
-Long line marker
+Long line marker
The long line marker helps to indicate overly-long lines, or as a hint to the user for when to break the line.
-
@@ -2562,7 +2566,7 @@ where it should appear.
-Virtual spaces
+Virtual spaces
Virtual space is space beyond the end of each line. The cursor may be moved into virtual space but no real space will be added to the document until there is some text typed or some other @@ -2578,10 +2582,10 @@ text insertion command is used.
-Files preferences
+Files preferences
-New files
+New files
- Open new documents from the command-line
- Whether to create new documents when passing filenames that don't @@ -2601,7 +2605,7 @@ On Unix-like systems, LF is default and CR is used on MAC systems.
-Saving files
+Saving files
Perform formatting operations when a document is saved. These can each be undone with the Undo command.
-
@@ -2623,7 +2627,7 @@ saving, avoiding mixed line endings in the same file.
-Miscellaneous
+Miscellaneous
- Recent files list length
- The number of files to remember in the recently used files list. @@ -2642,10 +2646,10 @@ not checked for changes due to performance issues
-Tools preferences
+Tools preferences
-Tool paths
+Tool paths
- Terminal
- The location of your terminal executable. @@ -2663,7 +2667,7 @@ Mingw project for instance might not work with Geany at the moment.
-Commands
+Commands
- Context action
- Set this to a command to execute on the current word. @@ -2673,13 +2677,13 @@ to the specified command.
-Template preferences
+Template preferences
This data is used as meta data for various template text to insert into a document, such as the file header. You only need to set fields that you want to use in your template files.
-Template data
+Template data
- Developer
- The name of the developer who will be creating files. @@ -2712,7 +2716,7 @@ which can be used with the ANSI C strftime function. For details please see
-Keybinding preferences
+Keybinding preferences
There are some commands listed in the keybinding dialog that are not, by default, bound to a key combination, and may not be available as a menu item.
@@ -2722,7 +2726,7 @@ bound to a key combination, and may not be available as a menu item.-Printing preferences
+Printing preferences
- Use external command for printing @@ -2744,7 +2748,7 @@ see http://man.cx/st
-Various preferences
+Various preferences
Rarely used preferences, explained in the table below. A few of them require restart to take effect, and a few other will only affect newly opened or created @@ -3020,11 +3024,11 @@ execute section of the Build menu.
The extract_filetype_regex has the default value GEANY_DEFAULT_FILETYPE_REGEX.
-Terminal (VTE) preferences
+Terminal (VTE) preferences
See also: Virtual terminal emulator widget (VTE).
-Terminal widget
+Terminal widget
- Terminal font
- Select the font that will be used in the terminal emulation control. @@ -3063,7 +3067,7 @@ like a Python console (e.g. ipython). Use this with care.
-Project management
+Project management
Project management is optional in Geany. Currently it can be used for:
- Storing and opening session files on a project basis. @@ -3081,7 +3085,7 @@ Geany is shutdown. When restarting Geany, the previously opened project file that was in use at the end of the last session will be reopened.
The project menu items are detailed below.
-New project
+New project
To create a new project, fill in the Name field. By default this will setup a new project file ~/projects/name.geany. Usually it's best to store all your project files in the same directory (they are @@ -3091,7 +3095,7 @@ can safely be set to any existing path -- it will not touch the file structure contained in it.
-Project properties
+Project properties
You can set an optional description for the project. Currently it's only used for a template wildcard - see Template wildcards.
The Base path field is used as the directory to run the Build menu commands. @@ -3103,7 +3107,7 @@ project, which can be used in the Indentation settings.
-Open project
+Open project
The Open command displays a standard file chooser, starting in ~/projects. Choose a project file named with the .geany extension.
@@ -3111,14 +3115,14 @@ extension. open files and open the session files associated with the project.-Close project
+Close project
Project file settings are saved when the project is closed.
When project session support is enabled, Geany will close the project session files and open any previously closed default session files.
-Indicators
+Indicators
Indicators are red squiggly underlines which are used to highlight errors which occurred while compiling the current file. So you can easily see where your code failed to compile. You can remove them by @@ -3154,7 +3158,7 @@ selecting Remove Error Indicators in the Document menu.
preferences.-Make custom target
+Make custom target
This is similar to running 'Make' but you will be prompted for the make target name to be passed to the Make tool. For example, typing 'clean' in the dialog prompt will run "make clean".
-Make object
+Make object
Make object will run "make current_file.o" in the same directory as the current file, using the filename for 'current_file'. It is useful for building just the current file without building the whole project.
-Previous error
+Previous error
The previous error item will move to the previous detected error in the file.
-Execute
+Execute
Execute will run the corresponding executable file, shell script or interpreted script in a terminal window. Note that the Terminal tool path must be correctly set in the Tools tab of the Preferences dialog - @@ -3236,7 +3240,7 @@ output from the program before the terminal window is closed.
-Stopping running processes
+Stopping running processes
When there is a running program, the Execute menu item in the menu and the Run button in the toolbar each become a stop button so you can stop the current running program (and @@ -3245,7 +3249,7 @@ any child processes). This works by sending the SIGQUIT signal to the process.
-Terminal emulators
+Terminal emulators
Xterm is known to work properly. If you are using "Terminal" (the terminal program of Xfce), you should add the command line option --disable-server otherwise the started process cannot be @@ -3254,7 +3258,7 @@ tab in the terminal field.
-Set build commands
+Set build commands
By default Compile, Build and Execute are fairly basic commands. You may wish to customise them using Set Build Commands.
E.g. for C you can add any include paths and compile flags for the @@ -3263,7 +3267,7 @@ arguments you want to use when running Execute.
-Printing support
+Printing support
Since Geany 0.13 there has been printing support using GTK's printing API. The printed page(s) will look nearly the same as on your screen in Geany. Additionally, there are some options to modify the printed page(s).
@@ -3551,7 +3555,7 @@ command line). gtklp or similar programs can be used.-Plugins
+Plugins
Plugins are loaded at startup, if the Enable plugin support general preference is set. There is also a command-line option, -p, which prevents plugins being loaded. Plugins are scanned in @@ -3567,7 +3571,7 @@ the following directories:
See also Plugin documentation for information about single plugins which are included in Geany.
-Plugin manager
+Plugin manager
The Plugin Manager dialog lets you choose which plugins should be loaded at startup. You can also load and unload plugins on the fly using this dialog. Once you click the checkbox for a specific plugin @@ -3578,13 +3582,13 @@ provides any.
-Keybindings
+Keybindings
Geany supports the default keyboard shortcuts for the Scintilla editing widget. For a list of these commands, see Scintilla keyboard commands. The Scintilla keyboard shortcuts will be overridden by any custom keybindings with the same keyboard shortcut.
-Switching documents
+Switching documents
There are some non-configurable bindings to switch between documents, listed below. These can also be overridden by custom keybindings.
@@ -3609,7 +3613,7 @@ listed below. These can also be overridden by custom keybindings.
See also Notebook tab keybindings.
-Configurable keybindings
+Configurable keybindings
For all actions listed below you can define your own keybindings. Open the Preferences dialog, select the desired action and click on change. In the resulting dialog you can press the key combination you @@ -3627,7 +3631,7 @@ either Ctrl-O or Alt-O.
which are common to many applications are marked with (C) after the shortcut.-Search keybindings
+Search keybindings
@@ -4125,7 +4129,7 @@ find, highlighted matches will be cleared. -Go to keybindings
+Go to keybindings
@@ -4217,7 +4221,7 @@ If the line is not wrapped, it behaves like -Help keybindings
+Help keybindings
@@ -4589,13 +4593,13 @@ the last build process. -Configuration files
+Configuration files
Warning
You must use UTF-8 encoding without BOM for configuration files.
-Configuration file paths
+Configuration file paths
Geany has default configuration files installed for the system and also per-user configuration files.
The system files should not normally be edited because they will be @@ -4614,14 +4618,14 @@ Geany-INFO: System data dir: /usr/share/geany Geany-INFO: User config dir: /home/username/.config/geany
-Paths on Unix-like systems
+Paths on Unix-like systems
The system path is $prefix/share/geany, where $prefix is the path where Geany is installed (see Installation prefix).
The user configuration directory is normally: /home/username/.config/geany
-Paths on Windows
+Paths on Windows
The system path is the data subfolder of the installation path on Windows.
The user configuration directory might vary, but on Windows XP it's: @@ -4629,7 +4633,7 @@ on Windows.
-Global configuration file
+Global configuration file
System administrators can add a global configuration file for Geany which will be used when starting Geany and a user configuration file does not exist.
@@ -4669,14 +4673,14 @@ need to do that.-Filetype definition files
+Filetype definition files
All color definitions and other filetype specific settings are stored in the filetype definition files. Those settings are colors for syntax highlighting, general settings like comment characters or word delimiter characters as well as compiler and linker settings.
See also Configuration file paths.
-Filenames
+Filenames
Each filetype has a corresponding filetype definition file. The format for built-in filetype Foo is:
@@ -4717,7 +4721,7 @@ filetypes.Foo.conf
See the link for details.
-System files
+System files
The system-wide filetype configuration files can be found in the system configuration path and are called filetypes.$ext, where $ext is the name of the filetype. For every @@ -4731,7 +4735,7 @@ because they will be overridden when Geany is updated.
-User files
+User files
To change the settings, copy a file from the system configuration path to the subdirectory filedefs in your user configuration directory. Then you can edit the file and the changes will still be @@ -4741,7 +4745,7 @@ settings you want to change. All missing settings will be read from the corresponding system configuration file.
-Custom filetypes
+Custom filetypes
At startup Geany looks for filetypes.*.conf files in the system and user filetype paths, adding any filetypes found with the name matching the '*' wildcard - e.g. filetypes.Bar.conf.
@@ -4767,7 +4771,7 @@ support for the following has been implemented:See Filetype configuration for details on each setting.
-Creating a custom filetype from an existing filetype
+Creating a custom filetype from an existing filetype
Because most filetype settings will relate to the syntax highlighting (e.g. styling, keywords, lexer_properties sections), it is best to copy an existing filetype file that uses @@ -4788,11 +4792,11 @@ list, or none.
-Filetype configuration
+Filetype configuration
As well as the sections listed below, each filetype file can contain a [build-menu] section as described in [build-menu] section.
-[styling] section
+[styling] section
In this section the colors for syntax highlighting are defined. The manual format is:
-
@@ -4812,7 +4816,7 @@ value is something other than "true" or "false", "false
This makes the key style have red foreground text, default background color text and bold emphasis.
-Using a named style
+Using a named style
The second format uses a named style name to reference a style defined in filetypes.common.
-
@@ -4830,7 +4834,7 @@ italic emphasis.
Section.
-Reading styles from another filetype
+Reading styles from another filetype
You can automatically copy all of the styles from another filetype definition file by using the following syntax for the [styling] group:
@@ -4849,7 +4853,7 @@ styling the same as the C styling, you would put the following in-[keywords] section
+[keywords] section
This section contains keys for different keyword lists specific to the filetype. Some filetypes do not support keywords, so adding a new key will not work. You can only add or remove keywords to/from @@ -4860,7 +4864,7 @@ an existing list.
-[lexer_properties] section
+[lexer_properties] section
Here any special properties for the Scintilla lexer can be set in the format key.name.field=some.value.
Properties Geany uses are listed in the system filetype files. To find @@ -4870,7 +4874,7 @@ egrep -o 'GetProperty\w*\("([^"]+)"[^)]+\)' scintilla/Lex*.cxx
-[settings] section
+[settings] section
- extension
This is the default file extension used when saving files, not @@ -4993,7 +4997,7 @@ this setting in their system configuration files.
-[indentation] section
+[indentation] section
This section allows definition of default indentation settings specific to the file type, overriding the ones configured in the preferences. This can be useful for file types requiring specific indentation settings (e.g. tabs @@ -5029,7 +5033,7 @@ only for Makefile). These settings don't override auto-detection if activated.<
-[build_settings] section
+[build_settings] section
As of Geany 0.19 this section is supplemented by the [build-menu] section. Values that are set in the [build-menu] section will override those in this section.
-
@@ -5082,7 +5086,7 @@ complete filename, e.g. for shell scripts.
-Special file filetypes.common
+Special file filetypes.common
There is a special filetype definition file called filetypes.common. This file defines some general non-filetype-specific settings.
@@ -5097,7 +5101,7 @@ the system file.See the Filetype configuration section for how to define styles.
-[named_styles] section
+[named_styles] section
Named styles declared here can be used in the [styling] section of any filetypes.* file.
For example:
@@ -5122,7 +5126,7 @@ original style.-[named_colors] section
+[named_colors] section
Named colors declared here can be used in the [styling] or [named_styles] section of any filetypes.* file or color scheme.
For example:
@@ -5138,7 +5142,7 @@ foo=my_red_color;my_blue_color;false;true scheme-wide only involves changing the hex value in a single location.-[styling] section
+[styling] section
- default
This is the default style. It is used for styling files without a @@ -5322,7 +5326,7 @@ arguments set whether to use the defined colors.
-[settings] section
+[settings] section
- whitespace_chars
Characters to treat as whitespace. These characters are ignored @@ -5336,7 +5340,7 @@ when moving, selecting and deleting across word boundaries
-Filetype extensions
+Filetype extensions
To change the default filetype extension used when saving a new file, see Filetype definition files.
You can override the list of file extensions that Geany uses to detect @@ -5356,7 +5360,7 @@ Make=Makefile*;*.mk;Buildfile;
-Filetype group membership
+Filetype group membership
Group membership is also stored in filetype_extensions.conf. This file is used to store information Geany needs at startup, whereas the separate filetype definition files hold information only needed when @@ -5377,13 +5381,13 @@ None=None;
-Preferences file format
+Preferences file format
The user preferences file geany.conf holds settings for all the items configured in the preferences dialog. This file should not be edited while Geany is running as the file will be overwritten when the preferences in Geany are changed or Geany is quit.
-Project file format
+Project file format
The project file contains project related settings and possibly a record of the current session files.
-Templates
+Templates
Geany supports the following templates:
- ChangeLog entry @@ -5464,7 +5468,7 @@ save a file in the user's template configuration directory. You can also force this by selecting Tools->Reload Configuration.
-Template meta data
+Template meta data
Meta data can be used with all templates, but by default user set meta data is only used for the ChangeLog and File header templates.
In the configuration dialog you can find a tab "Templates" (see @@ -5472,7 +5476,7 @@ meta data is only used for the ChangeLog and File header templates.
which will be inserted in the templates.-File templates
+File templates
File templates are templates used as the basis of a new file. To use them, choose the New (with Template) menu item from the File menu.
@@ -5484,7 +5488,7 @@ optional template wildcards like {fileheader}. wildcard can be placed anywhere, but it's usually put on the first line of the file, followed by a blank line.-Adding file templates
+Adding file templates
File templates are read from templates/files under the Configuration file paths.
The filetype to use is detected from the template file's extension, if @@ -5495,7 +5499,7 @@ clicked.
-Customizing templates
+Customizing templates
Each template can be customized to your needs. The templates are stored in the ~/.config/geany/templates/ directory (see the section called Command line options for further information about the configuration @@ -5503,7 +5507,7 @@ directory). Just open the desired template with an editor (ideally, Geany ;-) ) and edit the template to your needs. There are some wildcards which will be automatically replaced by Geany at startup.
-Template wildcards
+Template wildcards
All wildcards must be enclosed by "{" and "}", e.g. {date}.
Wildcards for character escaping
@@ -5716,7 +5720,7 @@ will only be replaced in file templates.
-Special {command:} wildcard
+Special {command:} wildcard
The {command:} wildcard is a special one because it can execute a specified command and put the command's output (stdout) into the template.
@@ -5751,14 +5755,14 @@ standard error and in the Help->Debug Messages dialog.-Customizing the toolbar
+Customizing the toolbar
You can add, remove and reorder the elements in the toolbar by using the toolbar editor, or by manually editing the configuration file ui_toolbar.xml.
The toolbar editor can be opened from the preferences editor on the Toolbar tab or by right-clicking on the toolbar itself and choosing it from the menu.
-Manually editing the toolbar layout
+Manually editing the toolbar layout
To override the system-wide configuration file, copy it to your user configuration directory (see Configuration file paths).
For example:
@@ -5780,7 +5784,7 @@ will be used instead.-Available toolbar elements
+Available toolbar elements
@@ -5894,13 +5898,13 @@ use 'SearchEntry') -Plugin documentation
+Plugin documentation
-HTML Characters
+HTML Characters
The HTML Characters plugin helps when working with special characters in XML/HTML, e.g. German Umlauts ü and ä.
-Insert entity dialog
+Insert entity dialog
When the plugin is enabled, you can insert special character entities using Tools->Insert Special HTML Characters.
This opens up a dialog where you can find a huge amount of special @@ -5912,7 +5916,7 @@ the entity for the character at the current cursor position. You might also like to double click the chosen entity instead.
-Replace special chars by its entity
+Replace special chars by its entity
To help make a XML/HTML document valid the plugin supports replacement of special chars known by the plugin. Both bulk replacement and immediate replacement during typing are supported.
@@ -5928,7 +5932,7 @@ replacement and immediate replacement during typing are supported.-At typing time
+At typing time
You can activate/deactivate this feature using the Tools->HTML Replacement->Auto-replace Special Characters menu item. If it's activated, all special characters (beside the given exceptions from @@ -5937,7 +5941,7 @@ above) known by the plugin will be replaced by their entities.
of this feature.-Bulk replacement
+Bulk replacement
After inserting a huge amount of text, e.g. by using copy & paste, the plugin allows bulk replacement of all known characters (beside the mentioned exceptions). You can find the function under the same @@ -5947,9 +5951,9 @@ configure a keybinding for the plugin.
-Save Actions
+Save Actions
-Instant Save
+Instant Save
This plugin sets on every new file (File->New or File->New (with template)) a randomly chosen filename and set its filetype appropriate to the used template or when no template was used, to a configurable default filetype. @@ -5959,7 +5963,7 @@ useful when you often create new files just for testing some code or something similar.
-Backup Copy
+Backup Copy
This plugin creates a backup copy of the current file in Geany when it is saved. You can specify the directory where the backup copy is saved and you can configure the automatically added extension in the configure dialog @@ -5970,7 +5974,7 @@ copied into the configured backup directory when the file is saved in Geany.
-Contributing to this document
+Contributing to this document
This document (geany.txt) is written in reStructuredText (or "reST"). The source file for it is located in Geany's doc subdirectory. If you intend on making changes, you should grab the @@ -5990,7 +5994,7 @@ to build the docs. The package is named
-Scintilla keyboard commands
+Scintilla keyboard commands
Copyright © 1998, 2006 Neil Hodgson <neilh(at)scintilla(dot)org>
This appendix is distributed under the terms of the License for Scintilla and SciTE. A copy of this license can be found in the file @@ -5999,7 +6003,7 @@ program and in the appendix of this document. See .
20 June 2006
-Keyboard commands
+Keyboard commands
Keyboard commands for Scintilla mostly follow common Windows and GTK+ conventions. All move keys (arrows, page up/down, home and end) allows to extend or reduce the stream selection when holding the @@ -6082,9 +6086,9 @@ menus. Some less common commands with no menu equivalent are:
-Tips and tricks
+Tips and tricks
-Document notebook
+Document notebook
- Double-click on empty space in the notebook tab bar to open a new document. @@ -6097,7 +6101,7 @@ shortcut). The interface pref must be enabled for this to work.
-Compile-time options
+Compile-time options
There are some options which can only be changed at compile time, and some options which are used as the default for configurable options. To change these options, edit the appropriate source file @@ -6140,7 +6144,7 @@ not be changed.
Most users should not need to change these options.
-keyfile.c
+keyfile.c
These are default settings that can be overridden in the Preferences dialog.
@@ -6358,7 +6362,7 @@ files. The GEANY_DEFAULT_FILETYPE_REGEX default value is -\*-\s*([^\s]+)\s*-\*- which finds Emacs filetypes.
-build.c
+build.c
@@ -6403,7 +6407,7 @@ overriding the compile setting. -GNU General Public License
+GNU General Public License
GNU GENERAL PUBLIC LICENSE Version 2, June 1991 @@ -6748,7 +6752,7 @@ Public License instead of this License.-License for Scintilla and SciTE
+License for Scintilla and SciTE
Copyright 1998-2003 by Neil Hodgson <neilh(at)scintilla(dot)org>
All Rights Reserved
Permission to use, copy, modify, and distribute this software and @@ -6768,7 +6772,7 @@ USE OR PERFORMANCE OF THIS SOFTWARE.
diff --git a/doc/geany.txt b/doc/geany.txt index 89b20cc4..2c3a2fa0 100644 --- a/doc/geany.txt +++ b/doc/geany.txt @@ -1593,6 +1593,8 @@ Different tag attributes like the return value or the argument list are separated with different characters indicating the type of the following argument. +Pipe-separated format +********************* The Pipe-separated format is easier to read and write. There is one tag per line and different tag attributes are separated by the pipe character (``|``). A line looks like:: @@ -1637,12 +1639,15 @@ Example for the wxD library for the D programming language:: geany -g wxd.d.tags /home/username/wxd/wx/*.d -*Generating C/C++ tag files:* +Generating C/C++ tag files +************************** +You may need to first setup the `C ignore.tags`_ file. -For C/C++ tag files, gcc and grep are required, so that header files -can be preprocessed to include any other headers they depend upon. +For C/C++ tag files gcc is required by default, so that header files +can be preprocessed to include any other headers they depend upon. If +you do not want this, use the ``-P`` option described above. -For C/C++ files, the environment variable CFLAGS should be set with +For preprocessing, the environment variable CFLAGS should be set with appropriate ``-I/path`` include paths. The following example works with the bash shell, generating tags for the GnomeUI library:: @@ -1653,28 +1658,13 @@ You can adapt this command to use CFLAGS and header files appropriate for whichever libraries you want. -*Replacing the default C/C++ tags file:* - -Geany currently uses a default global tags file c99.tags for -C and C++, commonly installed in /usr/share/geany. This file can -be replaced with one containing tags parsed from a different set -of header files. When Geany is next started, your custom tags file -will be loaded instead of the default c99.tags. You should keep a -copy of the generated tags file because it will get overwritten when -upgrading Geany. - -*Generating tag files on Windows:* - -This works basically the same as on other platforms but you need to make -sure you have grep installed and Geany can find it, i.e. it must be -in the PATH environment variable. To test this, open a console window -and type ``grep`` and see whether it is executed. -If it is, then you can create a tags file like the following:: +Generating tag files on Windows +******************************* +This works basically the same as on other platforms:: "c:\program files\geany\bin\geany" -g c:\mytags.php.tags c:\code\somefile.php - C ignore.tags ^^^^^^^^^^^^^
- HTML Characters
- [styling] section
- Configuration file paths
