<FILENAME filename="index.html"><html><head><title>The KDirStat Handbook</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="description" content='KDirStat is a graphical disk usage utility, very much like the Unix "du" command, plus some cleanup facilities to reclaim disk space.'><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="next" href="overview.html" title="Chapter 1. Overview"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> The KDirStat Handbook</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="overview.html">Next</a></td></tr></table></div><div id="contentBody"><div lang="en" class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idm1"></a>The KDirStat Handbook</h1></div><div><div class="authorgroup"><p class="author"><span class="firstname">Stefan</span> <span class="surname">Hundhammer</span> <code class="email"><sh@suse.de></code></p></div></div><div>Revision <span class="releaseinfo">2.4.4 (<span class="date">2002-02-22</span>)</span></div><div><p class="copyright">Copyright © 1999-2005 Stefan Hundhammer</p></div><div><p><a href="help:/kdoctools5-common/fdl-notice.html">Legal Notice</a></p></div><div><div><div class="abstract"><p>
<span class="application">KDirStat</span> is a graphical disk usage utility, very much like the Unix "du" command,
plus some cleanup facilities to reclaim disk space.
</p></div></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="overview.html">1. Overview</a></span></dt><dd><dl><dt><span class="sect1"><a href="overview.html#screenshot">Screen Shot</a></span></dt><dt><span class="sect1"><a href="features.html">Features</a></span></dt><dd><dl><dt><span class="sect2"><a href="features.html#idm46">Display Features</a></span></dt><dt><span class="sect2"><a href="features.html#idm65">Directory Reading</a></span></dt><dt><span class="sect2"><a href="features.html#idm75">Cleaning up</a></span></dt><dt><span class="sect2"><a href="features.html#idm84">Misc</a></span></dt></dl></dd><dt><span class="sect1"><a href="more-screen-shots.html">More Sceen Shots</a></span></dt><dd><dl><dt><span class="sect2"><a href="more-screen-shots.html#idm91">Configuring cleanup actions</a></span></dt><dt><span class="sect2"><a href="more-screen-shots.html#idm101">Configuring tree colors</a></span></dt><dt><span class="sect2"><a href="more-screen-shots.html#idm111">Feedback mail</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="basic_usage.html">2. Basic Usage</a></span></dt><dd><dl><dt><span class="sect1"><a href="basic_usage.html#invoking">Invoke <span class="application">KDirStat</span></a></span></dt><dt><span class="sect1"><a href="select_dir.html">Select a Directory</a></span></dt><dt><span class="sect1"><a href="find_out_where.html">Find out what Uses up all the Disk Space</a></span></dt><dt><span class="sect1"><a href="do_something.html">Do Something about it</a></span></dt></dl></dd><dt><span class="chapter"><a href="treemaps.html">3. Treemaps</a></span></dt><dd><dl><dt><span class="sect1"><a href="treemaps.html#treemap_intro">Quick Introduction to Treemaps</a></span></dt><dd><dl><dt><span class="sect2"><a href="treemaps.html#what_are_treemaps">What is it?</a></span></dt><dt><span class="sect2"><a href="treemaps.html#how_to_use_treemaps">How to Use Treemaps</a></span></dt><dt><span class="sect2"><a href="treemaps.html#treemap_advantages">Pros and Cons of Treemaps</a></span></dt><dt><span class="sect2"><a href="treemaps.html#getting_rid_of_treemaps">How to Get Rid of it</a></span></dt></dl></dd><dt><span class="sect1"><a href="treemap_actions.html">Treemap Related Actions</a></span></dt><dd><dl><dt><span class="sect2"><a href="treemap_actions.html#treemap_mouse_actions">Mouse Actions in the Treemap</a></span></dt><dt><span class="sect2"><a href="treemap_actions.html#treemap_menu_actions">Treemap Menu Actions</a></span></dt></dl></dd><dt><span class="sect1"><a href="treemap_in_depth.html">More Information about Treemaps</a></span></dt><dd><dl><dt><span class="sect2"><a href="treemap_in_depth.html#simple_treemap_construction">How a Simple Treemap is Constructed</a></span></dt><dt><span class="sect2"><a href="treemap_in_depth.html#squarified_treemaps">Squarified Treemaps</a></span></dt><dt><span class="sect2"><a href="treemap_in_depth.html#cushioned_treemaps">The Shading: Cushioned Treemaps</a></span></dt><dt><span class="sect2"><a href="treemap_in_depth.html#treemaps_optimizations"><span class="application">KDirStat</span>'s own Treemap Improvements</a></span></dt><dt><span class="sect2"><a href="treemap_in_depth.html#treemaps_credits">Credits and Further Reading about Treemaps</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="predefined_cleanups.html">4. Predefined Cleanup Actions</a></span></dt><dd><dl><dt><span class="sect1"><a href="predefined_cleanups.html#cleanup_open_in_konqueror">Open in Konqueror</a></span></dt><dt><span class="sect1"><a href="cleanup_open_in_terminal.html">Open in Terminal</a></span></dt><dt><span class="sect1"><a href="cleanup_compress.html">Compress</a></span></dt><dt><span class="sect1"><a href="cleanup_make_clean.html">make clean</a></span></dt><dt><span class="sect1"><a href="cleanup_clean_trash.html">Delete Trash Files</a></span></dt><dt><span class="sect1"><a href="cleanup_delete_to_trash_bin.html">Delete (to Trash Bin)</a></span></dt><dt><span class="sect1"><a href="cleanup_hard_delete.html">Delete (no way to undelete!)</a></span></dt></dl></dd><dt><span class="chapter"><a href="configuring_cleanups.html">5. Configuring Cleanup Actions</a></span></dt><dd><dl><dt><span class="sect1"><a href="configuring_cleanups.html#config_cleanups_reference">Reference</a></span></dt><dt><span class="sect1"><a href="config_cleanups_example.html">Examples</a></span></dt><dd><dl><dt><span class="sect2"><a href="config_cleanups_example.html#idm423">Open in Emacs</a></span></dt><dt><span class="sect2"><a href="config_cleanups_example.html#idm451">Compress</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="feedback_mail.html">6. Feedback Mail</a></span></dt><dd><dl><dt><span class="sect1"><a href="feedback_mail.html#feedback_mail_description">Description</a></span></dt><dt><span class="sect1"><a href="privacy.html">Privacy</a></span></dt><dt><span class="sect1"><a href="mail_example.html">Feedback Mail Example</a></span></dt></dl></dd><dt><span class="chapter"><a href="developers_guide.html">7. Developer's Guide to KDirStat</a></span></dt><dt><span class="chapter"><a href="faq.html">8. Questions and Answers</a></span></dt><dt><span class="chapter"><a href="credits.html">9. Credits and License</a></span></dt><dt><span class="appendix"><a href="installation.html">A. Installation</a></span></dt><dd><dl><dt><span class="sect1"><a href="installation.html#getting-kdirstat">How to obtain KDirStat</a></span></dt><dt><span class="sect1"><a href="requirements.html">Requirements</a></span></dt><dt><span class="sect1"><a href="compilation.html">Compilation and Installation</a></span></dt></dl></dd></dl></div><FILENAME filename="overview.html"><html><head><title>Chapter 1. Overview</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="index.html" title="The KDirStat Handbook"><link rel="next" href="features.html" title="Features"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Overview</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="index.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="features.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="overview"></a>Chapter 1. Overview</h1></div></div></div><p>
<span class="application">KDirStat</span> is a graphical disk usage utility. It shows you where all your disk
space has gone and tries to help clean it up.
</p><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="screenshot"></a>Screen Shot</h2></div></div></div><p>
</p><div class="screenshot"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><img src="kdirstat-main.png" alt="Main window screenshot"></div></div><p>
</p></div><FILENAME filename="features.html"><html><head><title>Features</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="overview.html" title="Chapter 1. Overview"><link rel="prev" href="overview.html" title="Chapter 1. Overview"><link rel="next" href="more-screen-shots.html" title="More Sceen Shots"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Features</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="overview.html">Prev</a></td><td class="upCell">Overview</td><td class="nextCell"><a accesskey="n" href="more-screen-shots.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="features"></a>Features</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm46"></a>Display Features</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Graphical and numeric display of used disk space
</p></li><li class="listitem"><p>
Treemap display of used disk space
</p></li><li class="listitem"><p>
Files kept apart from directories in separate <Files> items to prevent
cluttering the display
</p></li><li class="listitem"><p>
All numbers displayed human readable - e.g., 34.4 MB instead of 36116381 Bytes
</p></li><li class="listitem"><p>
Reasonable handling of sparse files - only blocks that are actually allocated
are added up to the total sums.
</p></li><li class="listitem"><p>
Reasonable handling of (regular) files with multiple hard links - their size is
divided by their number of hard links, thus evenly distributing their size over
the directories they are linked to -- and, more importantly, not adding the same
file up several times.
</p></li><li class="listitem"><p>
Different colors in the directory tree display to keep the different tree
levels visually apart
</p></li><li class="listitem"><p>
Display of latest change time within an entire directory tree - you can easily
see what object was changed last and when.
</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm65"></a>Directory Reading</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Stays on one file system by default - reads mounted file systems only on
request.
</p><p>
You don't care about a mounted /usr file system if the root file
system is full and you need to find out why in a hurry, nor do you want to scan
everybody's home directory on the NFS server when your local disk is full.
</p></li><li class="listitem"><p>
Network transparency: Scan FTP or Samba directories - or whatever else
protocols KDE support.
</p></li><li class="listitem"><p>
PacMan animation while directories are being read.
OK, this is not exactly essential, but it's fun.
</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm75"></a>Cleaning up</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Predefined cleanup actions: Easily delete a file or a directory tree, move it
to the KDE trash bin, compress it to a .tar.bz2 archive or simply open a shell
or a Konqueror window there.
</p></li><li class="listitem"><p>
User-defined cleanup actions: Add your own cleanup commands or edit the
existing ones.
</p></li><li class="listitem"><p>
"Send mail to owner" report facility: Send a mail requesting the owner
of a large directory tree to please clean up unused files.
</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm84"></a>Misc</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Feedback mail facility: Rate the program and tell the authors your opinion
about it.
</p></li></ul></div></div></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="overview.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="more-screen-shots.html">Next</a></td></tr><tr><td class="prevCell">Overview </td><td class="upCell">Overview</td><td class="nextCell"> More Sceen Shots</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="more-screen-shots.html"><html><head><title>More Sceen Shots</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="overview.html" title="Chapter 1. Overview"><link rel="prev" href="features.html" title="Features"><link rel="next" href="basic_usage.html" title="Chapter 2. Basic Usage"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> More Sceen Shots</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="features.html">Prev</a></td><td class="upCell">Overview</td><td class="nextCell"><a accesskey="n" href="basic_usage.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="more-screen-shots"></a>More Sceen Shots</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm91"></a>Configuring cleanup actions</h3></div></div></div><p>
</p><div class="screenshot"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><img src="kdirstat-config-cleanups.png" alt="Configure cleanup actions window screenshot"></div></div><p>
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm101"></a>Configuring tree colors</h3></div></div></div><p>
</p><div class="screenshot"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><img src="kdirstat-config-tree-colors.png" alt="Configure tree colors window screenshot"></div></div><p>
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm111"></a>Feedback mail</h3></div></div></div><p>
</p><div class="screenshot"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><img src="feedback-mail.png" alt="Feedback mail window screenshot"></div></div><p>
</p></div></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="features.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="basic_usage.html">Next</a></td></tr><tr><td class="prevCell">Features </td><td class="upCell">Overview</td><td class="nextCell"> Basic Usage</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="index.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="features.html">Next</a></td></tr><tr><td class="prevCell">The KDirStat Handbook </td><td class="upCell"> </td><td class="nextCell"> Features</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="basic_usage.html"><html><head><title>Chapter 2. Basic Usage</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="more-screen-shots.html" title="More Sceen Shots"><link rel="next" href="select_dir.html" title="Select a Directory"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Basic Usage</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="more-screen-shots.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="select_dir.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="basic_usage"></a>Chapter 2. Basic Usage</h1></div></div></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="invoking"></a>Invoke <span class="application">KDirStat</span></h2></div></div></div><p>
Start <span class="application">KDirStat</span> from the KDE menu, right-click a directory in a
Konqueror window or type
<strong class="userinput"><code>kdirstat</code></strong> or
<strong class="userinput"><code>kdirstat <directory-name></code></strong> in a shell
window or at KDE's <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Run command</span></span> prompt
(<span class="keycap"><strong>Alt-F2</strong></span>).
</p></div><FILENAME filename="select_dir.html"><html><head><title>Select a Directory</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="basic_usage.html" title="Chapter 2. Basic Usage"><link rel="prev" href="basic_usage.html" title="Chapter 2. Basic Usage"><link rel="next" href="find_out_where.html" title="Find out what Uses up all the Disk Space"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Select a Directory</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="basic_usage.html">Prev</a></td><td class="upCell">Basic Usage</td><td class="nextCell"><a accesskey="n" href="find_out_where.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="select_dir"></a>Select a Directory</h2></div></div></div><p>
<span class="application">KDirStat</span> will prompt for a directory if you didn't specify one when starting
it. You can specify local directories as well as URLs of remote locations -
<strong class="userinput"><code>kdirstat /usr/lib</code></strong> works as well as
<strong class="userinput"><code>kdirstat ftp:/ftp.myserver.org/pub</code></strong>.
</p><p>
In any case, <span class="application">KDirStat</span> will start reading that directory. That might take a
while, but you can work with the program during all that time.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="basic_usage.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="find_out_where.html">Next</a></td></tr><tr><td class="prevCell">Basic Usage </td><td class="upCell">Basic Usage</td><td class="nextCell"> Find out what Uses up all the Disk Space</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="find_out_where.html"><html><head><title>Find out what Uses up all the Disk Space</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="basic_usage.html" title="Chapter 2. Basic Usage"><link rel="prev" href="select_dir.html" title="Select a Directory"><link rel="next" href="do_something.html" title="Do Something about it"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Find out what Uses up all the Disk Space</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="select_dir.html">Prev</a></td><td class="upCell">Basic Usage</td><td class="nextCell"><a accesskey="n" href="do_something.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="find_out_where"></a>Find out what Uses up all the Disk Space</h2></div></div></div><p>
Look at the "Subtree Total" column or wait until a subtree is finished reading
and look at the graphical percentage bar display to find out what directory
subtee takes up how much disk space. Use the open / close icons (plus and minus
signs or small arrows, depending on how you set up your KDE) or double-click an
item to open or close it.
</p><p>
Notice how files at any directory level are kept apart from subdirectories -
there is a separate <Files> entry for them. This way, you can easily tell
how much disk space the files are using up in relation to the subdirectories
and their respective files.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="select_dir.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="do_something.html">Next</a></td></tr><tr><td class="prevCell">Select a Directory </td><td class="upCell">Basic Usage</td><td class="nextCell"> Do Something about it</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="do_something.html"><html><head><title>Do Something about it</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="basic_usage.html" title="Chapter 2. Basic Usage"><link rel="prev" href="find_out_where.html" title="Find out what Uses up all the Disk Space"><link rel="next" href="treemaps.html" title="Chapter 3. Treemaps"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Do Something about it</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="find_out_where.html">Prev</a></td><td class="upCell">Basic Usage</td><td class="nextCell"><a accesskey="n" href="treemaps.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="do_something"></a>Do Something about it</h2></div></div></div><p>
Once you found out where all your disk space goes, do something about it - this
is probably why you are using this program in the first place. You have several
options:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Go to a computer hardware store and buy a new hard disk.
This is probably not what you want. ;-)
</p></li><li class="listitem"><p>Tell the owner of that file or directory to please clean up.
You can use <span class="application">KDirStat</span> for that: Mark that file or directory (i.e., left-click
on it) and select <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Send Mail to Owner</span></span>
from the context menu (right-click), from the tool bar (the envelope icon) or
from the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Report</span></span> menu.
</p><p>
A precomposed message will open in your
<a class="link" href="faq.html#mail_client" title="8.6.">favourite mail client</a>.
You can edit that text before actually sending it. The recipient of
the mail is the user who owns the file or directory you marked - but of course
you can edit that, too in the mail client.
</p><p>
The mail will contain those items that are currently displayed open from the
marked item on. If you want to include more items, open the respective
directories; if you want less, close them. Of course you can always delete
lines in the mail client if you find them irrelevant - there is no use
complaining about some 367 byte files along with others that take several
megabytes.
</p></li><li class="listitem"><p>
Invoke a "cleanup" action. There are several predefined ones, and you can
define your own. Use the context menu, the tool bar or the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Clean
Up</span></span> menu to find out which are available.
</p><p>
For some cleanup actions you will have to wait until the directory
tree is completely read until you can activate them. If a cleanup action
doesn't get enabled even then, the type of item you selected is inappropriate
for that kind of action: Some actions can only performed on directories, while
others can only be performed on files. Only very few actions work for
<Files> pseudo entries since they don't have a real counterpart in the
file system.
</p></li></ul></div></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="find_out_where.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="treemaps.html">Next</a></td></tr><tr><td class="prevCell">Find out what Uses up all the Disk Space </td><td class="upCell">Basic Usage</td><td class="nextCell"> Treemaps</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="more-screen-shots.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="select_dir.html">Next</a></td></tr><tr><td class="prevCell">More Sceen Shots </td><td class="upCell"> </td><td class="nextCell"> Select a Directory</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="treemaps.html"><html><head><title>Chapter 3. Treemaps</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="do_something.html" title="Do Something about it"><link rel="next" href="treemap_actions.html" title="Treemap Related Actions"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Treemaps</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="do_something.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="treemap_actions.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="treemaps"></a>Chapter 3. Treemaps</h1></div></div></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="treemap_intro"></a>Quick Introduction to Treemaps</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="what_are_treemaps"></a>What is it?</h3></div></div></div><p>
The shaded rectangles you can see in the lower half of the <span class="application">KDirStat</span> main
window are called a "treemap". This is just another way of displaying items in
a tree that each have a numerical value, such as a file size.
</p><p>
Each rectangle corresponds to a file or directory on your hard disk. The larger
the rectangle (or, rather, the larger its area), the larger the file.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="how_to_use_treemaps"></a>How to Use Treemaps</h3></div></div></div><p>
Look at the largest rectangles. Click on one, and it is selected - both in
the treemap view and above in the tree view (the list above). You can now see
what file or directory that is - both in the tree view above and in the status
line below.
</p><p>
Find the largest rectangles, identify them, ant decide what to do with them:
Keep them, delete them, whatever. Use the cleanup actions like in the tree
view. The right mouse button opens a context menu that contains cleanup actions.
</p><p>
The shading gives hints about which files belong together in directories. The
bright spots indicate about where the center of parent directories is.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="treemap_advantages"></a>Pros and Cons of Treemaps</h3></div></div></div><p>
Treemaps are good for finding single large files, possibly very deeply nested
in the directory hierarchy. They don't help very much if lots of small files
clutter up a directory - use the tree view (the list) above the treemap for
that.
</p><p>
The treemap by itself view doesn't give away very much information other than
relative file sizes. It can tell you where large files are, even if they are
very deeply hidden in subdirectories. You always see all files at once, not
only the relative sizes of subdirectories against each other like in the tree
view. Click on a file to see more details in the tree view above.
</p><p>
Bottom line: Both the treemap and the tree view have their strenghs and
weaknesses. Use a combination of both to make best use of either's benefits.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="getting_rid_of_treemaps"></a>How to Get Rid of it</h3></div></div></div><p>
If you need the screen space for the tree view (the list) or if you find it
takes too long to update the tree view each time you delete a file, you can
drag the splitter between the tree view and the treemap all the way down. The
treemap doesn't get rebuilt below a certain minimum size, thus it doesn't eat
performance any more. Alternatively, uncheck "show treemap" in the "treemap"
menu or simply hit <span class="keycap"><strong>F9</strong></span>.
</p></div></div><FILENAME filename="treemap_actions.html"><html><head><title>Treemap Related Actions</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="treemaps.html" title="Chapter 3. Treemaps"><link rel="prev" href="treemaps.html" title="Chapter 3. Treemaps"><link rel="next" href="treemap_in_depth.html" title="More Information about Treemaps"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Treemap Related Actions</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="treemaps.html">Prev</a></td><td class="upCell">Treemaps</td><td class="nextCell"><a accesskey="n" href="treemap_in_depth.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="treemap_actions"></a>Treemap Related Actions</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="treemap_mouse_actions"></a>Mouse Actions in the Treemap</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
A single click with the left mouse button selects the clicked file or directory
both in the treemap and in the tree view.
</p></li><li class="listitem"><p>
A single click with the middle mouse button selects the parent of the clicked
file or directory.
</p></li><li class="listitem"><p>
A single click with the right mouse button opens the context menu.
</p></li><li class="listitem"><p>
A double click with the left mouse button zooms the treemap in at the clicked
file or directory: The treemap is redisplayed with the near-topmost ancestor of
the clicked file or directory as the root.
</p></li><li class="listitem"><p>
A double click with the middle mouse button zooms out after zooming in.
</p><p>
If the treemap is not zoomed in at all, it is simply rebuilt to fit into the
available screen space without the need for scrollbars. This is mainly useful
if automatic treemap resizing (the default) is switched off.
</p></li><li class="listitem"><p>
Dragging the splitter above the treemap not only resizes the treemap subwindow,
it also rebuilds the treemap and makes it fit into the available space.
</p></li><li class="listitem"><p>
You can drag the splitter all the way down to deactivate the treemap
alltogether. Below a minimum size the treemap will not be updated any more, so
it doesn't cost any performance.
</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="treemap_menu_actions"></a>Treemap Menu Actions</h3></div></div></div><p>
Most treemap mouse actions have counterparts in the "treemap" menu.
</p><p>
In addition to that, "show treemap" in the "treemap" menu toggles display of
the treemap subwindow. If disabled, the treemap is really inactive and doesn't
cost any performance.
</p></div></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="treemaps.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="treemap_in_depth.html">Next</a></td></tr><tr><td class="prevCell">Treemaps </td><td class="upCell">Treemaps</td><td class="nextCell"> More Information about Treemaps</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="treemap_in_depth.html"><html><head><title>More Information about Treemaps</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="treemaps.html" title="Chapter 3. Treemaps"><link rel="prev" href="treemap_actions.html" title="Treemap Related Actions"><link rel="next" href="predefined_cleanups.html" title="Chapter 4. Predefined Cleanup Actions"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> More Information about Treemaps</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="treemap_actions.html">Prev</a></td><td class="upCell">Treemaps</td><td class="nextCell"><a accesskey="n" href="predefined_cleanups.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="treemap_in_depth"></a>More Information about Treemaps</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="simple_treemap_construction"></a>How a Simple Treemap is Constructed</h3></div></div></div><p>
In its most basic form, construction of a treemap is very easy:
</p><p>
First, you need a tree where each node has an associated value. Directory trees
with their accumulated file sizes are a very natural example. However, the tree
needs to be complete with all accumulated values before anything can be done -
that's why <span class="application">KDirStat</span> doesn't display a treemap while directories are being
read.
</p><p>
Decide upon an direcion in which to split the available area initially. Since
normally the treemap subwindow is wider than it is high, we first split
horizontally.
</p><p>
Split the area so each toplevel directory gets an area proportional to its
accumulated size (i.e., its own size plus the size of all its children,
grandchildren etc.).
</p><p>
For each rectangle thus constructed, repeat the process for each directory
level, but change direction for each level. For example, the second level will
be split vertically, the third again horizontally etc.
</p><p>
This basic algorithm as well as the idea of treemaps at all was introduced by
Ben Shneiderman quite some years ago.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="squarified_treemaps"></a>Squarified Treemaps</h3></div></div></div><p>
One major drawback of the simple treemap algorithm is that it usually results
in lots of very thin, elongated rectangles that are hard to point at with the
mouse and hard to compare visually against each other. This is why <span class="application">KDirStat</span>
uses "squarified" treemaps as described by Mark Bruls, Kees Huizing, and Jarke
J. van Wijk of the Technical University of Eindhoven in the Netherlands. The
basic idea is to improve the aspect ratio of the resulting rectangles, thus to
make them more "square-like". Even though this doesn't always work out
perfectly, it usually improves things a lot: There are normally very few (if
any) thin, elongated rectangles in such a squarified treemap.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="cushioned_treemaps"></a>The Shading: Cushioned Treemaps</h3></div></div></div><p>
Squarifying a treemap comes at a cost: It makes the structure of the underlying
tree even less obvious for the user. Where simple treemaps change direction for
each level of subdivision, sqarified treemaps change direction within each
level. The result are clusters of more or less square-like rectangles. The only
hint about the tree structure that is given is that larger rectangles are near
the left and at the top of each level.
</p><p>
Thus, <span class="application">KDirStat</span> uses a technique described by Jarke J. van Wijk and Huub van
de Wetering of the TU Eindhoven, NL: "Cushioned" treemaps. This is the 3D-like
shading you can see in <span class="application">KDirStat</span>'s treemaps: It gives each rectangle within
the treemap (each "tile") a cushion-like impression. This is not just for
pretty looks, its main purpose is to group files optically together.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="treemaps_optimizations"></a><span class="application">KDirStat</span>'s own Treemap Improvements</h3></div></div></div><p>
The squarification algorithm requires items to be sorted by size. A Linux/Unix
directory tree, however, usually has lots of items; a full-blown Linux
installation can easily consist of 150,000+ (!) files and directories. The best
sort algorithms (heap sort, quick sort) still have a cost in the order of
n*ln(n), i.e. they are proportional to the product of the number of items times
their logarithm.
</p><p>
Likewise, the cushion shading algorithm requires relatively expensive
floating-point arithmetics for each individual pixel of each treemap tile (even
though, by the way, it is very efficient for a 3D-shading algorithm - no
expensive sinus/cosinus etc. calculation required).
</p><p>
On the other hand, most items in large directory trees are so tiny they cannot
be seen at all. <span class="application">KDirStat</span> simply omits everything that will result in treemap
tiles less than a predefined (3*3 pixels) size - they are pretty useless for
the purposes of <span class="application">KDirStat</span>'s users anyway. Those tiny thingies may end up in
some featureless grey space in the treemap display.
</p><p>
So don't wonder if you click on some grey pixels and <span class="application">KDirStat</span> insists they
belong to a rather high-level directory: <span class="application">KDirStat</span> simply means to tell you
that those pixels correspond to some small stuff in that directory. Use the
tree view (the list) above the treemap for more detailed information.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="treemaps_credits"></a>Credits and Further Reading about Treemaps</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
SequoiaView gave the inspiration for treemaps within <span class="application">KDirStat</span>. SequoiaView is
a MS Windows (that's the bad part) program created at the TU Eindhoven, NL. It
introduced cushion treemaps and later squarified cushion treemaps. Its purpose
is very close to <span class="application">KDirStat</span>'s. If you are looking for a <span class="application">KDirStat</span>-like program
on that "other" ;-) platform, go for SequoiaView:
<a class="ulink" href="http://www.win.tue.nl/sequoiaview" target="_top">
http://www.win.tue.nl/sequoiaview
</a>.
</p><p>
Needless to say, <span class="application">KDirStat</span> users should easily be able to simply mount their
MS Windows partitions and use <span class="application">KDirStat</span> to clean up those as well. The only
acceptable excuse ;-) for not doing this might be NTFS partitions (no reliable
write access from Linux to those yet) or single-OS MS Windows machines.
</p></li><li class="listitem"><p>
Ben Shneiderman invented treemaps - a truly intuitive way of visualizing
numerical contents of a tree. For more information, see
<a class="ulink" href="http://www.cs.umd.edu/hcil/treemaps/" target="_top">
http://www.cs.umd.edu/hcil/treemaps/
</a>.
</p></li><li class="listitem"><p>
Jarke J. van Wijk and Huub van de Wetering from the TU Eindhoven, NL wrote a
paper called "Cushion Treemaps: Visualization of Hierarchical Information". It
is available in PDF format at
<a class="ulink" href="http://www.win.tue.nl/~vanwijk/" target="_top">
http://www.win.tue.nl/~vanwijk/
</a>.
</p></li><li class="listitem"><p>
Mark Bruls, Kees Huizing and Jarke J. van Wijk from the TU Eindhoven wrote a
paper called "Squarified Treemaps". It is also available in PDF format at
<a class="ulink" href="http://www.win.tue.nl/~vanwijk/" target="_top">
http://www.win.tue.nl/~vanwijk/
</a>.
</p></li><li class="listitem"><p>
Alexander Rawass had written a previous implementation of treemaps for
<span class="application">KDirStat</span>. Even that part has been completely replaced for various reasons
(performance, integration into the <span class="application">KDirStat</span> main application, memory
consumption, stability, user interface conformance, lack of maintenance), it
had proven that treemaps are a useful addition for a program like <span class="application">KDirStat</span>.
</p></li><li class="listitem"><p>
Frederic Vernier and Laurence Nigay from the University of Grenoble, France
wrote a paper called "Modifiable Treemaps Containing Variable-Shaped Units"
(URL unknown, sorry). They also wrote a MS Windows programm called "parent"
that uses a mixture of treemaps and file lists within individual treemap
tiles.
</p><p>
Personally, I don't like that approach very much - I find that display very
cluttered and confusing (that is why I didn't adopt anything like that for
<span class="application">KDirStat</span>). But this is just my personal opinion that others may or may not
share.
</p></li></ul></div></div></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="treemap_actions.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="predefined_cleanups.html">Next</a></td></tr><tr><td class="prevCell">Treemap Related Actions </td><td class="upCell">Treemaps</td><td class="nextCell"> Predefined Cleanup Actions</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="do_something.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="treemap_actions.html">Next</a></td></tr><tr><td class="prevCell">Do Something about it </td><td class="upCell"> </td><td class="nextCell"> Treemap Related Actions</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="predefined_cleanups.html"><html><head><title>Chapter 4. Predefined Cleanup Actions</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="treemap_in_depth.html" title="More Information about Treemaps"><link rel="next" href="cleanup_open_in_terminal.html" title="Open in Terminal"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Predefined Cleanup Actions</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="treemap_in_depth.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="cleanup_open_in_terminal.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="predefined_cleanups"></a>Chapter 4. Predefined Cleanup Actions</h1></div></div></div><p>
<span class="application">KDirStat</span> comes with a number of predefined cleanup actions. You can configure
them all to your personal preference, and you can add your own. Here is what
the predefined cleanup actions do:
</p><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cleanup_open_in_konqueror"></a>Open in Konqueror</h2></div></div></div><p>
This opens the selected item in a Konqueror window.
</p><p>
You can use Konqueror to delete it (but then, you can also do that more easily
from within <span class="application">KDirStat</span>), you can move it to another place or you can examine it
more closely.
</p><p>
If the selected item is a known MIME type, this will open the appropriate
application. For example, if you invoke
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Open in Konqueror</span></span> on a PNG image, Konqueror will
immediately start an image viewer and display that image.
</p><p>
This is the Swiss army knife of cleanup actions: You can do a lot of different
things with it. Thus, <span class="application">KDirStat</span> cannot know if and when it makes sense to
re-read that directory - you will have to do that manually:
Select <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh selected</span></span> from the context menu
(right-click) or from the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">File</span></span> menu.
</p></div><FILENAME filename="cleanup_open_in_terminal.html"><html><head><title>Open in Terminal</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="predefined_cleanups.html" title="Chapter 4. Predefined Cleanup Actions"><link rel="prev" href="predefined_cleanups.html" title="Chapter 4. Predefined Cleanup Actions"><link rel="next" href="cleanup_compress.html" title="Compress"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Open in Terminal</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="predefined_cleanups.html">Prev</a></td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"><a accesskey="n" href="cleanup_compress.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cleanup_open_in_terminal"></a>Open in Terminal</h2></div></div></div><p>
This opens a terminal window in the directory of the selected item.
</p><p>
Use this to issue a few shell commands in that directory, then simply close
that shell window. You can easily open a new one in a different directory if
you need one, so you might want not to bother to repeatedly type
<strong class="userinput"><code>cd</code></strong> with lenghty paths - simply close that shell and open
a new one at the new location (type <span class="keycap"><strong>Ctrl</strong></span>-<span class="keysym">T</span>.
</p><p>
As with the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Open in Konqueror</span></span> cleanup action described
above, you must manually re-read the directory's contents if you make
changes. Otherwise they will not be reflected in <span class="application">KDirStat</span>'s display.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="predefined_cleanups.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="cleanup_compress.html">Next</a></td></tr><tr><td class="prevCell">Predefined Cleanup Actions </td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"> Compress</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="cleanup_compress.html"><html><head><title>Compress</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="predefined_cleanups.html" title="Chapter 4. Predefined Cleanup Actions"><link rel="prev" href="cleanup_open_in_terminal.html" title="Open in Terminal"><link rel="next" href="cleanup_make_clean.html" title="make clean"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Compress</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_open_in_terminal.html">Prev</a></td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"><a accesskey="n" href="cleanup_make_clean.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cleanup_compress"></a>Compress</h2></div></div></div><p>
This compresses the selected directory to a .tar.bz2 archive.
</p><p>
For example, a subdirectory
<strong class="userinput"><code>/work/home/kilroy/loveletters</code></strong> will become a compressed
archive <strong class="userinput"><code>/work/home/kilroy/loveletters.tar.bz2</code></strong>.
The directory is removed once the compressed archive is successfully created
(but of course not if that failed).
</p><p>
Any existing archive of the same name will silently be overwritten.
</p><p>
Remember that Konqueror and related utilities can use that kind of archive
transparently; there is no need to unpack it if you want to read a file in that
archive. Simply click into the archive in Konqueror.
</p><p>
If you prefer .tgz archives to .tar.bz2, change the command line in the
<a class="link" href="configuring_cleanups.html" title="Chapter 5. Configuring Cleanup Actions">cleanup settings</a>. With .tar.bz2,
this is
</p><p>
<strong class="userinput"><code>
cd ..; tar cjvf %n.tar.bz2 %n && rm -rf %n
</code></strong>
</p><p>
For .tgz archives, change this to
</p><p>
<strong class="userinput"><code>
cd ..; tar czvf %n.tgz %n && rm -rf %n
</code></strong>
</p><p>
But you might think twice before doing that: "bzip2" (for .tar.bz2) compresses
a lot more efficient than ordinary "gzip" (for .tgz or .tar.gz), and most
systems support that just as well. It's just a matter of getting used to typing
<strong class="userinput"><code>tar cjvf</code></strong> rather than <strong class="userinput"><code>tar czvf</code></strong> for
creating an archive or <strong class="userinput"><code>tar xjvf</code></strong> rather than <strong class="userinput"><code>tar
xzvf</code></strong> for unpacking it.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_open_in_terminal.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="cleanup_make_clean.html">Next</a></td></tr><tr><td class="prevCell">Open in Terminal </td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"> make clean</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="cleanup_make_clean.html"><html><head><title>make clean</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="predefined_cleanups.html" title="Chapter 4. Predefined Cleanup Actions"><link rel="prev" href="cleanup_compress.html" title="Compress"><link rel="next" href="cleanup_clean_trash.html" title="Delete Trash Files"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> make clean</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_compress.html">Prev</a></td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"><a accesskey="n" href="cleanup_clean_trash.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cleanup_make_clean"></a>make clean</h2></div></div></div><p>
This issues a <strong class="userinput"><code>make clean</code></strong> command in the selected
directory.
</p><p>
This is useful if you build software from source frequently. After successfully
installing the software (<strong class="userinput"><code>make install</code></strong>), there is no
need to keep the built binaries around in the source directory any longer. On
the other hand, people frequently forget to clean up those directories, so you
can do that from within <span class="application">KDirStat</span> with a few mouse clicks.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_compress.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="cleanup_clean_trash.html">Next</a></td></tr><tr><td class="prevCell">Compress </td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"> Delete Trash Files</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="cleanup_clean_trash.html"><html><head><title>Delete Trash Files</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="predefined_cleanups.html" title="Chapter 4. Predefined Cleanup Actions"><link rel="prev" href="cleanup_make_clean.html" title="make clean"><link rel="next" href="cleanup_delete_to_trash_bin.html" title="Delete (to Trash Bin)"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Delete Trash Files</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_make_clean.html">Prev</a></td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"><a accesskey="n" href="cleanup_delete_to_trash_bin.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cleanup_clean_trash"></a>Delete Trash Files</h2></div></div></div><p>
This deletes files that are usually superfluous, such as editor backup files or
core dumps in the selected directory and in any of its subdirectories.
</p><p>
By default, the following types of files are deleted:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Object files left over from compiling software: *.o</p></li><li class="listitem"><p>Editor backup files: *~ *.bak *.auto</p></li><li class="listitem"><p>Core dump files: core</p></li></ul></div><p>
Of course, you can <a class="link" href="configuring_cleanups.html" title="Chapter 5. Configuring Cleanup Actions">configure this</a>
to suit your personal preferences.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_make_clean.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="cleanup_delete_to_trash_bin.html">Next</a></td></tr><tr><td class="prevCell">make clean </td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"> Delete (to Trash Bin)</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="cleanup_delete_to_trash_bin.html"><html><head><title>Delete (to Trash Bin)</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="predefined_cleanups.html" title="Chapter 4. Predefined Cleanup Actions"><link rel="prev" href="cleanup_clean_trash.html" title="Delete Trash Files"><link rel="next" href="cleanup_hard_delete.html" title="Delete (no way to undelete!)"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Delete (to Trash Bin)</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_clean_trash.html">Prev</a></td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"><a accesskey="n" href="cleanup_hard_delete.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cleanup_delete_to_trash_bin"></a>Delete (to Trash Bin)</h2></div></div></div><p>
This invokes the KDE standard "delete" operation, i.e. the selected file or
directory is moved to the KDE trash bin.
</p><p>
Even though this doesn't help to reclaim disk space right away, it is a safe
method of deleting. Use this action for anything you want to get rid of and
then review your actions by looking into the KDE trash bin. If you are really
sure, select <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Empty Trash Bin</span></span> there. Until that point,
you can always move those items back to where they came from.
</p><p>
You might consider not using this cleanup action if you are cleaning up a
directory on a different file system than your home directory: In that case
that "moving to trash" involves copying the items (and then deleting them at
the original location) which might take a while.
</p><p>
Notice that when moving an item to trash is not successful, <span class="application">KDirStat</span> will
still falsely display that item as deleted even though it's still there. Use
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh selected</span></span> from the context menu to update the
display manually. Read <a class="link" href="configuring_cleanups.html#assume_deleted">here</a> why.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_clean_trash.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="cleanup_hard_delete.html">Next</a></td></tr><tr><td class="prevCell">Delete Trash Files </td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"> Delete (no way to undelete!)</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="cleanup_hard_delete.html"><html><head><title>Delete (no way to undelete!)</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="predefined_cleanups.html" title="Chapter 4. Predefined Cleanup Actions"><link rel="prev" href="cleanup_delete_to_trash_bin.html" title="Delete (to Trash Bin)"><link rel="next" href="configuring_cleanups.html" title="Chapter 5. Configuring Cleanup Actions"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Delete (no way to undelete!)</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_delete_to_trash_bin.html">Prev</a></td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"><a accesskey="n" href="configuring_cleanups.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="cleanup_hard_delete"></a>Delete (no way to undelete!)</h2></div></div></div><p>
This is a real delete, not simply moving something to the trash bin. It's
quicker, and disk space is reclaimed immediately, but there is no way to
recover if you made a mistake. You will be prompted for confirmation when you
invoke this.
</p><p>
You can <a class="link" href="configuring_cleanups.html#confirmation">change the configuration to not prompt for
confirmation</a>, but don't blame me if anything goes wrong after you did that.
</p><p>
As with <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Delete (to Trash Bin)</span></span>, you will need to manually
re-read a directory if this went wrong (usually due to insufficient permissions)
- <span class="application">KDirStat</span>'s display is out of sync with the hard disk if that happens.
Read <a class="link" href="configuring_cleanups.html#assume_deleted">here</a> why.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_delete_to_trash_bin.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="configuring_cleanups.html">Next</a></td></tr><tr><td class="prevCell">Delete (to Trash Bin) </td><td class="upCell">Predefined Cleanup Actions</td><td class="nextCell"> Configuring Cleanup Actions</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="treemap_in_depth.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="cleanup_open_in_terminal.html">Next</a></td></tr><tr><td class="prevCell">More Information about Treemaps </td><td class="upCell"> </td><td class="nextCell"> Open in Terminal</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="configuring_cleanups.html"><html><head><title>Chapter 5. Configuring Cleanup Actions</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="cleanup_hard_delete.html" title="Delete (no way to undelete!)"><link rel="next" href="config_cleanups_example.html" title="Examples"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Configuring Cleanup Actions</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_hard_delete.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="config_cleanups_example.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="configuring_cleanups"></a>Chapter 5. Configuring Cleanup Actions</h1></div></div></div><p>
Select <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Configure <span class="application">KDirStat</span>...</span></span> from the
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Settings</span></span> menu and switch to the
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Cleanups</span></span> page:
</p><p>
</p><div class="screenshot"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><img src="kdirstat-config-cleanups.png" alt="Configure cleanup actions window screenshot"></div></div><p>
</p><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="config_cleanups_reference"></a>Reference</h2></div></div></div><p>
Select the cleanup action you want to configure from the list at the left
side. You might need to check <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Enabled</span></span> before you can
make any changes.
</p><p>
Enter a title in the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Title</span></span> field. You should mark one of
the characters in the title with an ampersand ('&') to provide a keyboard
shortcut in the menus.
</p><p>
Enter a shell command in the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Command line</span></span> field. The
command will be invoked with <strong class="userinput"><code>/bin/sh</code></strong>, so you can use
everything the default shell provides - including pipelines, logical 'and' or
'or' ('&&' or '||', respectively) or multiple commands separated by
semicolons. Use '%p' for the full path (or URL) of the currently selected file
or directory or '%n' for the name without path. '%t' will be expanded to the
full path name of the KDE trash directory (usually ${HOME}/Desktop/Trash, but
since this tends to change between different KDE versions it is safer to use
'%t').
</p><p>
<span class="application">KDirStat</span>
will always change directory to the selected item, so there is no need to
manually add a <strong class="userinput"><code>cd</code></strong> command to the command line.
</p><p>
Commands are started in the background if possible, so don't add an extra
ampersand '&'.
</p><p>
Check <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Recurse into subdirectories</span></span> if the command should
be called for each subdirectory of the selected directory. Whether or not this
is useful depends on the kind of command you entered: A <strong class="userinput"><code>make
clean</code></strong> command usually takes care of that internally, while it's a
lot easier to use <strong class="userinput"><code>rm -f *.bak</code></strong> and let <span class="application">KDirStat</span> handle
subdirectories rather than using a more complex <strong class="userinput"><code>find ... | xargs
...</code></strong> command.
</p><p><a name="confirmation"></a>
Check <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Ask for confirmation</span></span> if you want to prompt the
user for confirmation every time he invokes that cleanup action (but not for
each recursive subdirectory!). But beware: Having to confirm a lot of such
prompts tends to make users unattentive. They begin to blindly confirm
everything out of habit. Thus, use confirmations only when really necessary.
</p><p>
Check the category of objects this cleanup action works for. Not all commands
make sense for both files and directories. <Files> pseudo entries are a
very special case: They don't have a real counterpart on the hard disk. You can
safely check the <Files> category for actions that require changing
directory to somewhere and then execute a command there, but there is no use
trying to delete such a <Files> entry.
</p><p>
Choose between <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">On local machine only ('file:/' protocol)</span></span>
and <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Network transparent (ftp, smb, tar, ...)</span></span>.
Most commands run locally only. There are only a few exceptions: For example,
you can open a remote location in many KDE applications, e.g., Konqueror.
</p><p>
Select a <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh Policy</span></span> to tell <span class="application">KDirStat</span> how to update
its display after the cleanup action has been invoked:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">No refresh</span></span>: Don't refresh the display. Either the
cleanup action doesn't change the directory tree anyway or it is unknown when
or how - or you don't care.
</p><p>
Cleanup actions with this refresh policy are the only ones that can be invoked
while the respective directory subtree is being read. All others can only be
started once reading is finished.
</p></li><li class="listitem"><p>
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh this entry</span></span>: Refresh the directory branch the
cleanup action was selected with. This is the most useful refresh policy for
cleanup actions that delete a number of items from a directory tree, for
example <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Delete Trash Files</span></span>.
</p><p>
If this refresh policy is selected, the command is not started in the
background: <span class="application">KDirStat</span> has to wait for it to finish so the directory display
can be refreshed at the proper time.
</p></li><li class="listitem"><p>
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh this entry's parent</span></span>: Similar to
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh this entry</span></span>, but one level higher up. Useful for
cleanup actions that delete the selected item but create a new one on the same
level, for example the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Compress</span></span> standard cleanup: The
original directory is deleted, but a .tar.bz2 file is created instead.
</p><p>
If this refresh policy is selected, the command is not started in the
background: <span class="application">KDirStat</span> has to wait for it to finish so the directory display
can be refreshed at the proper time.
</p></li><li class="listitem"><p><a name="assume_deleted"></a>
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Asume entry has been deleted</span></span>: Don't really re-read
anything from disk, but assume the cleanup action deletes the selected
item, thus simply remove that item from the directory tree's representation in
<span class="application">KDirStat</span>'s internal data structures.
</p><p>
This is much faster than any real refresh, but it might cause the internal data
structures to get out of sync with the hard disk if the cleanup action fails and
doesn't really delete the selected item. In this case, the user will have to
manually re-read that directory branch.
</p></li></ul></div></div><FILENAME filename="config_cleanups_example.html"><html><head><title>Examples</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="configuring_cleanups.html" title="Chapter 5. Configuring Cleanup Actions"><link rel="prev" href="configuring_cleanups.html" title="Chapter 5. Configuring Cleanup Actions"><link rel="next" href="feedback_mail.html" title="Chapter 6. Feedback Mail"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Examples</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="configuring_cleanups.html">Prev</a></td><td class="upCell">Configuring Cleanup Actions</td><td class="nextCell"><a accesskey="n" href="feedback_mail.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="config_cleanups_example"></a>Examples</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm423"></a>Open in Emacs</h3></div></div></div><p>
This is a trivial example that shows you how to add a new cleanup action that
opens a file in Emacs (or any other editor of your choice).
</p><p>
Select one of the unused user-defined cleanup actions from the list. Make sure
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Enabled</span></span> is checked.
</p><p>
Enter <strong class="userinput"><code>Open in &Emacs</code></strong> in the
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Title</span></span> field. Notice the '&': This marks the letter
'E' as this cleanup action's keyboard shortcut.
</p><p>
Enter <strong class="userinput"><code>emacs %p</code></strong> in the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Command
line</span></span> field.
</p><p>
Leave both <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Recurse into subdirectories</span></span> and
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Ask for confirmation</span></span> unchecked.
</p><p>
Make sure only <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Files</span></span> is checked in the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Works
for...</span></span> section and <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Directories</span></span> and
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton"><Files> pseudo entries</span></span> are unchecked. If you like
Emacs' "dired" mode very much, you can also leave
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Directories</span></span> checked, but it definitely doesn't make any
sense trying to open an editor with a <Files> entry.
</p><p>
Leave <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">On local machine only</span></span> selected. If you feel like
experimenting a lot, you can try setting up Emacs so it fetches files from
remote locations, but even then most likely only the 'ftp' protocol will work.
</p><p>
Leave the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh Policy</span></span> at
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">No refresh</span></span>. This ensures Emacs is started
in the background and you can continue working with <span class="application">KDirStat</span> while Emacs
runs. It wouldn't make too much sense to change the command line to
<strong class="userinput"><code>emacs %p &</code></strong> and change the refresh policy to, say,
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh this entry</span></span>: The refresh would take place
immediately after Emacs starts, and this is probably not what you want.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idm451"></a>Compress</h3></div></div></div><p>
This example explains the predefined <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Compress</span></span> cleanup
action in more detail. Remember, this cleanup action makes a compressed
.tar.bz2 archive from a directory.
</p><p>
The <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Command line</span></span> for this cleanup action is:
</p><p>
<strong class="userinput"><code>
cd ..; tar cjvf %n.tar.bz2 %n && rm -rf %n
</code></strong>
</p><p>
<strong class="userinput"><code>cd ..</code></strong> changes directory one level up. We don't
want to do something in the selected directory, but one level higher.
</p><p>
The semicolon <strong class="userinput"><code>;</code></strong> tells the shell to execute one more
command - unconditionally, no matter if the previous command succeeded or
failed.
</p><p>
<strong class="userinput"><code>tar cjvf %n.tar.bz2 %n &&</code></strong>
is where the compressed .tar.bz2 archive is created. "c" is the tar command for
"create", "j" means "use bzip2 compression", "v" is "verbose" (even though this
is strictly spoken unnecessary here), "f" means use the next argument as the
target file name rather than some default tape device (which nowadays nobody
uses any more anyway). "%n.tar.bz2" will be expanded to the name of the
selected directory without path plus "tar.bz2", "%n" will be expanded to
the name without anything else. For a directory
<strong class="userinput"><code>/usr/lib/something</code></strong> all this will result in a command
</p><p>
<strong class="userinput"><code>tar cjvf something.tar.bz2 something</code></strong>
</p><p>
<strong class="userinput"><code>&&</code></strong> makes the shell execute the rest only if the
previous command (the <strong class="userinput"><code>tar</code></strong> command) is executed
successfully. This is used here to make sure the directory only is deleted if
we really have a .tar.bz2 archive with the same contents so we can easily
restore it when necessary. This is crucial in case there insufficient disk
space to create the archive or should we have insufficient permissions to
create the archive.
</p><p>
<strong class="userinput"><code>rm -rf %n</code></strong> recursively deletes the directory
without asking or complaining.
</p><p>
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Works for...</span></span> is enabled for directories only. Note it
wouldn't be a good idea to enable it for <Files> entries, too: The user
would rightfully expect the .tar.bz2 archive to contain the contents of the
<Files> entry only, i.e. only the files on that directory level. The
command would, however, pack the entire directory tree from the parent level on
into the .tar.bz2 file.
</p><p>
The <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh Policy</span></span> is set to
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Refresh this entry's parent</span></span> since not only the selected
item is changed, but its parent also: It loses one child (the directory) but
gets another one (the .tar.bz2 archive).
</p><p>
Please note that <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Recurse into subdirectories</span></span> is not
checked here: the <strong class="userinput"><code>tar</code></strong> command and <strong class="userinput"><code>rm
-rf</code></strong> take care of any subdirectories.
</p></div></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="configuring_cleanups.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="feedback_mail.html">Next</a></td></tr><tr><td class="prevCell">Configuring Cleanup Actions </td><td class="upCell">Configuring Cleanup Actions</td><td class="nextCell"> Feedback Mail</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="cleanup_hard_delete.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="config_cleanups_example.html">Next</a></td></tr><tr><td class="prevCell">Delete (no way to undelete!) </td><td class="upCell"> </td><td class="nextCell"> Examples</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="feedback_mail.html"><html><head><title>Chapter 6. Feedback Mail</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="config_cleanups_example.html" title="Examples"><link rel="next" href="privacy.html" title="Privacy"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Feedback Mail</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="config_cleanups_example.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="privacy.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="feedback_mail"></a>Chapter 6. Feedback Mail</h1></div></div></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="feedback_mail_description"></a>Description</h2></div></div></div><p>
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Send Feedback Mail...</span></span> from the
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Help</span></span> menu opens this dialog:
</p><p>
</p><div class="screenshot"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><img src="feedback-mail.png" alt="Feedback mail window screenshot"></div></div><p>
</p><p>
You answer the questions (at least those marked as required) and add your personal
comments (in English, if you can, or in the special case of <span class="application">KDirStat</span>
alternatively in German).
</p><p>
Upon clicking on the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Mail this...</span></span> button, your
<a class="link" href="faq.html#mail_client" title="8.6.">mail client</a> opens with a
<a class="link" href="mail_example.html" title="Feedback Mail Example">precomposed mail</a>.
You can review that mail to make sure it doesn't contain anything you
don't like. When you are convinced the mail is okay and doesn't contain
anything you don't like, send it.
</p><p>
With your opinion and your personal comments, you can make a contribution to
the Open Source movement - even if you are not a developer, even if you don't
have a clue how to improve or change the software. Your opinion is important,
even if you decide you don't like the program and send the mail off with "this
program is crap" checked.
</p><p>
Open Source softare lives and breathes with user feedback. If you miss a
feature, tell us about it. If you consider an existing feature confusing, tell
us about it. If you find an application overloaded with features so you can't
find the ones you really need, tell us about it.
</p><p>
On the other hand, if you like the program the way it is and you wouldn't like
to see it changed in any way, tell us about that, too. If you simply want to
thank those who go through the trouble writing all that software, do it. Your
input is appreciated, be it positive or negative.
</p><p>
There is nothing more frustrating for an Open Source software author than that
lingering uncertainty if there is anybody out there who actually uses his
program. He may not get any response from users - does that mean nobody
uses the software, or does it mean it simply runs so good nobody has reason to
complain? You can contribute by telling him he is doing all right and he should
keep up the good work.
</p><p>
In the opposite case, why not tell the author of a particular annoying program
just how annoying it is? This may shake him sober and make him reconsider his
work.
</p><p>
Open Source is one of the world's greatest democracies. Make your vote!
</p></div><FILENAME filename="privacy.html"><html><head><title>Privacy</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="feedback_mail.html" title="Chapter 6. Feedback Mail"><link rel="prev" href="feedback_mail.html" title="Chapter 6. Feedback Mail"><link rel="next" href="mail_example.html" title="Feedback Mail Example"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Privacy</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="feedback_mail.html">Prev</a></td><td class="upCell">Feedback Mail</td><td class="nextCell"><a accesskey="n" href="mail_example.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="privacy"></a>Privacy</h2></div></div></div><p>
Your mail sent with <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Send Feedback Mail...</span></span> is sent to the
authors of this program, to nobody else. No company or government institution
will get your mail address or any personal data. You might have noticed no
personal data are requested in the feedback form. In particular, you will never
receive spam e-mail of any kind because of sending feedback mail.
</p><p>
We, the authors of this program, loathe spam probably even more than the
average KDE user since we get so much of it - spam robots tend to extract
e-mail addresses from source code and from web pages, so you can be sure we do
our best to make life as hard as we can on the spammers and certainly not help
them in any way.
</p><p>
The purpose of all this feedback mail is to gather information about average
user satisfaction, about average opinions about an application's feature set,
an application's stability and learning curve. It's all about averages, thus no
specific user's data will ever be made available to the public - only
statistical averages over a large number of users, if at all.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="feedback_mail.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="mail_example.html">Next</a></td></tr><tr><td class="prevCell">Feedback Mail </td><td class="upCell">Feedback Mail</td><td class="nextCell"> Feedback Mail Example</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="mail_example.html"><html><head><title>Feedback Mail Example</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="feedback_mail.html" title="Chapter 6. Feedback Mail"><link rel="prev" href="privacy.html" title="Privacy"><link rel="next" href="developers_guide.html" title="Chapter 7. Developer's Guide to KDirStat"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Feedback Mail Example</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="privacy.html">Prev</a></td><td class="upCell">Feedback Mail</td><td class="nextCell"><a accesskey="n" href="developers_guide.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mail_example"></a>Feedback Mail Example</h2></div></div></div><p>
A typical feedback mail looks about like that:
</p><p>
</p><pre class="screen" width="60">
<strong class="userinput"><code>[kde-feedback] KDirStat-2.4.4 user feedback</code></strong>
<strong class="userinput"><code><comment></code></strong>
<strong class="userinput"><code>This is where the personal comments go.</code></strong>
<strong class="userinput"><code>You may enter virtually any number of lines.</code></strong>
<strong class="userinput"><code></comment></code></strong>
<strong class="userinput"><code>general_opinion="5/8_nice_try"</code></strong>
<strong class="userinput"><code>features_liked="stay_on_one_filesys"</code></strong>
<strong class="userinput"><code>features_liked="feedback"</code></strong>
<strong class="userinput"><code>features_liked="pacman"</code></strong>
<strong class="userinput"><code>stability="5/5_keeps_crashing"</code></strong>
<strong class="userinput"><code>learning_curve="5/5_still_no_clue"</code></strong>
<strong class="userinput"><code>recommend="yes"</code></strong>
</pre><p>
</p><p>
Notice it's all plain ASCII. There is no attachment, no hidden header fields,
no information about your machine or yourself - only what you would send to
anybody else when you send a mail.
</p><p>
By the way, this is also why we kept the format that simple. Many developers
today prefer XML for all kinds of data, but the end user (you) should be able
to read and understand what you send - just so you can make sure you don't send
any information you'd rather keep to yourself.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="privacy.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="developers_guide.html">Next</a></td></tr><tr><td class="prevCell">Privacy </td><td class="upCell">Feedback Mail</td><td class="nextCell"> Developer's Guide to KDirStat</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="config_cleanups_example.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="privacy.html">Next</a></td></tr><tr><td class="prevCell">Examples </td><td class="upCell"> </td><td class="nextCell"> Privacy</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="developers_guide.html"><html><head><title>Chapter 7. Developer's Guide to KDirStat</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="mail_example.html" title="Feedback Mail Example"><link rel="next" href="faq.html" title="Chapter 8. Questions and Answers"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Developer's Guide to KDirStat</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="mail_example.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="faq.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="developers_guide"></a>Chapter 7. Developer's Guide to KDirStat</h1></div></div></div><p>
Most of what you can see of <span class="application">KDirStat</span> is one separate KDE widget that can be
used in other applications, too. Those parts of <span class="application">KDirStat</span> are even licensed
under the LGPL, so you are even allowed to use it in commercial applications.
</p><p>
The <span class="application">KDirStat</span> sources are extensively documented. Read the documentation in
the header files for more details or use "kdoc" to generate HTML documentation
from them.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="mail_example.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="faq.html">Next</a></td></tr><tr><td class="prevCell">Feedback Mail Example </td><td class="upCell"> </td><td class="nextCell"> Questions and Answers</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="faq.html"><html><head><title>Chapter 8. Questions and Answers</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="developers_guide.html" title="Chapter 7. Developer's Guide to KDirStat"><link rel="next" href="credits.html" title="Chapter 9. Credits and License"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Questions and Answers</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="developers_guide.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="credits.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="faq"></a>Chapter 8. Questions and Answers</h1></div></div></div><div class="qandaset"><a name="faqlist"></a><dl><dt>8.1. <a href="faq.html#ftp_server">
Can I use KDirStat to sum up a directory on an FTP server?
</a></dt><dt>8.2. <a href="faq.html#exact_byte_size">
How do I get the exact byte size of an entry rather than Megabytes or
Kilobytes?
</a></dt><dt>8.3. <a href="faq.html#du_reports_different_total">
Why does the "du" command sometimes report different
sizes than KDirStat?
</a></dt><dt>8.4. <a href="faq.html#sparse_files">
What does this display mean:
6.3 MB (allocated: 1.3 MB)
</a></dt><dt>8.5. <a href="faq.html#hard_links">
What does this display mean:
878.5 KB / 21 Links
</a></dt><dt>8.6. <a href="faq.html#mail_client">
I don't want to use KMail every time I send a mail with KDirStat.
How do I tell KDirStat to use a different mail client?
</a></dt><dt>8.7. <a href="faq.html#tree_colors">
How do I get rid of those many percentage bar colors? I want them all displayed
in the same color.
</a></dt></dl><table border="0" style="width: 100%;"><colgroup><col align="left" width="1%"><col></colgroup><tbody><tr class="question"><td align="left" valign="top"><a name="ftp_server"></a><a name="idm545"></a><p><b>8.1.</b></p></td><td align="left" valign="top"><p>
Can I use <span class="application">KDirStat</span> to sum up a directory on an FTP server?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
Yes. Simply specify the URL at the command line or even in <span class="application">KDirStat</span>'s
directory selection box:
<strong class="userinput"><code>kdirstat ftp:/ftp.myserver.org/pub</code></strong> (command line) or
<strong class="userinput"><code>ftp:/ftp.myserver.org/pub</code></strong> (directory selection box).
</p><p>
<span class="application">KDirStat</span> supports all protocols that KDE supports. You can even use the "tar"
protocol (does it make any sense to do that? You decide). The only restriction
is that the protocol needs to support the "list directory" service - which not
all protocols do.
</p><p>
If you are unsure about the syntax to use, try it in Konqueror first and look
at Konqueror's URL line. For example, to figure out how to specify a "tar" URL,
click into a "tar" archive in Konqueror and look at the resulting URL to get an
idea of what it looks like.
</p></td></tr><tr class="question"><td align="left" valign="top"><a name="exact_byte_size"></a><a name="idm557"></a><p><b>8.2.</b></p></td><td align="left" valign="top"><p>
How do I get the exact byte size of an entry rather than Megabytes or
Kilobytes?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
Right-click the number in the list.
</p></td></tr><tr class="question"><td align="left" valign="top"><a name="du_reports_different_total"></a><a name="idm562"></a><p><b>8.3.</b></p></td><td align="left" valign="top"><p>
Why does the "du" command sometimes report different
sizes than <span class="application">KDirStat</span>?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
There are different kinds of sizes reported by different kinds of system calls
or KDE services: The byte size and the block size.
</p><p>
The byte size is the exact number of bytes of a file or directory. This is what
<span class="application">KDirStat</span> uses.
</p><p>
The block size is the number of disk blocks allocated by a file or
directory. Most "du" commands use that.
Depending on the type of file system, parts of the last block of a
file or directory may be unused, yet reserved for it anyway. If such a file system
uses 1024 byte blocks, a file will at least need those 1024 bytes, no matter if
it is 1024, 200 or even just one byte large. That depends on the file system type
and sometimes even on how this is set up - i.e., this is highly system
specific.
</p><p>
<span class="application">KDirStat</span> uses the byte size since this the only size that is reliably
returned by all kinds of system calls and KDE services alike. It only really
makes a difference in very pathological situations anyway, for example if you
have subdirectories with a large number of tiny files.
</p></td></tr><tr class="question"><td align="left" valign="top"><a name="sparse_files"></a><a name="idm573"></a><p><b>8.4.</b></p></td><td align="left" valign="top"><p>
What does this display mean:
<strong class="userinput"><code>
6.3 MB (allocated: 1.3 MB)
</code></strong>
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
This is a so-called "sparse file" (also known as "file with holes").
This means that the file really is 6.3 MB large, but only 1.3 MB of that are
actually allocated - the rest are just zeroes.
</p><p>
This is typical for core dumps (memory images of crashed programs written to a
file named <strong class="userinput"><code>core</code></strong> or <strong class="userinput"><code>core.*</code></strong>)
or binary database files: The kernel writes those files in a way so only real
data content is allocated on disk and not the large amount of zeroes.
</p><p>
Technically, a sparse file is created with the regular open() system call to
open the file for writing, then using lseek() to extend the file size beyond
its previous size and then writing at least one byte. The area between the old
and the new file size becomes a "hole" in the file - it is not actually
allocated on the disk. Upon reading this area, a value of zero is returned for
each byte read. When bytes are written to that area, file system blocks are
actually allocated, possibly creating two smaller holes before and after the
area written to.
</p><p>
Please note that most file utilities do not deal graciously with sparse
files. Those that support them at all normally need special command line
arguments. Otherwise they tend to simply reading all bytes (including all the
zeroes from the holes) and writing them to a new location - which of course
means that the resulting file is no longer sparse, but really occupies all the
space its size indicates. This may mean that you can blow up the above 6.3 MB
core dump file from 1.3 MB disk usage (and 5 MB zeroes in holes) to really
6.3 MB disk usage.
</p><p>
GNU file system utilities like
<strong class="userinput"><code>tar</code></strong> and <strong class="userinput"><code>rsync</code></strong> at least support
command line options to prevent that.
GNU <strong class="userinput"><code>cp</code></strong> is a notable exception - it has a heuristic that
seems to work very well.
GUI driven file managers on the other hand tend to simply ignore this - even
the most modern and cool looking ones.
</p><p>
If in doubt, check your favourite file tools. Produce a core dump - they are
normally sparse files. The more memory a program uses, the more likely it is to
have large sections of zeroes in its memory image. Try this (in a shell):
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Enable core dumps - they are usually disabled in most Linux distributions:
</p><p>
<strong class="userinput"><code>ulmit -c 128000</code></strong>
</p><p>
This sets the limit of core dump files to 128000 blocks (512 bytes each), i.e.,
to 64 MB. This should be sufficient.
</p></li><li class="listitem"><p>
Start a program with considerable memory consumption - in the background:
</p><p>
<strong class="userinput"><code>xmms &</code></strong>
</p></li><li class="listitem"><p>
Make the program dump core:
</p><p>
<strong class="userinput"><code>kill -ABRT %xmms</code></strong>
</p><p>
This sends the ABORT signal to this process, terminating it with a core dump.
</p></li><li class="listitem"><p>
Look at the core dump:
</p><p>
<strong class="userinput"><code>kdirstat .</code></strong>
</p><p>
or, for a neutral third-party program (from the Linux coreutils package):
</p><p>
<strong class="userinput"><code>/usr/bin/stat core*</code></strong>
</p><p>
(You need to multiply the "blocks" output with 512 to find out allocated disk space)
</p></li><li class="listitem"><p>
Copy that core dump (e.g. to another directory) and look at it again. You will
be surprised how "heavy" all those zeroes suddenly have become. Try that with
several copy utilities (<strong class="userinput"><code>/bin/cp</code></strong>, file managers of your
choice). Remember to always use the sparse original, not any blown-up copies!
</p><p>
Moving files should always be safe (unless a file manager is really, really
stupid), but copying can easily blow up sparse files to huge assemblies of
meaningless zeroes.
</p></li></ul></div><p>
</p><p>
Agreed, sparse files are rather uncommon these days, so this is usually not a
problem. Just remember <span class="application">KDirStat</span> knows how to deal with them. ;-)
</p><p>
Please note that this special handling is only in effect if <span class="application">KDirStat</span>'s
optimized read methods for local files are used (you can turn this on and off
in the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Settings -> General</span></span> dialog) - KDE's KIO
methods do not return this kind of information.
</p></td></tr><tr class="question"><td align="left" valign="top"><a name="hard_links"></a><a name="idm621"></a><p><b>8.5.</b></p></td><td align="left" valign="top"><p>
What does this display mean:
<strong class="userinput"><code>
878.5 KB / 21 Links
</code></strong>
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
This means that this file has a number of hard links. <span class="application">KDirStat</span> uses only the
respective portion of its size for its statistics - in the above case, 878.5 KB
/ 21 = 41.8 KB. When another link to this file is processed, the next 875.5/21
KB are added to the total - and so on.
</p><p>
The rationale is that is makes no sense to count such a file 21 times with its
full size - this would greatly distort the statistics. For example, look at
<strong class="userinput"><code>/usr/lib/locale</code></strong> on a (SuSE) Linux system - many files
there have multiple hard links to save disk space. The total sum of that
directory on a SuSE Linux 9.2-i386 system is 40.5 MB -- as opposed to 205.6 MB
that the added-up output of <strong class="userinput"><code>/bin/ls -lR</code></strong> would suggest
(or <span class="application">KDirStat</span> with <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">use optimized local read methods</span></span>
turned off in the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Settings -> General</span></span> dialog)
- sometimes, as in this example, this really makes a difference!
</p><p>
Technical background: In Unix/Linux file systems, files primarily have a
numeric ID, their "i-number", the index of the corresponding "i-node", the file
system's administrative information. Each directory entry of a file really is
no more than a link to that i-node. You can have the very same file under
several distinct names this way - even in different directories. The only
limitation is that this is restricted to one file system (i.e. to one disk
partition) because those i-numbers are unique only per file system.
</p><p>
Hard links can also introduce a whole new dimenstion of problems with
applications that create backup copies of working files - they usually only
rename the original file to a backup name and write their content to a new
file. Editors usually work that way. This however means that any additional
hard links to that file now point to the outdated backup copy - which is
normally not what is desired. Only very few applications handle this
reasonably. So the bottom line is: Use hard links only if you know very well
what you are doing.
</p><p>
All this is probably why symbolic links have become so much more popular in recent
years: They can also point to different file systems, even (via NFS) to
different hosts in the network. On the downside, symlinks can also be stale -
pointing into nothingness. This cannot happen with hard links: A file is only
really deleted when the last of its links is deleted (this includes open
i-nodes in memory - i.e., processes still having an open file handle to that
i-node).
</p><p>
Directories rely completely on hard links (this is also why <span class="application">KDirStat</span> does not
attempt to try anything smart with multiple-hard-link directories - it would
make no sense): The ".." entries in each directory pointing to its parent is
nothing else than another hard link to that parent (named ".."), and "." is
nothing else than a hard link to itself. This is also why even a completely
empty directory has a link count of 2 - one for "." in its own directory, one
for its name in its parent directory.
</p><p>
Like sparse files above, regular files with multiple hard links are pretty
uncommon these days - but they are still used, and sometimes they can make a
difference, and this is why <span class="application">KDirStat</span> has special handling for them.
</p><p>
Please note that this special handling is only in effect if <span class="application">KDirStat</span>'s
optimized read methods for local files are used (you can turn this on and off
in the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Settings -> General</span></span> dialog) - KDE's KIO
methods do not return this kind of information.
</p></td></tr><tr class="question"><td align="left" valign="top"><a name="mail_client"></a><a name="idm644"></a><p><b>8.6.</b></p></td><td align="left" valign="top"><p>
I don't want to use KMail every time I send a mail with <span class="application">KDirStat</span>.
How do I tell <span class="application">KDirStat</span> to use a different mail client?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
Start <strong class="userinput"><code>kcontrol</code></strong> or select
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Preferences</span></span> in the KDE menu, then select
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Network</span></span> -> <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Email</span></span> and enter
your favourite mail client in the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Preferred Email client</span></span>
field.
</p></td></tr><tr class="question"><td align="left" valign="top"><a name="tree_colors"></a><a name="idm656"></a><p><b>8.7.</b></p></td><td align="left" valign="top"><p>
How do I get rid of those many percentage bar colors? I want them all displayed
in the same color.
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
Select <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Configure <span class="application">KDirStat</span>...</span></span> from the
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Settings</span></span> menu, switch to the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Tree
colors</span></span> page and drag the slider all the way up.
</p></td></tr></tbody></table></div></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="developers_guide.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="credits.html">Next</a></td></tr><tr><td class="prevCell">Developer's Guide to KDirStat </td><td class="upCell"> </td><td class="nextCell"> Credits and License</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="credits.html"><html><head><title>Chapter 9. Credits and License</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="faq.html" title="Chapter 8. Questions and Answers"><link rel="next" href="installation.html" title="Appendix A. Installation"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Credits and License</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="faq.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="installation.html">Next</a></td></tr></table></div><div id="contentBody"><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="credits"></a>Chapter 9. Credits and License</h1></div></div></div><p>
<span class="application">KDirStat</span>
</p><p>
Program copyright 1999-2002 Stefan Hundhammer <code class="email">(sh AT suse.de)</code>
</p><p>
Contributors:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Alexander Rawawss <code class="email">(alexannika AT users.sourceforge.net)</code>
Initial treemaps (those who currently don't work any more)
</p></li></ul></div><p>
</p><p>
Documentation copyright 2002 Stefan Hundhammer <code class="email">(sh AT suse.de)</code>
</p><p><a name="gnu-fdl"></a>This documentation is licensed under the terms of the <a class="ulink" href="help:/kdoctools5-common/fdl-license.html" target="_top">GNU Free Documentation
License</a>.</p><p>This program is licensed under the terms of the <a class="ulink" href="help:/kdoctools5-common/gpl-license.html" target="_top">GNU General Public License</a>.</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="faq.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="installation.html">Next</a></td></tr><tr><td class="prevCell">Questions and Answers </td><td class="upCell"> </td><td class="nextCell"> Installation</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="installation.html"><html><head><title>Appendix A. Installation</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="index.html" title="The KDirStat Handbook"><link rel="prev" href="credits.html" title="Chapter 9. Credits and License"><link rel="next" href="requirements.html" title="Requirements"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Installation</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="credits.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="requirements.html">Next</a></td></tr></table></div><div id="contentBody"><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="installation"></a>Appendix A. Installation</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="sect1"><a href="installation.html#getting-kdirstat">How to obtain KDirStat</a></span></dt><dt><span class="sect1"><a href="requirements.html">Requirements</a></span></dt><dt><span class="sect1"><a href="compilation.html">Compilation and Installation</a></span></dt></dl></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="getting-kdirstat"></a>How to obtain KDirStat</h2></div></div></div><p>
<span class="application">KDirStat</span> is part of the KDE project
<a class="ulink" href="http://www.kde.org" target="_top">http://www.kde.org</a>.
<span class="application">KDirStat</span> can be found on the <span class="application">KDirStat</span> home page at
<a class="ulink" href="http://kdirstat.sourceforge.net/" target="_top">http://kdirstat.sourceforge.net/</a>
or at the mirror site at
<a class="ulink" href="http://www.suse.de/~sh/kdirstat/" target="_top">http://www.suse.de/~sh/kdirstat/</a>
.</p></div><FILENAME filename="requirements.html"><html><head><title>Requirements</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="installation.html" title="Appendix A. Installation"><link rel="prev" href="installation.html" title="Appendix A. Installation"><link rel="next" href="compilation.html" title="Compilation and Installation"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Requirements</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="installation.html">Prev</a></td><td class="upCell">Installation</td><td class="nextCell"><a accesskey="n" href="compilation.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="requirements"></a>Requirements</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Linux or any other Unix-type operating system.</p><p>As stupid as this sounds: There were quite some people complaining that
they couldn't get <span class="application">KDirStat</span> installed on their Win9x system. Many people seem
to believe that if it has windows, it has to run on MS Windows...
</p></li><li class="listitem"><p>KDE 3.x</p></li></ul></div><p>
All required libraries as well as <span class="application">KDirStat</span> itself can be found on
<a class="ulink" href="http://kdirstat.sourceforge.net/" target="_top">The <span class="application">KDirStat</span> home page</a>.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="installation.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="compilation.html">Next</a></td></tr><tr><td class="prevCell">Installation </td><td class="upCell">Installation</td><td class="nextCell"> Compilation and Installation</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME><FILENAME filename="compilation.html"><html><head><title>Compilation and Installation</title><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/kdoctools5-common/kde-localised.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><meta name="keywords" content="KDE, kdeutils, utilities, file system, disk usage, cleanup"><link rel="home" href="index.html" title="The KDirStat Handbook"><link rel="up" href="installation.html" title="Appendix A. Installation"><link rel="prev" href="requirements.html" title="Requirements"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/kdoctools5-common/top-kde.jpg" width="36" height="34"> Compilation and Installation</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="requirements.html">Prev</a></td><td class="upCell">Installation</td><td class="nextCell"></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="compilation"></a>Compilation and Installation</h2></div></div></div><p>
See file "build-howto.html" in the distribution tarball.
</p></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="requirements.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"></td></tr><tr><td class="prevCell">Requirements </td><td class="upCell">Installation</td><td class="nextCell"> </td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="credits.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Contents</a></td><td class="nextCell"><a accesskey="n" href="requirements.html">Next</a></td></tr><tr><td class="prevCell">Credits and License </td><td class="upCell"> </td><td class="nextCell"> Requirements</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="overview.html">Next</a></td></tr><tr><td class="prevCell"> </td><td class="upCell"> </td><td class="nextCell"> Overview</td></tr></table></div><div id="footer_text">Would you like to make a comment or contribute an update to this page?<br>Send feedback to the <a href="mailto:kde-doc-english@kde.org" class="footer_email">KDE Docs Team</a></div></div></div></body></html></FILENAME>
Generated by dwww version 1.15 on Thu Jun 20 14:26:39 CEST 2024.