PageRenderTime 149ms CodeModel.GetById 139ms app.highlight 3ms RepoModel.GetById 5ms app.codeStats 0ms


HTML | 36 lines | 36 code | 0 blank | 0 comment | 0 complexity | 6dcde5c2be265898549557ad036a2316 MD5 | raw file
 1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>How jEdit Organizes Macros</title><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="jEdit 4.3 User's Guide"><link rel="up" href="using-macros.html" title="Chapter 8. Using Macros"><link rel="prev" href="running-macros.html" title="Running Macros"><link rel="next" href="using-plugins.html" title="Chapter 9. Installing and Using Plugins"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">How jEdit Organizes Macros</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="running-macros.html">Prev</a> </td><th width="60%" align="center">Chapter 8. Using Macros</th><td width="20%" align="right"> <a accesskey="n" href="using-plugins.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="organizing-macros"></a>How jEdit Organizes Macros</h2></div></div></div><p>Every macro, whether or not you originally recorded it, is stored
 2        on disk and can be edited as a text file. The file name of a macro must
 3        have a <code class="filename">.bsh</code> extension in order for jEdit to be
 4        aware of it. By default, jEdit associates a <code class="filename">.bsh</code>
 5        file with the BeanShell edit mode for purposes of syntax highlighting,
 6        indentation and other formatting. However, BeanShell syntax does not
 7        impose any indentation or line break requirements.</p><p>The <span class="guimenu"><strong>Macros</strong></span> menu lists all macros stored in two
 8        places: the <code class="filename">macros</code> subdirectory of the jEdit home
 9        directory, and the <code class="filename">macros</code> subdirectory of the
10        user-specific settings directory (see <a class="xref" href="settings-directory.html" title="The jEdit Settings Directory">the section called &#8220;The jEdit Settings Directory&#8221;</a> for information about the settings
11        directory). Any macros you record will be stored in the user-specific
12        directory.</p><p>Macros stored elsewhere can be run using the
13        <span class="guimenu"><strong>Macros</strong></span>&gt;<span class="guimenuitem"><strong>Run Other Macro</strong></span>
14        command, which displays a file chooser dialog box, and runs the
15        specified file.</p><p>The listing of individual macros in the <span class="guimenu"><strong>Macros</strong></span>
16        menu can be organized in a hierarchy using subdirectories in the general
17        or user-specific macro directories; each subdirectory appears as a
18        submenu. You will find such a hierarchy in the default macro set
19        included with jEdit.</p><p>When jEdit first loads, it scans the designated macro directories
20        and assembles a listing of individual macros in the
21        <span class="guimenu"><strong>Macros</strong></span> menu. When scanning the names, jEdit will
22        delete underscore characters and the <code class="filename">.bsh</code> extension
23        for menu labels, so that
24        <code class="filename">List_Useful_Information.bsh</code>, for example, will be
25        displayed in the <span class="guimenu"><strong>Macros</strong></span> menu as <span class="guimenuitem"><strong>List
26        Useful Information</strong></span>.</p><p>You can browse the user and system macro directories by opening
27        the <code class="filename">macros</code> directory from the
28        <span class="guimenu"><strong>Utilities</strong></span>&gt;<span class="guimenuitem"><strong>jEdit Home
29        Directory</strong></span> and
30        <span class="guimenu"><strong>Utilities</strong></span>&gt;<span class="guimenuitem"><strong>Settings
31        Directory</strong></span> menus.</p><p>Macros can be opened and edited much like ordinary files from the
32        file system browser. Editing macros from within jEdit will automatically
33        update the macros menu; however, if you modify macros from another
34        program or add macro files to the macro directories, you should run the
35        <span class="guimenu"><strong>Macros</strong></span>&gt;<span class="guimenuitem"><strong>Rescan Macros</strong></span>
36        command to update the macro list.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="running-macros.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="using-macros.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="using-plugins.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Running Macros </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 9. Installing and Using Plugins</td></tr></table></div></body></html>