PageRenderTime 56ms CodeModel.GetById 20ms RepoModel.GetById 0ms app.codeStats 1ms

/jEdit/tags/jedit-4-1-pre5/doc/FAQ/faq-items1.xml

#
XML | 686 lines | 654 code | 26 blank | 6 comment | 0 complexity | 5fd491bb0e24233b574319308d2c9a38 MD5 | raw file
Possible License(s): BSD-3-Clause, AGPL-1.0, Apache-2.0, LGPL-2.0, LGPL-3.0, GPL-2.0, CC-BY-SA-3.0, LGPL-2.1, GPL-3.0, MPL-2.0-no-copyleft-exception, IPL-1.0
  1. <!-- jEdit buffer-local properties: -->
  2. <!-- :indentSize=1:noTabs=true:maxLineLen=72:tab Size=2: -->
  3. <!-- jEdit FAQ -->
  4. <!-- Copyright (C) 2002 John Gellene -->
  5. <!-- $Id: faq-items1.xml 4040 2002-02-17 13:41:20Z jgellene $
  6. -->
  7. <sect1 id="faq-intro"><title>Introduction</title>
  8. <para>
  9. This document explains many of the basic features of jEdit and provides
  10. solutions for commonly encountered problems. It is not the principal
  11. resource for learning how to use and customize jEdit. The application
  12. includes an extensive User's Guide available from within jEdit by
  13. selecting <guimenuitem>jEdit Help</guimenuitem> on the
  14. <guimenu>Help</guimenu> menu.
  15. </para>
  16. <para>
  17. The User's Guide includes tutorials on writing macros and plugins as
  18. well as an annotated guide to jEdit's Application Programming Interface
  19. (API). It is worth browsing through the User's Guide to get a full sense
  20. of what jEdit has to offer. This document is intended to supplement the
  21. User's Guide by focusing on specific, relatively narrow topics in the
  22. traditional question-and-answer format.
  23. </para>
  24. <para>
  25. Each section of this document deals with a different category of topics,
  26. and each begins with a listing of the questions covered. This should
  27. allow you to find the information you are seeking quickly.
  28. </para>
  29. </sect1>
  30. <sect1 id="getting-jedit"><title>General Information and Availability</title>
  31. <para>
  32. This section deals with some background information and how to obtain the
  33. latest version of jEdit.
  34. </para>
  35. <qandaset defaultlabel="qanda">
  36. <qandadiv id="about">
  37. <title>About jEdit</title>
  38. <qandaentry>
  39. <question id="whatis"><para>
  40. What is jEdit?
  41. </para></question>
  42. <answer><para>
  43. jEdit is a programmer's text editor written in Java, being
  44. developed by Slava Pestov and others. It has an easy to use
  45. interface that resembles that of many other Windows and MacOS
  46. text editors. It is also highly customizable, and contains a
  47. <quote>plugin</quote> architecture that allows its features to
  48. be extended by additional programs.
  49. </para></answer>
  50. </qandaentry>
  51. <qandaentry>
  52. <question id="difftext"><para>
  53. What is the difference between a text editor and a word
  54. processor?
  55. </para></question>
  56. <answer><para>
  57. These categories are not absolute but refer to the primary
  58. purpose of an editing program and the focus of its features.
  59. </para>
  60. <para>
  61. A text editor is an application that edits files containing plain text
  62. without automatically formatting the text for printing or other publication.
  63. Typically the contents of such a file consists of data used by another
  64. application - for example, source code that a compiler will process or
  65. markup text that a web browser will display. A word processor deals with
  66. the preparation of documents for printing or similar publication.
  67. Besides editing text, a modern word processor allows the user to choose
  68. multiple fonts, margin sizes, line spacing, indentation, and a variety
  69. of other details that affect the appearance of the document being
  70. edited. In a text editor, these features are present, if at all, only in
  71. a basic form, and for the limited purpose of helping the user compose
  72. and organize the text. In place of word processing features, a text
  73. editor contains many features that allow the user to prepare and work with
  74. text quickly and efficiently.
  75. </para>
  76. <para>
  77. The jEdit application is a text editor, not a word processor. It
  78. contains a large assortment of features for manipulating source code,
  79. markup text, and other text files. As a programmer's text editor, it
  80. also has many features to help programmers manage their projects and
  81. work with other programming tools.
  82. </para></answer>
  83. </qandaentry>
  84. <qandaentry>
  85. <question id="features"><para>
  86. What features does jEdit have?
  87. </para></question>
  88. <answer><para>
  89. The short answer is, too many to list here. There is a detailed
  90. list available on the <ulink
  91. url="http://www.jedit.org/index.php?page=features">jEdit web
  92. site</ulink>, but here are some of the major features:
  93. </para>
  94. <itemizedlist>
  95. <listitem><para>
  96. Comprehensive online help
  97. </para></listitem>
  98. <listitem><para>
  99. Multiple editor windows and split editing panes within a single
  100. editing window
  101. </para></listitem>
  102. <listitem><para>
  103. Unlimited undo/redo
  104. </para></listitem>
  105. <listitem><para>
  106. Copy and paste with an unlimited number of clipboards
  107. (known as <quote>registers</quote>)
  108. </para></listitem>
  109. <listitem><para>
  110. <quote>Markers</quote> for remembering positions
  111. in files to return to later
  112. </para></listitem>
  113. <listitem><para>
  114. Rectangular selection
  115. </para></listitem>
  116. <listitem><para>
  117. Multiple selection for manipulating several chunks of text at once
  118. </para></listitem>
  119. <listitem><para>
  120. Syntax highlighting for more than 60 file types
  121. </para></listitem>
  122. <listitem><para>
  123. Intelligent bracket matching that skips quoted literals
  124. and comments
  125. </para></listitem>
  126. <listitem><para>
  127. Auto indent and word wrap
  128. </para></listitem>
  129. <listitem><para>
  130. Abbreviations
  131. </para></listitem>
  132. <listitem><para>
  133. <quote>Folding</quote> display mode that hides levels of
  134. indented text specified by the user
  135. </para></listitem>
  136. <listitem><para>
  137. Search and replace using both literal text and regular expressions
  138. </para></listitem>
  139. <listitem><para>
  140. <quote>HyperSearch</quote> option to show all found
  141. matches in a list
  142. </para></listitem>
  143. <listitem><para>
  144. File management functions available from within jEdit, including
  145. deleting and renaming files and creating new directories
  146. </para></listitem>
  147. <listitem><para>
  148. Choice of character encoding for loading and saving files
  149. </para></listitem>
  150. <listitem><para>
  151. Automatic compression and decompression of GZipped (.gz) files
  152. </para></listitem>
  153. <listitem><para>
  154. Plugin support for loading files from ZIP and TAR archives
  155. </para></listitem>
  156. <listitem><para>
  157. Plugin support for loading and saving files on FTP servers
  158. </para></listitem>
  159. <listitem><para>
  160. Fully customizable keyboard shortcuts, tool bar and right-click
  161. context menu
  162. </para></listitem>
  163. <listitem><para>
  164. Macro system permitting recording and writing of macros in the
  165. BeanShell scripting language
  166. </para></listitem>
  167. <listitem><para>
  168. An internal <quote>plugin manager</quote> that downloads and installs
  169. new and updated plugins from within jEdit
  170. </para></listitem>
  171. </itemizedlist>
  172. </answer>
  173. </qandaentry>
  174. <qandaentry>
  175. <question id="what-plugin"><para>
  176. What is a jEdit <quote>plugin</quote>?
  177. </para></question>
  178. <answer><para>
  179. A plugin is an application that is designed to work with jEdit
  180. by providing additional features that can be used from within
  181. the main program. Often the plugin will provide a visible user
  182. interface in a window that can be docked to jEdit's main view
  183. window.
  184. </para>
  185. <para>
  186. There are currently over 40 publicly available plugins that
  187. provide such services as a Java source code browser, a
  188. command-line shell, templated text insertion, and source code
  189. project management. They can be downloaded, installed, and kept
  190. current from within jEdit's <quote>Plugin Manager</quote>.
  191. There is also a section of the jEdit web site called <ulink
  192. url="http://plugins.jedit.org/">Plugin Central</ulink> that
  193. maintains a descriptive index and download links for all publicly
  194. available plugins.
  195. </para>
  196. <para>
  197. Additional questions and answers regarding plugins may be found
  198. in the section of this document entitled
  199. <link linkend="plugins"><quote>Working with
  200. Plugins</quote></link>.
  201. </para></answer>
  202. </qandaentry>
  203. <qandaentry>
  204. <question id="get-doc"><para>
  205. How do I get documentation on jEdit?
  206. </para></question>
  207. <answer><para>
  208. There is a comprehensive User's Guide available from within the program
  209. using the <guimenu>Help</guimenu> menu. The User's Guide can also
  210. be downloaded from the <ulink
  211. url="http://www.jedit.org/index.php?page=download&amp;platform=source">
  212. jEdit web site</ulink> in Portable Document Format (PDF), suitable for
  213. online display or printing.
  214. </para></answer>
  215. </qandaentry>
  216. <qandaentry>
  217. <question id="is-newsgroup"><para>
  218. Is there a newsgroup or mailing list devoted to jEdit?
  219. </para></question>
  220. <answer><para>
  221. Currently there is no newsgroup devoted to jEdit. There are three
  222. active mailing lists that are freely available by subscription:
  223. </para>
  224. <itemizedlist>
  225. <listitem><para>
  226. The <ulink url=
  227. "http://lists.sourceforge.net/lists/listinfo/jedit-users">
  228. jedit-users list</ulink>, for comments and questions about
  229. using jEdit and its features
  230. </para></listitem>
  231. <listitem><para>
  232. The <ulink url=
  233. "http://lists.sourceforge.net/lists/listinfo/jedit-devel">
  234. jedit-devel list</ulink>, for discussion of development issues by
  235. members of the developer team and other interested persons
  236. </para></listitem>
  237. <listitem><para>
  238. The <ulink url=
  239. "http://lists.sourceforge.net/lists/listinfo/jedit-announce">
  240. jedit-announce list</ulink>, a low-volume list used for announcing
  241. new releases of jEdit and plugins
  242. </para></listitem>
  243. </itemizedlist>
  244. <para>
  245. Each of these lists can be obtained on a full-text message or a daily
  246. digest basis. The daily digest bundles groups of postings in a single
  247. email message.
  248. </para>
  249. <para>
  250. If you are only interested in version announcements and plugin updates,
  251. <ulink url="http://lists.sourceforge.net/lists/listinfo/jedit-announce">
  252. subscribe to the jedit-announce list</ulink>. If you would like to participate
  253. in discussion or ask questions regarding jEdit, <ulink url=
  254. "http://lists.sourceforge.net/lists/listinfo/jedit-users">subscribe to the
  255. jedit-users list</ulink>. If you are interested in jEdit's development or want
  256. to write plugins, <ulink
  257. url="http://lists.sourceforge.net/lists/listinfo/jedit-devel">
  258. subscribe to jedit-devel</ulink>.
  259. </para>
  260. <para>
  261. Do not cross-post to both lists. All jEdit developers are
  262. subscribed to both the jedit-users and jedit-devel lists, so a post to
  263. jedit-users will be seen by most members of both lists. Also, keep in
  264. mind that both jEdit-users and
  265. jEdit-devel are high-traffic lists, and can fill up your mailbox unless
  266. you check your email regularly.
  267. </para>
  268. </answer>
  269. </qandaentry>
  270. <qandaentry>
  271. <question id="is-website"><para>
  272. Is there a web site devoted to jEdit?
  273. </para></question>
  274. <answer><para>
  275. There are several. The official <ulink url="http://www.jedit.org">jEdit
  276. web site</ulink> contains extensive information on all things having to
  277. do with jEdit. There are also resources available for those interested
  278. in jEdit development on the <ulink url=
  279. "http://sourceforge.net/projects/jedit">jEdit project page</ulink> of
  280. the <ulink url="http://sourceforge.net">SourceForge web site</ulink>.
  281. </para>
  282. <para>
  283. The <ulink url="http://community.jedit.org">jEdit Community</ulink> web
  284. site has articles on jEdit and related topics, user-submitted macros and
  285. other download resources, and listings of web links of interest to jEdit
  286. users. It has a message board system to allow users to ask
  287. questions and provide feedback on the project without having to subscribe
  288. to jEdit's mailing lists. Because the message boards have relatively low
  289. volume, using the mailing lists will often be a more effective
  290. approach.
  291. </para>
  292. <para>
  293. The jEdit Community site also has an <quote>Interactive FAQ</quote>
  294. facility that allows you to post questions to be answered by
  295. other users, and a screenshot gallery containg images
  296. submitted by users.
  297. </para></answer>
  298. </qandaentry>
  299. <qandaentry>
  300. <question id="copyright"><para>
  301. Are there copyright restrictions on the use of jEdit?
  302. </para></question>
  303. <answer><para>
  304. The jEdit application is free, <quote>Open Source</quote> software released
  305. under the <ulink url="http://www.gnu.org/licenses/licenses.html#GPL">
  306. GNU General Public License</ulink>. This ensures that jEdit and its source
  307. code remains freely available for use and distribution by the public.
  308. For specific copyright questions, you should review the General Public
  309. License and seek appropriate advice. Broadly speaking, there are no
  310. restrictions on the use of the program as a text editor, and its source
  311. code can be copied or modified for use in another program that is
  312. governed by the General Public License.
  313. </para>
  314. <para>
  315. Plugin application that are available using jEdit's Plugin Manager
  316. facility, as well as plugins available through the <ulink
  317. url="http://plugins.jedit.org">Plugin Central</ulink> web site or
  318. <ulink url="http://community.jedit.org">jEdit Community</ulink>, are
  319. governed either by the General Public License or another commonly
  320. recognized <quote>Open Source</quote> software license. This means
  321. that use of the application, including use for commercial purposes,
  322. is unrestricted without any requirement of royalty or license fee payments.
  323. To incorporate source code or an application or plugin as a whole in another
  324. application, you must consult the specific license terms to determine
  325. whether and on what basis you are permitted to do so.
  326. </para>
  327. </answer>
  328. </qandaentry>
  329. <qandaentry>
  330. <question id="java-only"><para>
  331. Is jEdit only useful for programming in Java?
  332. </para></question>
  333. <answer><para>
  334. Absolutely not. Many of the jEdit's plugin applications, and a few of
  335. the macros distributed with the program, target the Java language or
  336. integrate tools used in Java development. However, the core application
  337. is designed to work with any programming or markup language. Included
  338. with jEdit are packages providing syntax highlighting,
  339. abbreviations and other programming support for over 60 programming
  340. languages and file types, including C, C++, C#,
  341. Cobol, HTML, Java, Javascript, Lisp, Pascal, Perl, PHP, Python,
  342. TCL, Visual Basic and XML. The full list can be found on the
  343. <ulink url="http://www.jedit.org/index.php?page=features">jEdit web
  344. site</ulink>.
  345. </para></answer>
  346. </qandaentry>
  347. <qandaentry>
  348. <question id="knowing-java"><para>
  349. Do I need to know Java to use jEdit?
  350. </para></question>
  351. <answer><para>
  352. No. In fact, you do not need to know any specific programming language
  353. other than the ones with which you work.
  354. </para>
  355. <para>
  356. At some point in your use of jEdit, you will no doubt want to write your
  357. own macros to execute long or complex routines with a single command or
  358. keyboard shortcut. Macros in jEdit are written in a simplified dialect
  359. of Java called <ulink url="http://www.beanshell.org"> BeanShell</ulink>.
  360. Its syntax will be familiar to users of Java, C++ and other
  361. object-oriented languages, and it is not hard to learn even if you have
  362. no experience with those languages. The User's Guide provided
  363. with jEdit contains an extensive tutorial on writing macros.
  364. </para></answer>
  365. </qandaentry>
  366. <qandaentry>
  367. <question id="needed-software"><para>
  368. What software do I need to install and run jEdit?
  369. </para></question>
  370. <answer><para>
  371. Since jEdit runs on a Java platform, at a minimum you will need a Java
  372. Runtime Environment (JRE) package. If you are planning to use jEdit to
  373. program in Java, you will need a full Java Development Kit (JDK) package.
  374. We recommend obtaining a JDK package.
  375. </para>
  376. <para>
  377. The current version of jEdit, version 4.0, requires a Java runtime
  378. environment having a release version of 1.3 or greater. It will
  379. not run on versions 1.1 or 1.2. The <ulink
  380. url="http://www.jedit.org/index.php?page=compatibility">jEdit web
  381. site</ulink> contains a detailed discussion on the compatibility of
  382. various publicly available JDK's for the major operating systems.
  383. </para></answer>
  384. </qandaentry>
  385. <qandaentry>
  386. <question id="just-learning"><para>
  387. I've just started to learn programming. Is jEdit a good choice for my
  388. first text editor?
  389. </para></question>
  390. <answer><para>
  391. It is an excellent choice. Its basic features are extremely easy to use,
  392. and you will find things like abbreviations, keyboard shortcuts and
  393. macros to be great time-savers. It has built-in packages called
  394. <quote>edit modes</quote> that automatically display keywords, tags, and
  395. other program elements in different colors, making it easier to view and
  396. organize your code. It works well with many Open Source and proprietary
  397. programming tools. Because of its extensive customization features, it
  398. can adapt to your preferences and work patterns as you become more
  399. experienced. Finally, it's free, so you can buy a lot of programming texts
  400. with the money you will save.
  401. </para></answer>
  402. </qandaentry>
  403. </qandadiv>
  404. <qandadiv id="latest-version">
  405. <title>Getting the latest version</title>
  406. <qandaentry>
  407. <question id="get-latest-version"><para>
  408. How do I obtain the latest version of jEdit?
  409. </para></question>
  410. <answer><para>
  411. The program is in a continuing state of evolution. It is usually
  412. available in two versions, a <quote>stable</quote> version and a
  413. <quote>development</quote> version. A stable version represents a
  414. release of jEdit that is considered to be free of serious bugs or
  415. performance problems and suitable for general use. A
  416. <quote>development</quote> version includes new features or new elements
  417. of program design that require testing and possible further refinement.
  418. A development version contains the token <quote>pre</quote> in its
  419. version number, as in <literal>4.0pre5</literal>.
  420. </para>
  421. <para>
  422. The latest stable and development versions of jEdit are always
  423. available from the <ulink url="http://www.jedit.org">jEdit
  424. web site</ulink> and from the <ulink url="http://sourceforge.net/
  425. projects/jedit">jEdit project page</ulink> of the
  426. <ulink url="http://sourceforge.net">SourceForge web site</ulink>,
  427. which hosts jEdit's development resources.
  428. </para>
  429. <para>
  430. In addition, a plugin named <application>Check jEdit
  431. Version</application> can be run from within jEdit by selecting
  432. <guimenuitem>Check jEdit Version</guimenuitem> from the application's
  433. <guimenu>Plugins</guimenu> menu. It queries the jEdit web site, compares
  434. version information with the version of the currently running
  435. instance of jEdit, and reports the result to the user in a message box.
  436. It will tell you if you do not have the latest version of jEdit, regardless
  437. of whether that version is in <quote>stable</quote> or
  438. <quote>development</quote> form.
  439. </para>
  440. <para>
  441. Finally, if you subscribe to the <ulink
  442. url="http://lists.sourceforge.net/lists/listinfo/jedit-announce">
  443. jedit-announce</ulink> or <ulink
  444. url="http://lists.sourceforge.net/lists/listinfo/jedit-users">
  445. jedit-users</ulink> mailing lists, you will receive a email whenever
  446. a new release of jEdit becomes available.
  447. </para></answer>
  448. </qandaentry>
  449. <qandaentry>
  450. <question id="get-source"><para>
  451. How do I obtain a copy of the jEdit source code?
  452. </para></question>
  453. <answer><para>
  454. The latest version of jEdit's source code is available from the
  455. <ulink url="http://www.jedit.org/index.php?page=download&amp;platform=source">
  456. jEdit web site</ulink> or the <ulink url=
  457. "http://sourceforge.net/project/showfiles.php?group_id=588">
  458. SourceForge web site</ulink>. The web site provides the source code for the
  459. latest stable and development version, while the SourceForge site has
  460. a more extensive archive covering earlier versions.
  461. </para>
  462. <para>
  463. If you are interested in testing the absolutely latest changes to jEdit,
  464. and you are familiar with compiling your own Java programs and working
  465. with CVS, you can download the current code maintained in the <ulink
  466. url="http://sourceforge.net/cvs/?group_id=588">SourceForge
  467. CVS repository</ulink>.
  468. </para></answer>
  469. </qandaentry>
  470. <qandaentry>
  471. <question id="get-latest-faq"><para>
  472. Where can I get the latest version of this document?</para>
  473. </question><answer>
  474. <para>
  475. The latest release of this document is available at the
  476. <ulink
  477. url="http://jedit-community.sourceforge.net/modules.php?op=modload&amp;name=Include_Pages&amp;file=index&amp;req=viewarticle&amp;artid=5">
  478. jEdit Community web site</ulink>.
  479. </para>
  480. </answer>
  481. </qandaentry>
  482. <qandaentry>
  483. <question id="jedit-compile">
  484. <para>
  485. How do you set the classpath and compile the java files in jEdit?
  486. </para>
  487. </question>
  488. <answer>
  489. <para>
  490. Consult an article on the <ulink url="http://community.jedit.org">jEdit
  491. Community</ulink> web site entitled <quote>Build jEdit yourself: the 'Open'
  492. in Open Source</quote>.
  493. </para>
  494. </answer>
  495. </qandaentry>
  496. </qandadiv>
  497. </qandaset>
  498. </sect1>
  499. <sect1 id="problems"><title>Getting Answers and Reporting Problems</title>
  500. <para>
  501. This section deals with how to get answers to questions that the
  502. documentation does not address, how you can report problems with jEdit
  503. or its plugins, and how best to communicate with the jEdit developer team.
  504. </para>
  505. <qandaset defaultlabel="qanda">
  506. <qandadiv id="get-answers-div">
  507. <title>Getting answers</title>
  508. <qandaentry>
  509. <question id="get-answers"><para>
  510. How do I get answers to my questions about jEdit?
  511. </para></question>
  512. <answer>
  513. <para>
  514. You should look for answers in the following places:
  515. </para>
  516. <itemizedlist>
  517. <listitem><para>
  518. The User's Guide available from the application's
  519. <guimenu>Help</guimenu> menu.
  520. </para></listitem>
  521. <listitem><para>
  522. This FAQ document.
  523. </para></listitem>
  524. <listitem><para>
  525. The archives of jEdit's mailing lists. Archives for both the
  526. <ulink url="http://www.geocrawler.com/redir-sf.php3?list=jedit-users">
  527. jedit-users list</ulink> and the
  528. <ulink url="http://www.geocrawler.com/redir-sf.php3?list=jedit-devel">
  529. jedit-devel list</ulink> are available.
  530. </para></listitem>
  531. </itemizedlist>
  532. <para>
  533. If you cannot find help using those resources, post your question to the
  534. <ulink url="mailto:jedit-users@lists.sourceforge.net"> jedit-users
  535. list</ulink>. You will have to <ulink
  536. url="http://lists.sourceforge.net/lists/listinfo/jedit-users">
  537. subscribe to the mailing list</ulink> in order to
  538. post, but it is well worth it, and you can elect to have daily bundles
  539. of messages sent to you to keep email traffic down. Many questions
  540. are answered on the mailing list within 24 hours. The developers who
  541. respond to user questions generally do not send direct replies, so you
  542. will need to monitor messages from the mailing list is order to
  543. obtain an answer.
  544. </para>
  545. </answer>
  546. </qandaentry>
  547. <qandaentry>
  548. <question id="interactive-help"><para>
  549. Where can I get interactive help for jEdit?
  550. </para></question>
  551. <answer><para>
  552. There is an IRC channel, <filename>#jedit</filename>, available
  553. on the irc.openprojects.net server that is dedicated to jEdit support
  554. and discussion among developers. You can reach it using
  555. any IRC client (including Chatzilla), as well as the IRC plugin
  556. for jEdit.
  557. </para>
  558. <para>
  559. There is almost always someone from the developer team
  560. signed on the channel. Just say hello and describe your problem.
  561. </para></answer>
  562. </qandaentry>
  563. </qandadiv>
  564. <qandadiv id="bugs">
  565. <title>Reporting bugs</title>
  566. <qandaentry>
  567. <question id="report-bugs"><para>
  568. How do I report a bug I have found in jEdit?
  569. </para></question>
  570. <answer><para>
  571. To be as helpful as possible to the jEdit developer team and other
  572. users, you should use the <ulink
  573. url="http://sourceforge.net/tracker/index.php?group_id=588&amp;atid=100588">
  574. bug tracker database</ulink> that the jEdit project maintains on the
  575. <ulink url="http://sourceforge.net/">SourceForge web site</ulink>. You
  576. do not need to be a SourceForge member to post a bug report.
  577. </para>
  578. <para>
  579. Before posting a bug report, spend a few moments searching the bug
  580. database to see if a similar report has already been made. The bug
  581. tracker has a search facility that will let search for bug reports using
  582. a variety of criteria. If you find a similar bug report, and you
  583. have additional information to contribute, post a comment
  584. to the report. If you do not find a similar bug report, submit a new
  585. report.
  586. </para></answer>
  587. </qandaentry>
  588. <qandaentry>
  589. <question id="bug-report"><para>
  590. What information should I include in a bug report?
  591. </para></question>
  592. <answer><para>
  593. The form in the bug tracker report provides several fields for
  594. submitting information. If you are unsure about a particular
  595. item, leave it at the default setting provided in the form.
  596. </para>
  597. <para>
  598. The more important fields are <quote>Category</quote>,
  599. <quote>Summary</quote> and the <quote>Initial comment</quote>.
  600. When you write your initial comment describing the bug, you
  601. should specify the versions of jEdit, the Java platform and
  602. operating system you are using, because bugs often arise that
  603. are specific to particular versions. Sometimes the bug
  604. arises from the Java runtime environment or even the
  605. operating system, and knowing these details helps the
  606. developer team design testing and other debugging strategies.
  607. </para>
  608. <para>
  609. One of the macros installed with jEdit is called <guimenuitem>Make Bug
  610. Report</guimenuitem>. You will it find under the
  611. <guimenuitem>Misc</guimenuitem> category of the <guimenu>Macros
  612. </guimenu> menu. This macro extracts information regarding your jEdit
  613. installation and a stack trace from the last error recorded by jEdit's
  614. Activity Log and places it in a new text buffer. In many cases, the
  615. information furnished by the macro is all that is necessary to provide a
  616. helpful description of a bug. You can simply cut and paste the
  617. output of the macro into the <quote>Initial comment</quote> field of the
  618. bug report form.
  619. </para></answer>
  620. </qandaentry>
  621. <qandaentry>
  622. <question id="bug-track">
  623. <para>
  624. How do I track the status of a jEdit bug report?
  625. </para>
  626. </question>
  627. <answer>
  628. <para>
  629. If you know the bug report number, go to this web address:
  630. <userinput>http://sourceforge.net/tracker/index.php?func=detail&amp;aid=######&amp;group_id=588&amp;atid=100588</userinput>,
  631. where <userinput>######</userinput> is the bug report number. If you don't know the bug report number,
  632. you can browse and search the <ulink
  633. url="http://sourceforge.net/tracker/index.php?group_id=588&amp;atid=100588">
  634. bug database</ulink> to find the problem in which you are interested.
  635. </para>
  636. </answer>
  637. </qandaentry>
  638. </qandadiv>
  639. <qandadiv id="contact">
  640. <title>Contacting jEdit developers</title>
  641. <qandaentry>
  642. <question id="contact-team"><para>
  643. How do I contact members of the jEdit developer team?
  644. </para></question>
  645. <answer><para>
  646. If you want to ask a question, make a feature request or offer other
  647. general comments, the easiest way is to join and post a message to the
  648. <ulink url="mailto:jedit-users@lists.sourceforge.net">
  649. jedit-users mailing list</ulink>. All developers are members. If you are
  650. interested in working on jEdit or writing a plugin for it, use the
  651. <ulink url="mailto:jedit-users@lists.sourceforge.net">
  652. jedit-devel list</ulink>. Email addresses for individual developers
  653. can be found on the <ulink
  654. url="http://sourceforge.net/project/memberlist.php?group_id=588">
  655. SourceForge web site</ulink>.
  656. </para></answer>
  657. </qandaentry>
  658. </qandadiv>
  659. </qandaset>
  660. </sect1>