/usr/share/doc/jed-common/html/jed016.html is in jed-common 1:0.99.19-7.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 | <!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="generator" content="hevea 2.28">
<link rel="stylesheet" type="text/css" href="jed.css">
<title>Editing Binary Files</title>
</head>
<body >
<a href="jed015.html"><img src="previous_motif.gif" alt="Previous"></a>
<a href="index.html"><img src="contents_motif.gif" alt="Up"></a>
<a href="jed017.html"><img src="next_motif.gif" alt="Next"></a>
<hr>
<h2 id="sec33" class="section">15  Editing Binary Files</h2>
<p><span style="font-weight:bold">jed</span> may edit binary files as long as the proper precautions are taken. On
IBMPC systems, this involves calling the <span style="font-weight:bold">S-Lang</span> function
<code>set_file_translation</code> with an integer argument. If the argument is
0, files are opened as text files; otherwise, they are opened in binary
mode. There is no need to call this function for other systems. However,
beware of the user variable <code>ADD_NEWLINE</code> which if non zero, a
newline character will be appended to the file if the last character is
not a newline character. If you are going to edit binary files, it is
probably a good idea to set this variable to zero.</p>
<hr>
<a href="jed015.html"><img src="previous_motif.gif" alt="Previous"></a>
<a href="index.html"><img src="contents_motif.gif" alt="Up"></a>
<a href="jed017.html"><img src="next_motif.gif" alt="Next"></a>
</body>
</html>
|