Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ workshop(1) — Sun WorkShop 5.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

workshop(1)

NAME

workshop − An Integrated Programming Environment

SYNOPSIS

workshop [ standard motif toolkit options ] [ −D [ a.out [ core | pid ] ] [ −s editsessionname ] [ −x sessionfile-directory ] [ −V ] [ worksetname ]

AVAILABILITY

Available on Solaris 2.5.1, 2.6, and 2.7 on SPARC and x86, running OpenWindows, CDE, or Motif 1.2. 

DESCRIPTION

WorkShop is an integrated programming environment that allows you to build, edit, debug, and browse a program without having to explicitly start individual tools. 

You have the option of using the text editor of your choice by choosing Text Editor Options... from the Options menu and selecting an editor in the Text Editor Options dialog box that is displayed. 

OPTIONS

workshop accepts all standard Motif Toolkit command line options.  In addition, the following options are accepted:

−D a.out [core|pid]
Run WorkShop and start a debugging session. If a.out is specified, load this program into the Debugger. If core is specified, the Debugger will use it to do post-mortem debugging on a.out.  If pid is specified, the Debugger will attach to the process with the given process id. In this case you can use "-" instead of a.out but then the executable information will not be stored in picklists or worksets. 

−s editsessionname
Run WorkShop under the edit server named editsessionname.  If there is no edit server with the given name, start one. If this option is not specified (that is, the default), WorkShop applications will share the same editor. 

−x sessionfile-directory
Read and write Sun WorkShop’s session files .workshop∗ in the specified directory rather than the home directory. Allows multiple configurations. 

−V Display the Sun WorkShop version string on standard output. 

worksetname
Load the specified workset into Sun WorkShop. If a workset with the given name does not exist, one is created.

Starting Sun WorkShop

To start Sun WorkShop from a shell, type workshop & at the command prompt. 

Starting Sun WorkShop From Emacs

You can start Sun WorkShop directly from the editor without having to return to the command line. When you quit out of Emacs, both Sun WorkShop and Emacs are terminated. 

You can start Sun WorkShop from the XEmacs editor in three ways:

∗ Type M-x workshop-start in the minibuffer. 

∗ Choose Start Sun WorkShop from the Tools menu. 

∗ Click on the WorkShop button in the tool bar. 

You can start Sun WorkShop from the GNU Emacs editor as follows:

1. Load workshop.el by setting the load path in your .emacs file as follows:

   (setq load-path
     (append load-path ’("/WorkShop_install_directory/lib")))
   (require ’workshop)

   and then restarting Emacs. 

2. Type M-x workshop-start or choose Start Sun WorkShop from the Tools menu. 

Breaking the Sun WorkShop-Emacs Connection

You can break the connection between Emacs and Sun WorkShop with the command, M-x workshop-quit. If you started Sun WorkShop from Emacs, this command will terminate the Sun WorkShop process while continuing to run Emacs. 

If you try to start Sun WorkShop from Emacs and Sun WorkShop does not connect to the editor or does not appear at all, you should terminate Sun WorkShop from Emacs by choosing Quit WorkShop from the WorkShop menu. 

Customizations

Windows

Sun WorkShop windows can be customized by changing the default X resource values. The X resource files for Sun WorkShop, named WORKSHOP and ESERVE, can be found in the directory:

  wdir/lib/locale/LANG/app−defaults/CDE

where:

wdir is the directory where Sun WorkShop was installed, usually
/opt/SUNWspro. 

LANG is your current locale, for example, C or ja. 

CDE is either CDE or non-CDE, depending on whether
or not Sun WorkShop is running in a CDE environment.

You do not have to modify any of the resources in order to use Sun WorkShop.  However, if you do want to make modifications, follow these steps:

1. Copy the WorkShop X resource files to be modified to your home directory, or some other private directory on your XUSERFILESEARCHPATH. 

2. Modify the resources you are interested in changing. For example, if you wish to change the background color of the push buttons to white, you would set this resource in the WORKSHOP resource file:

   WORKSHOP∗XmPushButton∗background: #FFFFFF

   CAUTION: Gratuitous changes can cause Sun WorkShop to malfunction! 

Function Keys

By default, Sun WorkShop binds Emacs function keys to commands useful for interacting with Sun WorkShop.  You can disable the key rebinding by re-setting the Emacs variable eserve−bind−fkeys. To do this, add the following line to your .emacs file:

  (setq eserve-bind-fkeys nil)

ENVIRONMENT

SPRO_LAUNCH_EDITOR_FROM_PATH
When launching xemacs, Sun WorkShop first looks for it in the top-level bin directory of the Sun WorkShop installation. If it cannot find xemacs there, Sun WorkShop searches for it using the PATH environment variable. Setting SPRO_LAUNCH_EDITOR_FROM_PATH to any value disables the check for xemacs in the top-level bin directory of the Sun WorkShop installation. 

SPRO_LAUNCH_TOOLS_FROM_PATH
When launching tools from the main window toolbar or from the Tools menu, Sun WorkShop first looks for a binary in the top-level bin directory of the Sun WorkShop installation. If it cannot find the binary there, Sun WorkShop searches for the binary using the PATH environment variable. Setting SPRO_LAUNCH_TOOLS_FROM_PATH to any value disables the check for the binary in the top-level bin directory of the Sun WorkShop installation. 

SPRO_DBX_PATH
When launching dbx, use this path instead of the default location.

SEE ALSO

WorkShop: Getting Started
WorkShop: Beyond the Basics
WorkShop: Command-Line Utilities

SunOS 5.0  —  Last change: 06/08/98

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026