/usr/lib/swi-prolog/dotfiles/dotplrc is in swi-prolog-nox 5.10.4-3ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 | /* $Id$ -*- Prolog -*-
SWI-Prolog personalization file
*/
/* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This is a sample user-initialisation file for SWI-Prolog. If you wish to
customise prolog, make a copy of this file and edit it to your
preferences.
Installation:
Unix/MacOS: ~/.plrc
Windows: <appdata>/pl.ini (see win_folder(appdata, AppData))
More hints on useful things you can put into this file are in the
SWI-Prolog reference manual. Notably look at debugger settings, editor
hooks, file_search_path/2, set_prolog_flag/2 and portray/1.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - */
/********************************
* XPCE *
********************************/
% If we are running XPCE, load the user XPCE stuff if it exists
:- ( current_prolog_flag(xpce, true),
( current_prolog_flag(windows, true)
-> Base = 'xpce.ini'
; Base = '.xpcerc'
),
absolute_file_name(user_profile(Base),
[ file_errors(fail),
access(read)
],
XpceRC)
-> ensure_loaded(XpceRC)
; true
).
/*******************************
* IDE *
*******************************/
% Use this if you want to run the development tools in a separate
% thread. Doing allows you to use the editor, thread monitor and
% other tools while you are running a (long) query from the
% toplevel.
%
% HIGHLY EXPERIMENTAL
% :- set_prolog_flag(xpce_threaded, true).
/*******************************
* EDITOR *
*******************************/
% Define the editor to use. Note that more advanced manipulation
% of this is defined in the SWI-Prolog reference manual, section
% "Listing and Editor Interface"
%
% The value pce_emacs (or built_in) causes the system to use the
% built-in editor PceEmacs if the environment provides for a GUI.
% pce_emacs is the default if XPCE is available.
%
% The second entry defines an arbitrary editor and how to tell
% SWI-Prolog to open a file with it on a specified line-number.
% :- set_prolog_flag(editor, pce_emacs).
% :- set_prolog_flag(editor, pico).
%:- multifile
% prolog_edit:edit_command/2.
%
%prolog_edit:edit_command(pico, '%e +%d "%f"').
%prolog_edit:edit_command(pico, '%e "%f"').
/*******************************
* DEBUGGING *
*******************************/
% If you prefer graphical tracing, add the line below.
% :- (current_prolog_flag(gui, true) -> guitracer ; true).
% Determine how terms are printed by the debugger and toplevel. The
% values here are defaults. max_depth(10) replaces all subterms at
% a greater depth with elipses (...). See write_term/3 for further
% explanation and more options.
% :- set_prolog_flag(toplevel_print_options,
% [quoted(true), portray(true), max_depth(10)]).
% :- set_prolog_flag(debugger_print_options,
% [quoted(true), portray(true), max_depth(10)]).
% If you want to suppress printing toplevel query variables
% starting with an `_'
% :- set_prolog_flag(toplevel_print_anon, false).
% If you do not want the tracer to stop at at the exit port.
% :- leash(-exit).
% If you like ?- spy(Class<-Method) to set spy-points for XPCE
% :- op(100, xfx, (<-)).
/*******************************
* MISC SETTINGS *
*******************************/
% If you want to access the command-history like a Unix shell,
% set this to the number of commands to remember. Systems that
% use GNU readline (Unix) can enable saving the history on a
% per-directory bases using the call to prolog_history/1.
% :- set_prolog_flag(history, 50).
% :- prolog_history(enable).
|