## This file has been auto generated from makeman.tcl ## on date Sat Feb 19 20:12:12 CET 2000 ## ## proc createHelpPage {prefix} { global __help_ref __help_headers __BASEDIR __system set __help_headers {{{How to use this help page} h1 1.4} {{Help page layout} h2 4.6} {{Introduction} h1 13.4} {{Navigating The Dotfile Generator } h1 20.4} {{The load page } h2 23.6} {{The detail page } h3 32.8} {{The configuration page } h2 39.6} {{Layout} h3 42.8} {{The ExtEntry } h2 55.6} {{Adding elements } h3 58.8} {{Cut Copy and Paste } h3 65.8} {{Index element } h3 73.8} {{FillOut} h2 79.6} {{Window } h2 84.6} {{Command } h2 89.6} {{Menus} h1 96.4} {{File } h2 99.6} {{Generate } h3 102.8} {{Regenerate } h3 105.8} {{Save } h3 108.8} {{Save As } h3 115.8} {{Export } h3 118.8} {{Reload } h3 123.8} {{Quit } h3 126.8} {{Setup } h2 129.6} {{Options } h3 132.8} {{Manage Save/Export Files } h3 145.8} {{Mail } h2 148.6} {{Help } h2 153.6} {{About } h3 156.8} {{Help Page } h3 159.8} {{How to use the output } h3 162.8} {{More information } h1 165.4} {{---------------} h1 170.4} {{Bash module} h1 173.4} {{Configuration pages} h1 177.4} {{User/Bash interface} h2 180.6} {{Prompting} h3 183.8} {{Command aliases} h3 187.8} {{Command history} h3 190.8} {{Commandline} h3 193.8} {{Completion} h3 196.8} {{Job control} h3 199.8} {{Keyboard bindings} h3 202.8} {{Mail check} h3 205.8} {{TTY appearance} h3 208.8} {{System/Bash interface} h2 211.6} {{Error handling} h3 214.8} {{File and directory handling} h3 217.8} {{Paths} h3 220.8} {{System limits} h3 223.8} {{Bash version} h3 226.8} {{How to use the output } h1 229.4} {{How to use .bashrc options} h2 235.6} {{How to use .inputrc options} h2 241.6}} set __help_ref(Mail_check) {203.304} set __help_ref(Command_history) {188.774} set __help_ref(navigating) {20.4} set __help_ref(manuals) {165.4} set __help_ref(scissors) {65.8} set __help_ref(System/Bash_interface) {209.129} set __help_ref(Completion) {194.158} set __help_ref(menu_helppage) {159.8} set __help_ref(load_detail) {32.8} set __help_ref(extentry_newElm) {58.8} set __help_ref(extentry_index) {73.8} set __help_ref(menu_reload) {123.8} set __help_ref(User/Bash_interface) {178.323} set __help_ref(menu_file) {99.6} set __help_ref(menu_setup) {129.6} set __help_ref(howToUse) {229.4} set __help_ref(Error_handling) {212.326} set __help_ref(Commandline) {191.466} set __help_ref(menu_about) {156.8} set __help_ref(menu_mail) {148.6} set __help_ref(menu_quit) {126.8} set __help_ref(menu_saveas) {115.8} set __help_ref(menu_generate) {102.8} set __help_ref(Paths) {218.121} set __help_ref(TTY_appearance) {206.280} set __help_ref(Command_aliases) {185.0} set __help_ref(Prompting) {181.142} set __help_ref(menu_options) {132.8} set __help_ref(window) {84.6} set __help_ref(menus) {96.4} set __help_ref(File_and_directory_handling) {215.86} set __help_ref(menu_howToUse) {162.8} set __help_ref(Bash_version) {224.194} set __help_ref(Job_control) {197.462} set __help_ref(menu_save) {108.8} set __help_ref(configpage) {39.6} set __help_ref(extentry) {55.6} set __help_ref(menu_help) {153.6} set __help_ref(menu_manage) {145.8} set __help_ref(loadpage) {23.6} set __help_ref(System_limits) {221.267} set __help_ref(Keyboard_bindings) {200.821} set __help_ref(menu_export) {118.8} set __help_ref(menu_regenerate) {105.8} set __help_ref(command) {89.6} $prefix insert end {1. How to use this help page In the Dotfile Generators help page you will find information about the Dotfile Generator, and it's behavior. Furthermore the modules may insert text, which will describe complicated features, which is difficult to describe on a single configuration page . 1.1. Help page layout In the following list you'll see the different parts of the help page. Index list In the index list you can see all the section headers in the help text. Help text The help text is of course the box showing the actual help text. Left and Right arrows These two buttons let you travel back and forth in your history list . This is just like you know them from you favorite web browser. Search String In the entry at the bottom of the page you can can search for a string in the help text. The search is case insensitive and it will search from the current position in the help text. Up and Down arrows These two arrows will bring you to the previous/next match in your search. Note : This help file is also available via WWW 2. Introduction The Dotfile Generator is a configuration tool, which let you configure those awful dotfiles almost every unix program has. For the Dotfile Generator to configure a given program, it needs a module. To see which modules are installed on your system, type dotfile without any arguments in your shell. To configure a program you will start the Dotfile Generator with the given module name as argument (as you already did). This will most likely bring up a load page , where you can select a predefined setup to load. When you've selected one, The Dotfile Generator will show a menu structure, which resembles a directory browser. This menu structure represent several configuration pages . The pages contains the actual configuration options, and when you've configured all to your hearts content, you will generate , which will result in a configuration file for the given program. The most important thing to know about The Dotfile Generator is that help is available all the time, just press the right mouse button over the element you wish to know more about, and help will be shown either in the help region at the button of the configuration page or in the help browser you are looking at. 3. Navigating The Dotfile Generator In this section a description can be found on the different elements/pages of The Dotfile Generator. If you read this continually, please bear in mind that the help description is written so it is self contained and can be referenced to from the different pages and menus in The Dotfile Generator. 3.1. The load page The load page, is the one which is shown, when you start The Dotfile Generator, or when you select Reload in the File menu. This page lets you (re)load a given setup, either one you have created yourself, one that came with The Dotfile Generator, or sometimes even the one which is located in your original dotfile. You may chose to load only some of the configuration pages or all the pages in the module. To select only some of the pages, click the Details button. If you came to this page, from the Reload menu, you may also choose to reset some of the pages, which means that all configuration on the given page(s) will be deleted. This is equivalent to pressing the Cancel button at startup. 3.1.1. The detail page On the Detail page, you can select which configuration pages to load, reload or reset. For export files you may choose either to merge the existing page with the one shown in the item, or you may overwrite the exiting page, with the one in the item. Merge means that elements of ExtEntries , will be merged, ie. the elements will be added to the elements of the ExtEntry. Overwrite means that the existing page will be totally overwritten. Both menu items and configuration pages are shown, and when selecting a menu item, you will (de)select all the items below this menu item. 3.2. The configuration page The configuration pages are the places where you configure your program. Only one page is visible at a time, though this page may have several Window widgets . 3.2.1. Layout In the title bar of the window you can see which page you are configuring, this is very useful when you travel all the pages of the module. At the bottom of the page you can see which pages will be generated. See the setup menu for the different possibilities. Above this, you will see some text. This is the help region. All help for the configuration page is located there. When you enter the page, general information about the page is located there. Later when you press the right mouse button on one of the elements of the page, you will see the help associated with this element in the help region. The rest of the page is configuration options. These are built from entries, check buttons, pull down menus, combo boxes and list boxes. For further information on these elements, please refer to the user manual . There are a few extra elements, however, which are specific for The Dotfile Generator, and they will be described below. 3.3. The ExtEntry The ExtEntry is an element, which repeats other elements several times. It is used for configurations, which the user may have zero, one or many of. Your search path in the shell is a good example of this sort of information. You may have a number of directories, in which the shell may search for executables. 3.3.1. Adding elements To add a new tuple to an extentry, you have to press the button, which look like this: This will also locate the new element in the view of the ExtEntry. 3.3.2. Cut Copy and Paste The tuples in the ExtEntry may be treated just like they were basic elements. Under the icon which look like this: is located a pull down menu with the following items: Cut This will copy the tuple to the clipboard, and remove it from the ExtEntry. Copy This will copy the tuple to the clipboard, and leave it in the ExtEntry. Paste This will copy the tuple from the clipboard into the ExtEntry, just before the one in which the scissors was invoked. Insert Blank This will insert an empty tuple, just before the one in which the scissors was invoked. 3.3.3. Index element An ExtEntry may be arbitraryly big, by that reason some of them have an index element. This index element is used to travel to an other tuple in the ExtEntry, without having to scroll all the way to it. If an ExtEntry has an index element, a button which look like this: is located next to it. If you press this button a listbox will show up, and in it you can select the index element associated with the tuple you want to go to. When you've selected one, The Dotfile Generator will scroll the ExtEntry to this tuple. 3.4. FillOut The FillOut widget is used to type some text, which is built from tokens and ordinary text. An example of this is the prompt in your shell. It is composed by a listbox and an entry. In the entry you can type ordinary text and insert tokens from the listbox within this text. The elements of the listbox may either be a basic token, or may be a configurable one. The configuration is, of course, done with basic Dotfile Generator widgets. 3.5. Window The configurations on one configuration page, may be located in several windows. This is especially useful, inside ExtEntries . A window widget is just a button, which brings up the window when it's pressed. 3.6. Command In addition to The Dotfile Generator's standard widget, there may be added some additional widgets, which all bring up a configuration page. At this moment the following widgets exists: Color Widget This widget will let you select a color, either by name or by dragging three scales representing the three basic colors: red, green and blue. Font Widget Here you select a font, either by name or by it's basic attributes (font name, font size etc.) File/Directory Browser This is an ordinary browser, which you surely know from other applications. 4. Menus At the top of the main window, there is located three pull down menus. These contain links to different actions, configuration pages and help pages. The menus may be torn off, which is done by selecting the dashes at the top of the pull down menu. 4.1. File 4.1.1. Generate This is the most important function in The Dotfile Generator. This is the one which converts your configurations to the code of the program you are configuring. The code will be shown in a window and written to file(s). This can however be configured in the setup menu . To see how to use the output, please refer to the section below 4.1.2. Regenerate To generate a large module may take awhile. This delay will be annoying, if you play around with the different options on a page. To avoid this, you can regenerate the single page you are working on, and let the other part of the configuration file be. To do this you have to generate the whole module first! 4.1.3. Save This will save your configuration in a file, which lets you continue your configuration in a later Dotfile Generator session. You can (re)load the save files from the load menu This format is version dependent (both The Dotfile Generator version and module version). It is however very fast compared to the export format . 4.1.4. Save As This will save your configuration to the file you specify. 4.1.5. Export This will export your configuration to an export format. This format is version independent. However it is very slow to import from. So this format should only be used, if you want to upgrade your Dotfile Generator, or give your configuration to someone who uses The Dotfile Generator. (ver 2.0 or later.) The export format is also used if the module has a filter, which can convert from the original dotfile to configuration in The Dotfile Generator. 4.1.6. Reload This will let you reload /reset one or more configuration pages . 4.1.7. Quit This will quit The Dotfile Generator. If you have any unsaved changes, you will be offered to save these. 4.2. Setup 4.2.1. Options In the options menu you can configure how The Dotfile Generator behaves. It contains the following options: Name of the file(s) to generate to. At the top of the setup window you can specify which file(s) to generate to, and the comment character for the given file. What to generate. Next you can select where you want the generated code to go: Either in file(s), in window(s) on the screen, or both. How much to generate. You can specify how many pages you which to generate: One page. The Dotfile Generator will only generate the current visible configuration page. This is useful, if you experiment with The Dotfile Generator, to see what it generates for the different widgets. Selected pages. The Dotfile Generator will only generated the pages, which you select. The selection is done at the bottom of the configuration page . All pages. All the configuration pages are generated. Generate Defaults? Some of the programs configured by The Dotfile Generator has default values, which is set when the option is not specified at all in the configuration file. If you append the output from The Dotfile Generator to the original configuration file, then this is useful to ensure that the settings in The Dotfile Generator will overwrite the original, which may be located in your configuration file. Save when Generating. When you generate your module, you'll often want to save too. Here you can tell The Dotfile Generator to do this for you automatically. Place windows. If your window manager asks you to place the windows, you may tell The Dotfile Generator that it shall place them for you. This may be useful... 4.2.2. Manage Save/Export Files This will let you configure the header and description on the save- and export files. 4.3. Mail You can mail either a suggestion/comment, a bug report, or a postcard from The Dotfile Generator. The postcard is only for encouraging the programmers to make their job even better, after all... if no one is using our product, we may not want to spend so much time on it. 4.4. Help 4.4.1. About This will bring up a window with version information about The Dotfile Generator and the current module. 4.4.2. Help Page This will bring up this help page. 4.4.3. How to use the output This is a link into the help page, which the module programmer has written. It should tell you how to use the output from the current module. 5. More information The Dotfile Generator has a home page , which you may wish to check out. A manual on how to write modules for The Dotfile Generator is also available on the net. A mailing list exists for The Dotfile Generator. You may subscribe by sending a mail to dotfile-request@imada.sdu.dk with the subject subscribe. To unsubscribe, let the subject be unsubscribe. \n\n 6. --------------- 7. Bash module This module will help you configure Bash versions ranging from 1.14.4 to 2.0. The module consists of 17 configuration pages, where you can setup options as shell prompt, command aliases, completion, error handling and much more. Before generating your configuration options, please make sure you have choosen the right version of Bash (default 1.14.4 to 2.0). 8. Configuration pages Below you will find a list of configuration pages in this module. You can use it to get an overview of the module, and if needed a small description of each page is included. For further information on each configuration option on the individual pages, as well as the the generated output, please read the reference guide. 8.1. User/Bash interface In this section you can configure options concerning the interaction between User and Bash (i.e. commandline, completion and prompting, etc.) 8.1.1. Prompting A collection of pages, that will help you setup how Bash is to prompt you. 8.1.2. Command aliases UNIX often have commands with very cryptic names, or numerous arguments you have to remember/type each time you use the command/program. With aliases you are saved from that kind of annoyances. If you are familiar with C shells (like Tcsh), the major difference is you cannot use arguments in alias expansions-the alias function in Bash can be compared with search-and-replace. The use of arguments is provided by functions , a sort of script-within-a-script, which you can use to define some shell code by name and store it in the shell's memory, to be invoked and run later. Due to the versatility of functions, you can not define functions (-maybe in a later version), but are you interested in writing shell functions, I can recommend the book Learning the bash Shell . 8.1.3. Command history This configuration page will help you setup the history function of Bash. The history mechanism records your commands, and is very useful if you make a mistake. Instead of retyping the entire commandline, you just recall the command, fix the mistake and re-execute the command. Bash has several ways to edit old commands; either by using incremental search for a single commandline by using up and down cursor keys, or using the builtin fc ( f ix c ommand) command. 8.1.4. Commandline This configuration page will help you setup options concerning the commandline. In particular which editing mode is prefered, how to respond to scripts, etc. 8.1.5. Completion This page will help you setup options concerning completion and globbing. You can complete a commandline typing TAB. Bash will complete the line based on the text before point. Bash attempts completion treating the text as a variable (if the text begins with $), username (if the text begins with ~), hostname (if the text begins with @), or command (including aliases and functions) in turn. If none of these produces a match, filename completion is attempted. 8.1.6. Job control Job control refers to the ability to selectively stop ( suspend ) the execution of processes and continue ( resume ) their execution at a later point. A user typically employs this facility via an interactive interface supplied jointly by the system's terminal driver and Bash. If the operating system on which Bash is running supports job control, Bash allows you to use it. Typing the suspend character (typically ^Z , CTRL-z) while a process is running causes that process to be stopped and returns you to Bash. You may then manupulate the state of this job, using the bg command to continue it in the background, the fg command to continue it in the foreground, or the kill command to kill it. A ^Z takes effect immediately, and has the additional side effect of causing pending output and typeahead to be discarded. 8.1.7. Keyboard bindings Here you can setup keyboard macros. A macro is simply a sequeence of keystrokes or a builtin (readline) command. Typing the key sequence causes the keys in the macro to be entered as though you had typed them. Some of the readline commands and their bindings you can see in Bash module reference guide . 8.1.8. Mail check You can make Bash check for incoming mail, if you should choose to. The shell can't actually check for incoming mail, but it check your mail file periodically and dertermine whether the file has been modified since last check. Here you can setup how often, what file(s) to check. 8.1.9. TTY appearance This configuration page covers topics as screen dimensions, bell style, how to react on commandline exceeding screen width, etc. 8.2. System/Bash interface Here you can configure options that have no affect on interactive communication with user-not directly anyway. In this group options on file creation, path search, etc. is found. Please remember, options in this section is to be altered with much care, as much of this information is essential for the shell to work properly. 8.2.1. Error handling This configuration page will help you to setup options concerning certain exceptions. 8.2.2. File and directory handling This configuration page will help you to setup options concerning file and directory handling, how to follow links, etc. 8.2.3. Paths This configuration page will help you to setup paths. If a path is already defined, the Bash module will attempt to read it and auto-fillout the entries. You can then add, or delete in the list as you please, just bear in mind not to compromise with system security. 8.2.4. System limits This configuration page will help you to setup how system resources are shared, e.g. how much disk space a user file may allocate, how much memory and CPU-time a user process can allocate, etc. 8.2.5. Bash version In contrast to the other configuration pages, this page will not create any output, when generating. Here you can specify which version of Bash you want to generate dot.files for. 9. How to use the output This module generate options used by the following two files: .bashrc which is used for configuring Bash, and .inputrc holding Readline options (Readline is the builtin Bash commandline editor). 9.1. How to use .bashrc options You have to options: - You may generate directly to your ~/.bashrc file. This is recomented if you do NOT have a ~/.bashrc file allready, and do NOT plan to add additional code to the output (i.e. conditions). - You may generate to an other file than ~/.bashrc (e.g. ~/.bash-dotfile ). this file may then be sourced in your original ~/.bashrc file, with the command source . The source line may look like this: source ~/.bash-dotfile 9.2. How to use .inputrc options Where .bashrc allows you to link in other configuration files, .inputrc does not allow such linking. Therefore you have the following options: - You may generate directly to your ~/.inputrc file. This is recomented if you do NOT have a ~/.inputrc file allready, and do NOT plan to add additional code to the output. - You may copy from the file generated by the Dotfile Generator ( ~/.inputrc-dotfile ) to your /~.inputrc . When using simple cut-and-paste, please remember to add your auto- generated information at the bottom--in this way other old configurations are overwritten by your new choice. Good luck! Second edition, 1997 January 27 Per Zacho } label $prefix.img1 -bitmap @$__BASEDIR/Generator/bitmaps/new.xbm $prefix window create 59.87 -window $prefix.img1 label $prefix.img2 -bitmap @$__BASEDIR/Generator/bitmaps/scissors.xbm $prefix window create 66.115 -window $prefix.img2 label $prefix.img3 -bitmap @$__BASEDIR/Generator/bitmaps/idx.xbm $prefix window create 76.68 -window $prefix.img3 $prefix tag configure rmedium240 -font {-*-helvetica-medium-r-*-*-*-240-*-*-*-*-*-*} $prefix tag add rmedium240 1.0 1.29 13.0 13.16 20.0 20.37 96.0 96.9 165.0 165.21 170.0 170.19 173.0 173.15 177.0 177.23 229.0 229.26 $prefix tag configure rbold180 -font {-*-helvetica-bold-r-*-*-*-180-*-*-*-*-*-*} $prefix tag add rbold180 235.17 235.24 241.17 241.25 $prefix tag configure rmedium180 -font {-*-helvetica-medium-r-*-*-*-180-*-*-*-*-*-*} $prefix tag add rmedium180 4.0 4.22 23.0 23.20 32.0 32.24 39.0 39.29 42.0 42.14 55.0 55.19 58.0 58.24 65.0 65.27 73.0 73.22 79.0 79.13 84.0 84.13 89.0 89.14 99.0 99.11 102.0 102.17 105.0 105.19 108.0 108.13 115.0 115.16 118.0 118.15 123.0 123.15 126.0 126.13 129.0 129.12 132.0 132.16 145.0 145.33 148.0 148.11 153.0 153.11 156.0 156.14 159.0 159.18 162.0 162.30 180.0 180.25 183.0 183.17 187.0 187.23 190.0 190.23 193.0 193.19 196.0 196.18 199.0 199.19 202.0 202.25 205.0 205.18 208.0 208.22 211.0 211.27 214.0 214.22 217.0 217.35 220.0 220.13 223.0 223.21 226.0 226.20 235.0 235.17 235.24 235.32 241.0 241.17 241.25 241.33 $prefix tag configure omedium140 -font {-*-helvetica-medium-o-*-*-*-140-*-*-*-*-*-*} $prefix tag add omedium140 8.80 8.92 14.254 14.261 18.218 18.229 24.99 24.105 24.113 24.117 30.35 30.41 30.204 30.210 33.129 33.134 33.196 33.205 61.45 61.49 70.35 70.40 80.30 80.34 106.80 106.91 188.414 188.423 191.437 191.439 191.442 191.443 191.447 191.448 200.56 200.63 200.108 200.114 237.82 237.85 237.125 237.128 238.157 238.163 243.83 243.86 243.127 243.130 $prefix tag configure rbold140 -font {-*-helvetica-bold-r-*-*-*-140-*-*-*-*-*-*} $prefix tag add rbold140 5.71 6.11 6.85 7.10 7.77 8.22 8.158 9.14 9.199 10.19 11.0 11.4 66.170 67.4 67.82 68.5 68.80 69.6 69.126 70.13 90.186 91.13 91.157 92.12 92.109 93.23 133.108 134.36 134.161 135.18 135.137 136.22 136.78 137.10 137.207 138.16 138.153 139.11 139.56 140.19 140.417 141.22 141.160 142.15 168.126 168.133 188.748 188.771 200.416 200.418 200.572 200.574 200.621 200.623 200.673 200.677 200.700 200.702 230.62 231.7 231.50 232.8 237.37 237.46 237.93 237.102 238.42 238.51 238.58 238.73 238.124 238.133 238.202 238.224 242.6 242.13 242.63 242.71 243.37 243.47 243.94 243.104 244.67 244.85 244.96 244.106 $prefix tag configure rmedium140 -font {-*-helvetica-medium-r-*-*-*-140-*-*-*-*-*-*} $prefix tag add rmedium140 1.29 2.257 4.22 5.71 6.11 6.85 7.10 7.77 8.22 8.80 8.92 8.158 9.14 9.199 10.19 11.0 11.4 11.48 13.16 14.254 14.261 18.218 18.229 18.313 20.37 21.298 23.20 24.99 24.105 24.113 24.117 30.35 30.41 30.204 30.210 30.230 32.24 33.129 33.134 33.196 33.205 37.207 39.29 40.160 42.14 53.0 55.19 56.311 58.24 61.45 61.49 63.0 65.27 66.170 67.4 67.82 68.5 68.80 69.6 69.126 70.13 70.35 70.40 71.0 73.22 77.248 79.13 80.30 80.34 82.298 84.13 87.80 89.14 90.186 91.13 91.157 92.12 92.109 93.23 94.0 96.9 97.248 99.11 100.0 102.17 103.335 105.19 106.80 106.91 106.309 108.13 113.146 115.16 116.59 118.15 121.146 123.15 124.66 126.13 127.106 129.12 130.0 132.16 133.108 134.36 134.161 135.18 135.137 136.22 136.78 137.10 137.207 138.16 138.153 139.11 139.56 140.19 140.417 141.22 141.160 142.15 143.0 145.33 146.86 148.11 151.174 153.11 154.0 156.14 157.105 159.18 160.35 162.30 163.142 165.21 168.126 168.133 168.198 170.19 171.0 173.15 175.131 177.23 178.323 180.25 181.142 183.17 185.0 187.23 188.414 188.423 188.748 188.771 188.774 190.23 191.437 191.439 191.442 191.443 191.447 191.448 191.466 193.19 194.158 196.18 197.462 199.19 200.56 200.63 200.108 200.114 200.416 200.418 200.572 200.574 200.621 200.623 200.673 200.677 200.700 200.702 200.821 202.25 203.304 205.18 206.280 208.22 209.129 211.27 212.326 214.22 215.86 217.35 218.121 220.13 221.267 223.21 224.194 226.20 227.180 229.26 230.62 231.7 231.50 232.8 233.0 235.32 237.37 237.46 237.82 237.85 237.93 237.102 237.125 237.128 238.42 238.51 238.58 238.73 238.124 238.133 238.157 238.163 238.202 238.224 239.0 241.33 242.6 242.13 242.63 242.71 243.37 243.47 243.83 243.86 243.94 243.104 243.127 243.130 244.67 244.85 244.96 244.106 249.9 $prefix tag configure indent1 -lmargin1 {0} $prefix tag configure indent1 -lmargin2 {25} $prefix tag add indent1 5.71 10.95 66.170 70.102 90.186 93.100 133.108 142.161 230.62 232.86 236.21 238.225 242.143 244.285 $prefix tag configure indent2 -lmargin1 {25} $prefix tag configure indent2 -lmargin2 {50} $prefix tag add indent2 136.78 139.55 $prefix tag add tag0 2.236 2.254 $prefix tag configure tag0 -underline 1 $prefix tag bind tag0 <1> "help`gotoTag configpage" $prefix tag add tag1 16.154 16.163 $prefix tag configure tag1 -underline 1 $prefix tag bind tag1 <1> "help`gotoTag loadpage" $prefix tag add tag2 16.366 16.385 $prefix tag configure tag2 -underline 1 $prefix tag bind tag2 <1> "help`gotoTag configpage" $prefix tag add tag3 16.505 16.513 $prefix tag configure tag3 -underline 1 $prefix tag bind tag3 <1> "help`gotoTag menu_generate" $prefix tag add tag4 18.251 18.269 $prefix tag configure tag4 -underline 1 $prefix tag bind tag4 <1> "help`gotoTag configpage" $prefix tag add tag5 28.39 28.58 $prefix tag configure tag5 -underline 1 $prefix tag bind tag5 <1> "help`gotoTag configpage" $prefix tag add tag6 28.135 28.142 $prefix tag configure tag6 -underline 1 $prefix tag bind tag6 <1> "help`gotoTag load_detail" $prefix tag add tag7 33.41 33.60 $prefix tag configure tag7 -underline 1 $prefix tag bind tag7 <1> "help`gotoTag configpage" $prefix tag add tag8 33.91 33.103 $prefix tag configure tag8 -underline 1 $prefix tag bind tag8 <1> "help`gotoTag menu_export" $prefix tag add tag9 35.29 35.39 $prefix tag configure tag9 -underline 1 $prefix tag bind tag9 <1> "help`gotoTag extentry" $prefix tag add tag10 40.143 40.157 $prefix tag configure tag10 -underline 1 $prefix tag bind tag10 <1> "help`gotoTag window" $prefix tag add tag11 45.73 45.87 $prefix tag configure tag11 -underline 1 $prefix tag bind tag11 <1> "help`gotoTag menu_setup" $prefix tag add tag12 49.196 49.211 $prefix tag configure tag12 -underline 1 $prefix tag bind tag12 <1> "help`gotoTag manuals" $prefix tag add tag13 85.115 85.125 $prefix tag configure tag13 -underline 1 $prefix tag bind tag13 <1> "help`gotoTag extentry" $prefix tag add tag14 103.258 103.268 $prefix tag configure tag14 -underline 1 $prefix tag bind tag14 <1> "help`gotoTag menu_setup" $prefix tag add tag15 103.317 103.334 $prefix tag configure tag15 -underline 1 $prefix tag bind tag15 <1> "help`gotoTag howToUse" $prefix tag add tag16 111.41 111.50 $prefix tag configure tag16 -underline 1 $prefix tag bind tag16 <1> "help`gotoTag loadpage" $prefix tag add tag17 113.130 113.143 $prefix tag configure tag17 -underline 1 $prefix tag bind tag17 <1> "help`gotoTag menu_export" $prefix tag add tag18 116.10 116.14 $prefix tag configure tag18 -underline 1 $prefix tag bind tag18 <1> "help`gotoTag menu_save" $prefix tag add tag19 124.18 124.24 $prefix tag configure tag19 -underline 1 $prefix tag bind tag19 <1> "help`gotoTag loadpage" $prefix tag add tag20 124.44 124.63 $prefix tag configure tag20 -underline 1 $prefix tag bind tag20 <1> "help`gotoTag configpage" $prefix tag add tag21 138.132 138.150 $prefix tag configure tag21 -underline 1 $prefix tag bind tag21 <1> "help`gotoTag configpage" $prefix tag add tag22 141.76 141.80 $prefix tag configure tag22 -underline 1 $prefix tag bind tag22 <1> "help`gotoTag menu_save" $prefix tag add tag23 163.10 163.14 $prefix tag configure tag23 -underline 1 $prefix tag bind tag23 <1> "help`gotoTag howToUse" $prefix tag add tag24 175.90 175.97 $prefix tag configure tag24 -underline 1 $prefix tag bind tag24 <1> "help`gotoTag Bash_version" $prefix tag add tag25 11.44 11.47 $prefix tag configure tag25 -underline 1 $prefix tag bind tag25 <1> "startBrowser http://www.imada.sdu.dk/~blackie/dotfile/help.html" $prefix tag add tag26 166.28 166.37 $prefix tag configure tag26 -underline 1 $prefix tag bind tag26 <1> "startBrowser http://www.imada.sdu.dk/~blackie/dotfile" $prefix tag add tag27 166.75 166.105 $prefix tag configure tag27 -underline 1 $prefix tag bind tag27 <1> "startBrowser http://www.imada.sdu.dk/~blackie/dotfile/dotdotfiles/" $prefix tag add tag28 188.748 188.772 $prefix tag configure tag28 -underline 1 $prefix tag bind tag28 <1> "startBrowser http://www.ora.com/catalog/bash/" $prefix tag add tag29 203.274 203.301 $prefix tag configure tag29 -underline 1 $prefix tag bind tag29 <1> "startBrowser http://www.imada.sdu.dk/~pzacho/bash/bashguide.html#Commandline/2" }