This file is indexed.

/usr/share/doc/bup/bup-newliner.html is in bup-doc 0.29-3.

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
30
31
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <meta http-equiv="Content-Style-Type" content="text/css" />
  <meta name="generator" content="pandoc" />
  <meta name="author" content="Avery Pennarun apenwarr@gmail.com" />
  <meta name="date" content="2017-04-01" />
  <title>bup-newliner(1) Bup debian/0.29-3</title>
  <style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<div id="header">
<h1 class="title">bup-newliner(1) Bup debian/0.29-3</h1>
<h2 class="author">Avery Pennarun <a href="mailto:apenwarr@gmail.com">apenwarr@gmail.com</a></h2>
<h3 class="date">2017-04-01</h3>
</div>
<h1 id="name">NAME</h1>
<p>bup-newliner - make sure progress messages don't overlap with output</p>
<h1 id="synopsis">SYNOPSIS</h1>
<p>&lt;any command&gt; 2&gt;&amp;1 | bup newliner</p>
<h1 id="description">DESCRIPTION</h1>
<p><code>bup newliner</code> is run automatically by bup. You shouldn't need it unless you're using it in some other program.</p>
<p>Progress messages emitted by bup (and some other tools) are of the form &quot;Message ### content\r&quot;, that is, a status message containing a variable-length number, followed by a carriage return character and no newline. If these messages are printed more than once, they overwrite each other, so what the user sees is a single line with a continually-updating number.</p>
<p>This works fine until some other message is printed. For example, progress messages are usually printed to stderr, but other program messages might be printed to stdout. If those messages are shorter than the progress message line, the screen will be left with weird looking artifacts as the two messages get mixed together.</p>
<p><code>bup newliner</code> prints extra space characters at the right time to make sure that doesn't happen.</p>
<p>If you're running a program that has problems with these artifacts, you can usually fix them by piping its stdout <em>and</em> its stderr through bup newliner.</p>
<h1 id="bup">BUP</h1>
<p>Part of the <code>bup</code>(1) suite.</p>
</body>
</html>