File: paw%2B%2B.README.debian

package info (click to toggle)
cernlib 2004.11.04.dfsg-0sarge1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 29,292 kB
  • ctags: 1,159
  • sloc: ansic: 2,285; sh: 840; makefile: 582
file content (53 lines) | stat: -rw-r--r-- 1,647 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
Notes on paw++
--------------

1) Graphics window corruption

If you experience corruption of the graphics window when other windows are
moved over top of it, turn on the BackingStore option of the X server.
In the "Screen" section of your /etc/X11/XF86Config-4 file, you should have
something like:

Section "Screen"
        .
        .
        .
    Option "BackingStore"
        .
        .
        .
EndSection

Be aware that making this change will cause Debconf to refuse to update your X
settings; see file:///usr/share/doc/xfree86-common/FAQ.xhtml#forceoverwriteconf
for more information.

2) Remote data files

Paw++ can read files remotely from computers running the distributed PAW
(pawserv) server, which is included in the pawserv Debian package.  This is
done from within Paw++ using 'rlogin' and 'rshell' commands; see the PAW
User's Guide for details.  Please note that these commands transmit passwords
in clear text and should be used only within a secured LAN.

3) Path issues

If you compile a FORTRAN script within Paw++, the path to the file cannot
be excessively long (more than 256 characters).

4) Filename case issues

The default behavior in Debian has been set so that Paw++ is case-sensitive
in its treatment of filenames.  If you have any old Paw scripts that do not
treat filenames in a case-sensitive way, you may need to add the line

	filecase convert

to the beginning of them.

5) 64-bit issues

Note that this package is not yet fully functional on 64-bit machines, as the
COMIS portion of Pawlib does not yet work correctly on those architectures.

-- Kevin McCarty <kmccarty@princeton.edu>, Mon, 29 Nov 2004