PageRenderTime 131ms CodeModel.GetById 91ms app.highlight 9ms RepoModel.GetById 21ms app.codeStats 0ms


XML | 558 lines | 555 code | 1 blank | 2 comment | 0 complexity | 1632f78bb99911d3dc15360ad3008cd8 MD5 | raw file
  1<!-- jEdit buffer-local properties: -->
  2<!-- :tabSize=1:indentSize=1:noTabs=true: -->
  4<chapter id="files"><title>Working With Files</title>
  5 <sect1 id="creating"><title>Creating New Files</title>
  6  <para>
  7   <guimenu>File</guimenu>&gt;<guimenuitem>New</guimenuitem> (shortcut:
  8   <keycombo><keycap>Control</keycap><keycap>N</keycap></keycombo>) opens a new
  9   untitled buffer. When it is saved, a file will be created on disk.
 10   Another way to create a new file is to specify a non-existent file
 11   name when starting jEdit from your operating system's command line.
 12  </para>
 13 </sect1>
 14 <sect1 id="opening"><title>Opening Files</title>
 15  <para>
 16   <guimenu>File</guimenu>&gt;<guimenuitem>Open</guimenuitem> (shortcut:
 17   <keycombo><keycap>Control</keycap><keycap>O</keycap></keycombo>) displays
 18   a file selector dialog box and loads the specified file into a new
 19   buffer. Multiple files can be opened at once by holding down
 20   <keycap>Control</keycap> while clicking on them in the file system browser.
 21  </para>
 22  <para>
 23   <guimenu>File</guimenu>&gt;<guimenuitem>Insert</guimenuitem> displays
 24   a file selector dialog box and inserts the specified file into the current
 25   buffer.
 26  </para>
 27  <para>
 28   The <guimenu>File</guimenu>&gt;<guimenuitem>Current Directory</guimenuitem>
 29   menu lists all files in the current buffer's directory.
 30  </para>
 31  <para>
 32   The <guimenu>File</guimenu>&gt;<guimenuitem>Recent Files</guimenuitem> menu
 33   lists recent files. When a recent file is opened, the caret
 34   is automatically moved to its previous location in that file.
 35   The number of recent files to remember can be changed and caret
 36   position saving can be disabled in the <guibutton>General</guibutton> pane of
 37   the <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
 38   dialog box; see <xref linkend="global-opts" />.
 39  </para>
 40  <para>
 41   Files that you do not have write access to are opened in read-only
 42   mode, and editing will not be permitted.
 43  </para>
 44  <tip>
 45   <para>
 46    jEdit supports transparent editing of GZipped files; files with
 47    the <filename>.gz</filename> extension are automatically decompressed before
 48    loading, and compressed when saving.
 49   </para>
 50  </tip>
 51 </sect1>
 52 <sect1 id="saving"><title>Saving Files</title>
 53  <para>
 54   Changed made to a buffer do not affect the file on disk until the
 55   buffer is <firstterm>saved</firstterm>.
 56  </para>
 57  <para>
 58   <guimenu>File</guimenu>&gt;<guimenuitem>Save</guimenuitem> (shortcut:
 59   <keycombo><keycap>Control</keycap><keycap>S</keycap></keycombo>)
 60   saves the current buffer to disk.
 61  </para>
 62  <para>
 63   <guimenu>File</guimenu>&gt;<guimenuitem>Save All</guimenuitem>
 64   (shortcut: <keycombo><keycap>Control</keycap><keycap>E</keycap></keycombo>
 65   <keycombo><keycap>Control</keycap><keycap>S</keycap></keycombo>) saves all
 66   open buffers to disk, asking for confirmation first.
 67  </para>
 68  <para>
 69   <guimenu>File</guimenu>&gt;<guimenuitem>Save As</guimenuitem> saves the
 70   buffer to a different specified file on disk. The buffer is then
 71   renamed, and subsequent saves also save to the specified file.
 72  </para>
 73  <para>
 74   <guimenu>File</guimenu>&gt;<guimenuitem>Save a Copy As</guimenuitem> saves
 75   the buffer to a different specified file on disk, but doesn't rename the
 76   buffer, and doesn't clear the <quote>modified</quote> flag.
 77  </para>
 78  <sidebar><title>How files are saved</title>
 79   <para>
 80    To prevent data loss in the unlikely case that jEdit should crash in the
 81    middle of saving a file, files are first saved to
 82    <filename>#<replaceable>filename</replaceable>#save#</filename>. If this
 83    operation is successful, the original file is replaced with the temporary
 84    file.
 85   </para>
 86   <para>
 87    However, in some situations, this behavior is undesirable. For example,
 88    on Unix saving files this way will result in the owner and group of the
 89    file being reset. If this bothers you, you can disable this so-called
 90    <quote>two-stage save</quote> in the <guibutton>Loading and Saving</guibutton>
 91    pane of the
 92    <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
 93    dialog box.
 94   </para>
 95  </sidebar>
 96  <sect2><title>Autosave and Crash Recovery</title>
 97   <para>
 98    The autosave feature protects your work from computer crashes and
 99    such. Every 30 seconds, all buffers with unsaved changes are
100    written out to their respective file names, enclosed in hash
101    (<quote>#</quote>) characters. For example, <filename>program.c</filename>
102    will be autosaved to <filename>#program.c#</filename>.
103   </para>
104   <para>
105    Saving a buffer using
106    one of the commands in the previous section automatically deletes the
107    autosave file, so they will only ever be visible in the unlikely
108    event of a jEdit (or operating system) crash.
109   </para>
110   <para>
111    If an autosave file is
112    found while a buffer is being loaded, jEdit will offer to recover the
113    autosaved data.
114   </para>
115   <para>
116    The autosave feature can be configured
117    in the <guibutton>Loading and Saving</guibutton> pane of the
118    <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
119    dialog box; see <xref linkend="global-opts" />.
120   </para>
121  </sect2>
122  <sect2><title>Backups</title>
123   <para>
124    The backup feature can be used to roll back to the previous version
125    of a file after changes were made. When a buffer is saved
126    for the first time after being opened, its original contents are
127    <quote>backed up</quote> under a different file name.
128   </para>
129   <para>
130    The default behavior is to back up the original contents
131    to the buffer's file name suffixed with a tilde (<quote>~</quote>).
132    For example, <filename>paper.tex</filename> will be backed up to
133    <filename>paper.tex~</filename>.
134   </para>
135   <para>
136    The backup feature can also be configured to do any of the following:
137   </para>
138   <itemizedlist>
139    <listitem><para>
140     Save numbered backups, named
141     <filename><replaceable>filename</replaceable>~<replaceable>number</replaceable>~</filename>
142    </para></listitem>
143    <listitem><para>
144     Add a prefix to the backed-up file name
145    </para></listitem>
146    <listitem><para>
147     Adds a suffix, other than <quote>~</quote>, to the backed-up file name
148    </para></listitem>
149    <listitem><para>
150     Backups can optionally be saved in a specified backup directory, instead of
151     the directory of the original file. This can reduce clutter
152    </para></listitem>
153    <listitem><para>
154     Backups can also optionally be created every time a buffer is saved;
155     as mentioned above, the default is to only create a backup the first
156     time a buffer is saved after being opened.
157    </para></listitem>
158   </itemizedlist>
159   <para>
160    The above features can be configured
161    in the <guibutton>Loading and Saving</guibutton> pane of the
162    <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
163    dialog box; see <xref linkend="global-opts" />.
164   </para>
165  </sect2>
166 </sect1>
167 <sect1 id="line-separators"><title>Line Separators</title>
168  <para>
169   The three major operating systems use different conventions to mark
170   line endings in text files.
171   The MacOS uses Carriage-Return characters (<literal>\r</literal> in
172   Java-speak) for that purpose. Unix
173   uses Newline characters (<literal>\n</literal>). Windows uses both
174   (<literal>\r\n</literal>). jEdit can read and write files in all three formats.
175  </para>
176  <para>
177   When loading a file, the line separator used within is automatically
178   detected, and will be used when saving a file back to disk. The line
179   separator used when saving the current buffer can be changed in the
180   <guimenu>Utilities</guimenu>&gt;<guimenuitem>Buffer
181   Options</guimenuitem> dialog box; see <xref linkend="buffer-opts" />.
182  </para>
183  <para>
184   By default, new files are saved with your operating system's native line
185   separator. This can be changed in the
186   <guibutton>Loading and Saving</guibutton> pane of the
187   <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
188   dialog box; see <xref linkend="global-opts" />. Note that changing this
189   setting has no effect on existing files.
190  </para>
191 </sect1>
192 <sect1 id="encodings"><title>Character Encodings</title>
193  <para>
194   Internally, Java programs like jEdit store text as a stream of
195   16-bit numerical values, with each value a character in the Unicode character
196   set. Unicode is a
197   standardized character set that can represent characters in almost all human
198   languages.
199  </para>
200  <para>
201   Unfortunately, most other computer programs use far less flexible methods of
202   storing
203   text; therefore, if jEdit loaded and saved all files as raw Unicode, it would
204   be useless.
205  </para>
206  <para>
207   To get around this, jEdit converts Unicode text to other character
208   encodings and vice versa when loading and saving files. jEdit can use any
209   encoding supported by the Java platform.
210  </para>
211  <para>
212   The default encoding, used to load and save files for which no
213   other encoding is specified, can be set in the <guibutton>Loading and
214   Saving</guibutton> pane of the
215   <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
216   dialog box; see <xref linkend="global-opts" />. The setting is presented as
217   an editable combo box; the combo box
218   contains a few of the more frequently used encodings, but the Java platform
219   defines practically hundreds more you can use.
220  </para>
221  <para>
222   Unfortunately, there
223   is no programmical way to obtain a list of all supported encodings, and the
224   set is constantly changing with each Java version. So to play it safe, jEdit
225   has a few pre-defined defaults, but allows you to use any other supported
226   encoding, assuming you know its name.
227  </para>
228  <para>
229   Unless you change the default encoding, jEdit will use your operating
230   system's native encoding; <literal>MacRoman</literal> on the MacOS,
231   <literal>Cp1252</literal> on Windows, and <literal>8859_1</literal> on
232   Unix.
233  </para>
234  <para>
235   The <guimenu>File</guimenu>&gt;<guisubmenu>Open With Encoding</guisubmenu>
236   lets you open a file with an encoding other than the default. The menu
237   contains a set of items, one for each common encoding, along with
238   <guimenuitem>System Default</guimenuitem> and <guimenuitem>jEdit
239   Default</guimenuitem> commands. Invoking a menu item displays the usual
240   file dialog box, and opens the selected file with the chosen encoding.
241  </para>
242  <para>
243   The <guimenu>Open With Other Encoding</guimenu> command in the same menu
244   lets you enter an arbitriary encoding name, assuming it is supported by
245   your Java implementation.
246  </para>
247  <para>
248   Once a file has been opened, the encoding to use when saving it
249   can be set in the <guimenu>Utilities</guimenu>&gt;<guimenuitem>Buffer
250   Options</guimenuitem> dialog box.
251  </para>
252  <para>
253   The current buffer's encoding is shown in the status bar. If a file is opened
254   without an explicit encoding specified, jEdit will use the encoding last used
255   when working with that file, if the file is in the recent file list.
256   Otherwise, the default encoding will be used.
257  </para>
258  <sect2><title>Commonly Used Encodings</title>
259   <para>
260    The most frequently-used character encoding is ASCII, or <quote>American 
261    Standard Code for Information Interchange</quote>. ASCII encodes Latin
262    letters used in English, in addition to numbers and a range of punctuation
263    characters.
264    The ASCII character set consists of 127 characters only, and it is unsuitable
265    for anything but English text (and other file types which only use English
266    characters, like most program source). jEdit will load and save files as
267    7-bit ASCII if the <literal>ASCII</literal> encoding is used.
268   </para>
269   <para>
270    Because ASCII is unsuitable for international use, most operating
271    systems use an 8-bit extension of ASCII, with the first 127 characters
272    remaining the same, and the rest used to encode accents, ulmauts, and
273    various less frequently used typographical marks. Unfortunately, the three
274    major
275    operating systems all extend ASCII in a different way. Files written by
276    Macintosh programs can be read using the <literal>MacRoman</literal>
277    encoding; Windows text files are usually stored as
278    <literal>Cp1252</literal>. In the Unix world, the <literal>8859_1</literal>
279    (otherwise known as Latin1) character encoding has found widespread usage.
280   </para>
281   <para>
282    Windows users are accustomized to dealing with files in a wide range of
283    character sets, known as <firstterm>code pages</firstterm>. Java supports a
284    large number of code pages; the encoding name consists of the text
285    <quote>Cp</quote>, followed by a number.
286   </para>
287   <para>
288    Raw Unicode files are quite rare, but can be read and written with the
289    <literal>Unicode</literal> encoding.
290    One reason raw Unicode has not found widespread usage for storing files on
291    disk is that each character takes up 16 bits. Most other character sets
292    devote 8 bits per character, which saves space. The <literal>UTF8</literal>
293    encoding encodes frequently-used Unicode characters as 8 bits, with
294    less-frequent ones stretching up to 24 bits. This saves space but allows the
295    full range of Unicode characters to be represented.
296   </para>
297   <para>
298    Many common cross-platform international character sets are supported;
299    <literal>KOI8_R</literal> for Russian text, <literal>Big5</literal> and
300    <literal>GBK</literal> for Chinese, and <literal>SJIS</literal> for
301    Japanese.
302   </para>
303   <para>
304    Java even supports a few downright obscure encodings, such as the
305    <literal>EBCDIC</literal> character encoding used on IBM mainframes.
306   </para>
307  </sect2>
308 </sect1>
309 <sect1 id="vfs-browser"><title>The File System Browser</title>
310  <para>
311   <guimenu>Utilities</guimenu>&gt;<guimenuitem>File System
312   Browser</guimenuitem> displays a file system browser.
313   By default, the file system browser is shown in a floating window;
314   it can be set to dock into the view in the <guibutton>Docking</guibutton>
315   pane of the <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global
316   Options</guimenuitem> dialog box; see <xref linkend="docking" />.
317  </para>
318  <para>
319   The file system browser can be customized in the
320   <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
321   dialog box.
322  </para>
323  <sect2><title>Navigating the File System</title>
324   <para>
325    The directory to browse is specified in the <guibutton>Path</guibutton> text
326    field. Clicking the mouse in the text field automatically selects its
327    contents allowing a new path to be quickly typed in. If a relative path is
328    entered, it will be resolved relative to the current path. This text field
329    remembers previously entered strings; see <xref linkend="history" />.
330    Previously browsed directories are also listed in the
331    <guimenu>File</guimenu>&gt;<guisubmenu>Recent Directories</guisubmenu>
332    menu; selecting one opens it in the file system browser.
333   </para>
334   <para>
335    To browse higher up in the directory hierarchy, click one of the parent
336    directories in the parent directory list.
337   </para>
338   <para>
339    Files and directories in the file list are shown in different colors
340    depending on what glob patterns their names match. The patterns and colors
341    can be customized in the
342    <guibutton>File System Browser</guibutton>&gt;<guibutton>Colors</guibutton>
343    pane of the
344    <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
345    dialog box.
346   </para>
347   <para>
348    To browse a listed directory, double-click it (or if you have a three-button
349    mouse, click the middle mouse button). Alternatively, click the disclosure
350    widget next to a directory to list its contents in place.
351   </para>
352   <para>
353    Open files in the file list have a vertical black bar next to their icon.
354    Single-clicking an open file will select the appropriate buffer in the current
355    view. Unopened files can be opened for editing by double-clicking (or by
356    clicking the middle mouse button).
357   </para>
358   <para>
359    Clicking a file or directory with the right mouse button displays a popup
360    menu containing file manipulation commands. Note that attempting to delete
361    a directory containing files will give an error;
362    only empty directories can be deleted.
363   </para>
364   <para>
365    If you only want to see a specific set of files (for example,
366    those whose names end with <filename>.java</filename>), enter a glob pattern
367    in the <guibutton>Filter</guibutton> text field.
368    See <xref linkend="globs" /> for information about glob patterns.
369    This text fields remembers previously entered strings;
370    see <xref linkend="history" />.
371   </para>
372   <tip>
373    <para>
374     The file list sorting algorithm used in jEdit handles numbers in file names
375     in an intelligent manner. For example, a file named
376     <filename>section10.xml</filename> will be placed after a file named
377     <filename>section5.xml</filename>. A conventional letter-by-letter
378     sort would have placed these two files in the wrong order.
379    </para>
380   </tip>
381  </sect2>
382  <sect2><title>The Commands Menu</title>
383   <para>
384    Clicking the <guibutton>Commands</guibutton> button displays a menu
385    containing the following items:
386   </para>
387   <itemizedlist>
388    <listitem><para><guimenuitem>Parent Directory</guimenuitem> - displays the
389    directory containing the one currently being viewed.</para></listitem>
390    <listitem><para><guimenuitem>Reload Directory</guimenuitem> - reloads the
391    file list from disk.</para></listitem>
392    <listitem><para><guimenuitem>Local Drives</guimenuitem> - displays all
393    local drives. On Windows, this will be a list of
394    drive letters; on Unix, the list will only contain one entry, the
395    root directory.</para></listitem>
396    <listitem><para><guimenuitem>Home Directory</guimenuitem> - displays your
397    home directory.</para></listitem>
398    <listitem><para><guimenuitem>Directory of Current Buffer - displays the
399    directory containing the currently active buffer.</guimenuitem></para></listitem>
400    <listitem><para><guimenuitem>New File</guimenuitem> - opens an
401    <filename>Untitled</filename> file in the current directory. The file will
402    not actually be created on disk until it is saved.</para></listitem>
403    <listitem><para><guimenuitem>New Directory</guimenuitem> - creates a new
404    directory after prompting for the desired name.</para></listitem>
405    <listitem><para><guimenuitem>Search in Directory</guimenuitem> -
406    displays the
407    search and
408    replace dialog box for searching in all files in the current directory. If a
409    file is selected, its extension becomes the file name filter for the search;
410    otherwise, the file name filter entered in the browser is used.
411    See <xref linkend="search-replace" /> for details.</para></listitem>
412    <listitem><para><guimenuitem>Show Hidden Files</guimenuitem> - toggles if
413    hidden files are to be shown in the file list.</para></listitem>
414   </itemizedlist>
415  </sect2>
416  <sect2><title>The Plugins Menu</title>
417   <para>
418    Clicking the <guibutton>Plugins</guibutton> button displays a menu
419    containing commands for browsing plugin file systems. For information
420    about plugins, see <xref linkend="using-plugins" />.
421   </para>
422  </sect2>
423  <sect2><title>The Favorites Menu</title>
424   <para>
425    Clicking the <guibutton>Favorites</guibutton> button displays a menu
426    showing all directories in the favorites list, along with an
427    <guimenuitem>Add to Favorites</guimenuitem> command that adds the current
428    directory to the favorites, and an <guimenuitem>Edit Favorites</guimenuitem>
429    command that shows the favorites list in the file system view, allowing items
430    to be removed by right-clicking on them and selecting
431    <guimenuitem>Delete</guimenuitem> from the resulting popup menu.
432   </para>
433  </sect2>
434  <sect2><title>Keyboard Shortcuts</title>
435   <para>
436    The file system browser can be navigated from the keyboard:
437   </para>
438   <itemizedlist>
439    <listitem><para><keycap>Enter</keycap> - opens the currently selected file or
440    directory.</para></listitem>
441    <listitem><para><keycap>Left</keycap> - goes to the current directory's parent.
442    </para></listitem>
443    <listitem><para><keycap>Up</keycap> - selects previous file in list.
444    </para></listitem>
445    <listitem><para><keycap>Down</keycap> - selects next file in list.
446    </para></listitem>
447    <listitem><para><keycap>/</keycap> - displays all
448    local drives.</para></listitem>
449    <listitem><para><keycap>~</keycap> - displays your home directory.
450    </para></listitem>
451    <listitem><para><keycap>-</keycap> - displays the directory containing
452    the current buffer.</para></listitem>
453    <listitem><para>Typing the first few characters of
454    a file's name will select that file.
455    </para></listitem>
456   </itemizedlist>
457   <para>
458    The file system view, and not the <guibutton>Path</guibutton> or
459    <guibutton>Filter</guibutton> text fields must have keyboard focus for these
460    shortcuts to work.
461   </para>
462  </sect2>
463 </sect1>
464 <sect1 id="reloading"><title>Reloading Files</title>
465  <para>
466   If an open buffer is modified on disk by another application, a warning
467   dialog box is displayed, offering to either continue editing
468   (and lose changes made by the other application)
469   or reload the buffer from disk (and lose any usaved changes). This
470   feature can be disabled in the <guibutton>General</guibutton> pane of the
471   <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
472   dialog box; see <xref linkend="global-opts" />.
473  </para>
474  <para>
475   <guimenu>File</guimenu>&gt;<guimenuitem>Reload</guimenuitem> can be used to
476   discard unsaved changes and reload the current buffer from disk at any other
477   time; a confirmation dialog box will be displayed first if the buffer
478   has unsaved changes.
479  </para>
480  <para>
481   <guimenu>File</guimenu>&gt;<guimenuitem>Reload All</guimenuitem>
482   discards unsaved changes in all open buffers and reload them from disk,
483   asking for confirmation first.
484  </para>
485 </sect1>
486 <sect1 id="threaded-io"><title>Multi-Threaded I/O</title>
487  <para>
488   To improve responsiveness and perceived performance,
489   jEdit executes all input/output operations asynchronously.
490   While I/O is in progress, the status bar displays the number of
491   remaining I/O operations. When I/O is complete, the status bar shows a message
492   to this effect.
493   The <guimenu>Utilities</guimenu>&gt;<guimenuitem>I/O Progress
494   Monitor</guimenuitem> command displays a window with more detailed status
495   information and progress meters. Requests can also be aborted in this window.
496   Note that aborting a buffer save can result in data loss.
497  </para>
498  <para>
499   By default, four I/O threads are created, which means that up
500   to four buffers can be loaded or saved simultaneously. The number of
501   threads can be changed in the
502   <guibutton>Loading and Saving</guibutton> pane of the
503   <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global Options</guimenuitem>
504   dialog box; see <xref linkend="global-opts" />. Setting the number to zero
505   disables multi-threaded I/O completely; doing this is not recommended.
506  </para>
507 </sect1>
508 <sect1 id="printing"><title>Printing Files</title>
509  <para>
510   <guimenu>File</guimenu>&gt;<guimenuitem>Print</guimenuitem>
511   (shortcut: <keycombo><keycap>Control</keycap><keycap>P</keycap></keycombo>)
512   will print the current buffer. By default, the printed output will have
513   syntax highlighting, and each page will have a header with the file name,
514   and a footer with the current date/time and page number. The appearance of
515   printed output
516   can be customized in the <guibutton>Printing</guibutton> pane of the
517   <guimenu>Utilities</guimenu>&gt;<guimenuitem>Global
518   Options</guimenuitem> dialog box. The following settings can be changed:
519  </para>
520  <itemizedlist>
521   <listitem><para>The font to use when printing</para></listitem>
522   <listitem><para>If a header with the file name should be printed on each
523   page</para></listitem>
524   <listitem><para>If a footer with the page number and current date should be
525   printed on each page</para></listitem>
526   <listitem><para>If line numbers should be printed</para></listitem>
527   <listitem><para>If the output should be styled according to the current
528   mode's syntax highlighting rules</para></listitem>
529   <listitem><para>If the output should be colored according to the current
530   mode's syntax highlighting rules (might look bad on grayscale
531   printers)</para></listitem>
532   <listitem><para>The page margins</para></listitem>
533  </itemizedlist>
534 </sect1>
535 <sect1 id="closing-exiting"><title>Closing Files and Exiting jEdit</title>
536  <para>
537   <guimenu>File</guimenu>&gt;<guimenuitem>Close</guimenuitem>
538   (shortcut: <keycombo><keycap>Control</keycap><keycap>W</keycap></keycombo>)
539   closes the current buffer. If it has unsaved changes, jEdit
540   will ask if they should be saved first.
541  </para>
542  <para>
543   <guimenu>File</guimenu>&gt;<guimenuitem>Close All</guimenuitem>
544   (shortcut: <keycombo><keycap>Control</keycap><keycap>E</keycap></keycombo>
545   <keycombo><keycap>Control</keycap><keycap>W</keycap></keycombo>)
546   closes all buffers. If any buffers have unsaved
547   changes, they will be listed in a dialog box where they can be saved
548   or discarded. In the dialog box, multiple buffers to operate on at
549   once can be selected by clicking on them in the list while holding
550   down <keycap>Control</keycap>.
551  </para>
552  <para>
553   <guimenu>File</guimenu>&gt;<guimenuitem>Exit</guimenuitem>
554   (shortcut: <keycombo><keycap>Control</keycap><keycap>Q</keycap></keycombo>)
555   will completely exit jEdit.
556  </para>
557 </sect1>