Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Commit [54fe39] jedit-0-2-19980929 Maximize Restore History

import of jEdit-0.2-19980929

Slava Pestov Slava Pestov 1998-09-29

1 2 > >> (Page 1 of 2)
added doc/index.txt
added doc/installing.txt
added doc/old
added doc/old/menus.txt
added etc
added etc/jEdit.kdelnk
added etc/jOpen.kdelnk
added etc/jedit.pif
added etc/jopen.pif
added etc/pif.txt
added src/Cmd_print.java
changed Makefile
changed README
changed bin
changed bin/jedit.bat
changed bin/jopen.bat
changed doc
changed doc/Makefile
changed doc/menus.txt
changed installit.bat
changed src
changed src/Buffer.java
changed src/Cmd_about.java
changed src/Cmd_help.java
changed src/Makefile
changed src/View.java
changed src/jEdit.java
changed src/jOpen.java
changed src/properties
copied doc/commands.txt -> doc/old/commands.txt
copied doc/plugins.txt -> doc/old/plugins.txt
copied BUGS -> VERSION
copied INSTALL -> doc/old/props.txt
copied TODO -> etc/kdelnk.txt
copied doc/props.txt -> doc/old/server.txt
copied doc/server.txt -> doc/starting.txt
doc/index.txt Diff Switch to side-by-side view
Loading...
doc/installing.txt Diff Switch to side-by-side view
Loading...
doc/old
Directory.
doc/old/menus.txt Diff Switch to side-by-side view
Loading...
etc
Directory.
etc/jEdit.kdelnk Diff Switch to side-by-side view
Loading...
etc/jOpen.kdelnk Diff Switch to side-by-side view
Loading...
etc/jedit.pif Diff Switch to side-by-side view
Loading...
etc/jopen.pif Diff Switch to side-by-side view
Loading...
etc/pif.txt Diff Switch to side-by-side view
Loading...
src/Cmd_print.java Diff Switch to side-by-side view
Loading...
Makefile Diff Switch to side-by-side view
Loading...
README Diff Switch to side-by-side view
Loading...
bin
Directory.
bin/jedit.bat Diff Switch to side-by-side view
Loading...
bin/jopen.bat Diff Switch to side-by-side view
Loading...
doc
Directory.
doc/Makefile Diff Switch to side-by-side view
Loading...
doc/menus.txt Diff Switch to side-by-side view
Loading...
installit.bat Diff Switch to side-by-side view
Loading...
src
Directory.
src/Buffer.java Diff Switch to side-by-side view
Loading...
src/Cmd_about.java Diff Switch to side-by-side view
Loading...
src/Cmd_help.java Diff Switch to side-by-side view
Loading...
src/Makefile Diff Switch to side-by-side view
Loading...
src/View.java Diff Switch to side-by-side view
Loading...
src/jEdit.java Diff Switch to side-by-side view
Loading...
src/jOpen.java Diff Switch to side-by-side view
Loading...
src/properties Diff Switch to side-by-side view
Loading...
doc/commands.txt to doc/old/commands.txt
File was copied or renamed.
doc/plugins.txt to doc/old/plugins.txt
File was copied or renamed.
BUGS to VERSION
--- a/BUGS
+++ b/VERSION
@@ -1,8 +1,14 @@
-JEDIT KNOWN BUGS
+VERSION INFORMATION (VERSION, last modified 29 Sep 1998)
 
-- some null pointer conditions might not be handled well
-- code isn't very thread safe
-- some obscure error conditions aren't handled very well
+-- Version 0.2 To Do:
+- Search and replace
+- Printing
+- Options dialog
+- Better documentation
+- Persistent markers
+- Fix handling of obscure errors
+- Make code thread safe
+- Make null pointer handling better
 
 -- Slava Pestov
 <slava_pestov@geocities.com>
INSTALL to doc/old/props.txt
--- a/INSTALL
+++ b/doc/old/props.txt
@@ -1,50 +1,46 @@
-JEDIT INSTALLATION INSTRUCTIONS
+JEDIT PROPERTY MANAGER
 
-1. General
+1. Introduction
+---------------
+jEdit's settings, strings and menus are stored in property files. This makes
+them easier to modify. For more information about menus, see menus.txt.
+
+2. Startup
 ----------
-jEdit requires a Java VM and Sun's Java Foundation Classes. A Java VM for
-Solaris, Windows 95/NT and the MacOS can be found at <http://java.sun.com>.
-A Linux version is available at <http://java.blackdown.org>. JFC can be
-downloaded from <http://java.sun.com>.
+jEdit loads the following property files on startup:
+- The default property file. It is located in the jEdit JAR. If it could not
+  be found or if there is an error loading it, jEdit will exit.
+- The user's property file, unless the -nousrprops switch is specified on the
+  command line. By default, this is ~/.jedit on Unix, and some JVM-dependent
+  directory on Windows 95/NT.
+- Any *.props files in the plugin JARs.
 
-2. Unix & Clones
-----------------
-Use the supplied Makefile. If you want to recompile the source, type `make' at
-a shell prompt in the jEdit directory. Then log in as root and `make install'.
+Because the properties from the plugins are loaded after the other property
+files, you can't just put some properties into your user props file to override
+them. You must create your own plugin and ensure that it loads after the plugin
+whose properties you want to override.
 
-By default, everything will be installed under /opt/slava. If you want to
-install jEdit elsewhere, edit the Make.rules file.
+3. Format
+---------
+Property files are in the standard Java property format. Generally, it goes
+like this:
+opt1=value
+opt2=value2
+module.opt1=some value
+module.opt2=some other value
+When creating your own property files, you should group related items under a
+single module name.
 
-Once it's installed, you'll have to add /opt/slava/bin to your PATH. On bourne
-compatible shells (sh, jsh, ash, bash, zsh) the command to do this is
-	PATH=$PATH:/opt/slava/bin;export PATH
-Or on C shells (csh, tcsh)
-	setenv PATH $PATH:/opt/slava/bin
-You might want to add this command to your .profile (bourne shell) or
-.csh.login (C shell) if you don't want to type this every time you log in.
-
-Finally, type `jedit' to start jEdit or `jopen' to open files in a running
-instance of jEdit.
-
-3. Windows 95/NT
-----------------
-Use the makeit.bat batch file to compile it if necessary and
- the installit.bat
-batch file to install it. By default, everything will be
- installed under
-C:\Program Files\jEdit. If you don't like this, edit the top
- level installit.bat
-file.
-
-Once it's installed, run C:\Program Files\jEdit\jedit.bat to start jEdit or
-C:\Program Files\jEdit\jopen.bat to open files in a running instance of jEdit.
-
-4. MacOS
---------
-No idea whatsoever... sorry, I don't have access to a modern Mac. Try
- compiling
-all the Java files and running the jEdit class as a stand alone
- application.
+4. Changing Properties
+----------------------
+The easiest way to change a property is to add it to your user property file.
+But finding the name of the property might be tricky. If you have the full JDK
+installed, you can use the jar program to extract the default properties and
+copy the appropriate values to your user properties file. Use this command to
+accomplish this:
+jar xf <path to jedit.jar>/jedit.jar properties
+Then you can copy properties to your user properties file and delete the
+properties you don't want to change.
 
 -- Slava Pestov
 <slava_pestov@geocities.com>
TODO to etc/kdelnk.txt
--- a/TODO
+++ b/etc/kdelnk.txt
@@ -1,10 +1,6 @@
-TODO FOR JEDIT
+KDELNK README (kdelnk.txt, last modified 29 Sep 1998)
 
-- Search/replace
-- Printing
-- Options dialog
-- Better docs
-- Persistent marks
-  
+If you use the K Desktop Enviroment, you'll find these .kdelnk files handy.
+
 -- Slava Pestov
 <slava_pestov@geocities.com>
doc/props.txt to doc/old/server.txt
--- a/doc/props.txt
+++ b/doc/old/server.txt
@@ -1,46 +1,49 @@
-JEDIT PROPERTY MANAGER
+JEDIT CLIENT/SERVER
 
 1. Introduction
 ---------------
-jEdit's settings, strings and menus are stored in property files. This makes
-them easier to modify. For more information about menus, see menus.txt.
+Using jEdit's client/server features, it is possible to have only instance of
+jEdit running at any time, and use the jOpen utility to instruct that instance
+to open files. This saves memory and makes the buffer list global.
 
-2. Startup
-----------
-jEdit loads the following property files on startup:
-- The default property file. It is located in the jEdit JAR. If it could not
-  be found or if there is an error loading it, jEdit will exit.
-- The user's property file, unless the -nousrprops switch is specified on the
-  command line. By default, this is ~/.jedit on Unix, and some JVM-dependent
-  directory on Windows 95/NT.
-- Any *.props files in the plugin JARs.
+2. The Server Side
+------------------
+The server is run by the main jEdit application. It listens for connections and
+opens the appropriate files. jEdit will only start the server if given the
+-server= command line parameter. The equals sign must be followed by the name
+of the file where the port number will be stored. For example:
+	jedit -server=~/.jedit-server
+NOTE: If you're using the jedit shell script or the jedit.bat batch file to
+start jEdit, the server is started automatically with a default port file. 
 
-Because the properties from the plugins are loaded after the other property
-files, you can't just put some properties into your user props file to override
-them. You must create your own plugin and ensure that it loads after the plugin
-whose properties you want to override.
+3. The Client Side
+------------------
+The jOpen application is the client. It connects to the jEdit server and sends
+it the list of files to open. It must be given at -portfile= option. The equals
+sign must be followed by the name of the file where the port number is stored.
+For example:
+	jopen -portfile=~/.jedit-server <files to open>
+NOTE: If you're using the jopen shell script or the jopen.bat batch file to
+start jOpen, the -portfile= option isn't necessary.
 
-3. Format
----------
-Property files are in the standard Java property format. Generally, it goes
-like this:
-opt1=value
-opt2=value2
-module.opt1=some value
-module.opt2=some other value
-When creating your own property files, you should group related items under a
-single module name.
+4. Security
+-----------
+The server accepts connections from any host, so anybody in the world can open
+files on your desktop. However, the port is only stored on the local host, so a
+remote attacker would have to guess it, and even if they do guess the port,
+they can't go much damage - only opening files.
 
-4. Changing Properties
-----------------------
-The easiest way to change a property is to add it to your user property file.
-But finding the name of the property might be tricky. If you have the full JDK
-installed, you can use the jar program to extract the default properties and
-copy the appropriate values to your user properties file. Use this command to
-accomplish this:
-jar xf <path to jedit.jar>/jedit.jar properties
-Then you can copy properties to your user properties file and delete the
-properties you don't want to change.
+5. Protocol
+-----------
+When the server starts, it finds an unused port and binds a socket to it. It
+stores the port number in the specified port file. It waits for connections.
+When a connection is made, it opens a new view, reads a new-line separated list
+of filenames, and opens them.
+
+The client connects to the port stored in the port file, and sends the list of
+files, separated by newlines.
+
+The port file stores the port number as text.
 
 -- Slava Pestov
 <slava_pestov@geocities.com>
doc/server.txt to doc/starting.txt
--- a/doc/server.txt
+++ b/doc/starting.txt
@@ -1,49 +1,113 @@
-JEDIT CLIENT/SERVER
+STARTING JEDIT (starting.txt, last modified 29 Sep 1998)
 
-1. Introduction
----------------
-Using jEdit's client/server features, it is possible to have only instance of
-jEdit running at any time, and use the jOpen utility to instruct that instance
-to open files. This saves memory and makes the buffer list global.
+Contents
+--------
+1. Starting jEdit
+2. Platform Specific Notes
+3. jEdit Initialization
 
-2. The Server Side
-------------------
-The server is run by the main jEdit application. It listens for connections and
-opens the appropriate files. jEdit will only start the server if given the
--server= command line parameter. The equals sign must be followed by the name
-of the file where the port number will be stored. For example:
-	jedit -server=~/.jedit-server
-NOTE: If you're using the jedit shell script or the jedit.bat batch file to
-start jEdit, the server is started automatically with a default port file. 
+1. Starting jEdit
+-----------------
+Usually, jEdit is started to edit one or more files with this command:
 
-3. The Client Side
-------------------
-The jOpen application is the client. It connects to the jEdit server and sends
-it the list of files to open. It must be given at -portfile= option. The equals
-sign must be followed by the name of the file where the port number is stored.
-For example:
-	jopen -portfile=~/.jedit-server <files to open>
-NOTE: If you're using the jopen shell script or the jopen.bat batch file to
-start jOpen, the -portfile= option isn't necessary.
+	jedit <filename 1> <filename 2>...
 
-4. Security
------------
-The server accepts connections from any host, so anybody in the world can open
-files on your desktop. However, the port is only stored on the local host, so a
-remote attacker would have to guess it, and even if they do guess the port,
-they can't go much damage - only opening files.
+Or if another instance of jEdit is already running, jOpen can be used to open
+files in it:
 
-5. Protocol
------------
-When the server starts, it finds an unused port and binds a socket to it. It
-stores the port number in the specified port file. It waits for connections.
-When a connection is made, it opens a new view, reads a new-line separated list
-of filenames, and opens them.
+	jopen <filename 1> <filename 2>...
 
-The client connects to the port stored in the port file, and sends the list of
-files, separated by newlines.
+jEdit can also be started with no arguments:
 
-The port file stores the port number as text.
+	jedit
+
+In that case, it will open a new `Untitled' file. If jOpen is started with no
+arguments, it opens a new view of the first buffer.
+
+A number of options can also be given to jEdit:
+
+	-version: Print jEdit version and exit
+	-usage: Print a command line usage
+	-nousrprops: Don't load user properties
+	-helpdir=<dir>: Documentation directory
+	-plugindir=<dir>: Plugin directory
+	-server=<file>: Write server port to <file>
+
+If jEdit is started with the jedit shell script or the jedit.bat batch file,
+-helpdir, -plugindir and -server are set automatically.
+
+jOpen also accepts certain options:
+
+	-version: Print jOpen version and exit
+	-usage: Print command line usage
+	-server=<hostname>: jEdit server to connect to
+	-portfile=<file>: File with server port
+
+If jOpen is started with the jopen shell script or the jopen.bat batch file,
+-portfile is set automatically.
+
+If you want to open a file whose name starts with a dash (-), you must place
+the -- argument before it in the command line to stop it from being interpreted
+as an option:
+
+	jedit -- -file-who's-name-starts-with-dash
+
+The -- indicates the end of options. No more options after it are interpreted.
+
+CAVEAT: If you give jOpen a relative pathname, it will be resolved relative to
+jEdit's working directory, now jOpen's. For example, if jEdit was started from
+/home/bob/Work, and jOpen is invoked with argument `filename' from the directory
+/home/bob/Play, jEdit will try to open /home/bob/Work/filename, not
+/home/bob/Play/filename as expected.
+
+2. Platform Specific Notes
+--------------------------
+Unix and clones:
+
+You need to set the PATH variable to point to the directory with the jedit and
+jedit shell scripts so that the shell can locate them. The default location is
+/opt/slava/bin. If you're using a Bourne shell (sh, ash, jsh, bash, zsh) The
+command to add /opt/slava/bin to the PATH is:
+
+	set PATH=$PATH:/opt/slava/bin; export PATH
+
+If you're using a C shell (csh, tcsh) the equivalent is:
+
+	setenv PATH $PATH:/opt/slava/bin
+
+It is advisable to place these commands in the .profile script (Bourne shell)
+or the .csh.login script (C shell) so that the PATH will be set every time you
+log in.
+
+Windows 95 and 98:
+
+If you want to use jEdit from the command line, you must add it's directory to
+the PATH. By default, jEdit is installed in C:\Program Files\jEdit. The command
+to add that directory to the PATH is:
+
+	set PATH=%PATH%;C:\Program Files\jEdit
+
+It is advisable to place this command in your C:\AUTOEXEC.BAT so that it's
+executed every time the computer starts up.
+
+Windows NT:
+
+The PATH is set in the System control panel in Windows NT. The default
+installation directory is the same as that in Windows 95/98.
+
+Other Platforms:
+
+On systems without a DOS or Unix style shell such as the Mac, jEdit will have
+to be started manually with the following options:
+
+	-plugindir=<dir>: One of these for each directory with plugins
+	-helpdir=<dir>: The doc directory in the jEdit distribution
+	-server=<file>: Some file, in a temporary directory perhaps
+
+jOpen will have to be started with these options:
+
+	-portfile=<file>: The same filename specified in the -server option to
+	jEdit
 
 -- Slava Pestov
 <slava_pestov@geocities.com>
1 2 > >> (Page 1 of 2)