Settings
Settings can be changed from the setup dialog. They are separated into some subdialogs.

General
Size of listviewicons	How big (square) the icons in main list view should be
Show file info	If a small tooltip should appear when moving mouse over an item
Mark item status with icon overlay	When an item isn't in normal subversion state it may get an overlay. (See Meaning of icon overlays)
Items sorting order is case sensitive	If the sort order in main window is case sensitive or not, if a not equal to A.
Display ignored files	Show items marked in subversion for ignore or not.
Maximum log messages in history	How many log messages kdesvn should remember.
Display colored annotate	Use colors defined in the settings dialog for annotations.
Use navigation panel	Toggle the display of the repository tree view.

Subversion and timed jobs settings

Subversion
Start check for updates when open a working copy	When open a working copy start a check for updates in background
Start fill log cache on open	If set kdesvn start (re-)filling the log cache when open a repository or working copy if repository is not assigned local (file://)
Check if items has svn:needs-lock set	Check on working copies if an item has this property set and if yes, displays a special overlayed icon. Setting this may let listings get real slow.
Get file details while remote listing	When checked, kdesvn get more detailed info about file items when making a listing to remote repositories. So you may see remote locks in overview. Be careful: This may let listings REAL slow!
Gain item info recursive	When activated, info on folders will gain information about all items below, may be real slow.
Store passwords for remote connections	Storing passwords is often a security problem. Subversion stores its passwords into a flat file, passwords in the plain text! So be careful setting this flag and see next entry, too. This item only says if saving passwords is the default, you may change it for specific realms inside login dialog.
Store passwords into KDE Wallet	When saving passwords, the plain text file from subversion is a security hole. kdesvn is able saving them into encrypted wallet instead there (starting with version 0.12.0) and use them. On other hand other subversion clients aren't able reading them so you must enter them if using tools like svn command line tool or rapidsvn, too. As long as subversion does not encrypt password storage you should think twice about it.
Use internal password cache	When a password is not stored persistent kdesvn may hold it until kdesvn ends, so you may not need to enter it again for each operation. This cache is never persistent, it will not be saved anywhere.
Log follows node changes	If checked log follows copy operations.
Log always reads list of changed files	The log command may read list of changed files in commit. This is useful and in most cases it cost not real more traffic.
Review items before commit	When doing a commit kdesvn may make a check what to do. For example, if unversioned items are below which may be added, list items changed and current operation will commit. This cost a depending on tree more or less time.
Hide new items in commit box	Should unversioned items displayed in commit dialog or not.
Update modifies instead of conflicts	If set, a local addition at the same path as an incoming addition of the same node kind results in a normal node with a possible local modification, instead of a tree conflict.
Update makes missing parents	If set, create any non-existent parent directories also by checking them out at depth=empty

Timed jobs
Check modified items every N seconds Check for updated items every N seconds	If set check for updates or modified items in working copy when network is enabled on regular base

Diff & Merge
Diff ignores content type 	 Only interesting when diff are made with subversion itself. When set, than subversion diff ignores the content type of entries. Otherwise it will not output diffs from binaries.
Diff in revision tree is recursive 	 When set, diffs made from within revision tree view are made recursive like in all other cases, too. Otherwise only changes belonging to that folder items are shown. How that is made depends on how you let diffs generate (from subversion itself or from external viewers).
Diff ignores white space changes 	 Ignore changes in the amount of white space (option -b to diff)
Diff ignores all white spaces 	 Ignore all white space (option -w to diff)
Prefer external merge program 	 Set if merge with external program is preferred and not Subversion's merge
Use Git diff format 	
Show copies as add 	

Use external diff display
Selects an external application to display diffs. Default is .

External diff display
Defines what kdesvn is using for external display of differences and how it will be called. There are three ways:
<program> <parameter> 	 The difference will generated with subversion and put direct into standard input of the external program (, no temporary files needed)
<program> <parameter> %f 	 The difference will be generated with subversion, saved into a temporary file and the parameter %f will be replaced with that file name. This may be used, for instance, with a simple call to less or text viewer.
<program> <parameter> %1 %2 	 kdesvn let the external program make the difference. %1 and %2 will be replaced with required values (file names or folder names). kdesvn stores content to compare in a temporary environment (when folders does an export, when single file, does a cat) when needed and cleans up after closing external program or closing itself.
Prefer external merge program 	Select if in merge dialog Use external merge should be checked or not as default.

External merge program
Setup the program and options for using when subversion's builtin merge isn't wanted. The default is kdiff3 %s1 %s2 %t. The order of substitution variables isn't important, and them may there more than once, ⪚ like kdiff3 -o %t %s1 %s2 %t. This stuff is only tested with meld and . Think about that external programs mostly do not know anything about subversion ignore parameter so them may show lot more than expected.

Variable substitutions for external merge program
%s1 	 Substituted with source number one.
%s2 	 Substituted with source number two. If this is empty or this is equal to source one and start and end revision is same, this variable will skipped. So be careful setting up command lines like xxdiff --title1 %s1 --title2 %s2 %s1 %s2 %t.
%t 	 Substituted with target.

Conflict resolver program
You may use an external program like for resolving conflicts, the default is kdiff3 %o %m %n -o %t.

Variable substitution for external conflict resolver
In parenthesis after each description is an example how subversion would call the files. These options are designed for , because at this moment this is the only one application supporting all parameters required for a good conflict resolving.
%o or %l 	 Old (local, left) version. This means the lower revision number, the start point of conflicted changes. (foo.cc.r2)
%m or %w 	 Mine (working) version of file, what you had changed against old version. (foo.cc.mine)
%n or %r 	 New (remote, right) version of file. For example, version someone other had made. (foo.cc.r3)
%t 	 Target name, ⪚ the origin name. For (as an example) this would be name after the -o parameter (= output file). (foo.cc)

KIO / command line
Show log after executing a command 	 Should a dialog open with the log of last subversion command when it was executed via command line or action menu.
Minimum log lines to show 	 If Show log... is set, what is the minimum of lines before such a dialog will shown. So you may set that such window will only shown when interesting output was generated (commit log and so on)
Do not display context menu in 	 If set, no action menu entry for kdesvn is made in .
Do not display entries in toplevel action menu 	 If set, kdesvn will not show some extra actions inside Action menu of or .
KIO operations use standard log message 	 When making operations on a repository via the kdesvn KIO protocol from within (, ksvn+... protocols) on large operations like moving or copy folders kdesvn would ask for a log message for each item. This is a behavior of . When this option is set, the KIO implementation from kdesvn will not ask for a log message but set a standard log message. This flag is not for the operations from kdesvn action menu for but only copy/move/mkdir/delete made with or other file managers on a KIO-url.
Standard message 	 The message kdesvn KIO should set on operations from within when the flag above is set. Default is Revision made with kdesvn KIO.
KIO can overwrite 	 If this flag is set, you will have a simple write support for existing items. ⪚ you can open files in your editor and save them direct without checking out them before (kdesvn will do it in background).
Use this only if you are sure what you are doing.
KIO shows progress messages 	 If set KIO shows in KDE's Plasma detailed information about current operation. Error messages of KIO will always displayed and can not be switched off.