<commit_before>================================================================
Logtalk - Open source object-oriented logic programming language
Release 2.36.1

Copyright (c) 1998-2009 <NAME>.        All Rights Reserved.
Logtalk is free software.  You can redistribute it and/or modify
it under the terms of the "Artistic License 2.0" as published by 
The Perl Foundation. Consult the "LICENSE.txt" file for details.
================================================================


The recommended way of installing Logtalk is to use, whenever possible, one 
of the provided installers. This file contains detailed instructions for 
manual installation and configuration of Logtalk. You should also consult 
the "scripts/NOTES.txt" and "integration/NOTES.txt" files for a description 
of a set of shell scripts that might be used for Logtalk installation on 
some operating-systems and for easy Logtalk integration with popular Prolog 
compilers.

Note that the broad compatibility of Logtalk, both with Prolog compilers and 
operating-systems, together with all the possible user scenarios, means that 
installation can vary from very simple by running a couple of scripts to the 
need of patching both Logtalk and Prolog compilers to workaround the lack of 
strong Prolog standards.


1. LOGTALK BASIC INSTALLATION

Installing Logtalk can be as simple as decompressing the downloaded archive 
and copying the resulting directory to a suitable location. This location 
depends on the working environment and on the number of users. The Logtalk 
directory can reside in any user accessible location. Whenever possible, it 
is recommended that Logtalk be installed by a user with administrative rights, 
as described below. This leads to a setup where each Logtalk user may freely 
try and modify the provided examples, library, and configuration files with 
the option of, at any time, restoring the files to its original state by 
simply running one of the provided scripts.


* Installing for a single user with no administrative rights:

In the case of a single user with no administrative rights, the Logtalk 
directory may simply be copied to the user home directory.


* Installing for one or more users by a user with administrative rights:

In the case of installation by a user with administrative rights, the Logtalk 
directory can be copied to any location that its accessible by all the users 
(assuming that copying the Logtalk directory to each user home directory is, 
for some reason, not feasible or desired).

The "scripts" sub-directory contains shell scripts for easy installation of 
Logtalk on POSIX operating systems (see the "scripts/NOTES.txt" file for 
details). Starting from the Logtalk directory, type:

	% cd scripts
	% sudo ./install.sh

This installation script makes all files read-only for non-admin users in 
order to avoid user tempering. This is a convenient setup for computer labs, 
given that making directories world-writable is a security risk.


2. SETTING LOGTALK ENVIRONMENT VARIABLES

You need to set two environment variables, LOGTALKHOME and LOGTALKUSER. The 
environment variable LOGTALKHOME should be set to the Logtalk installation 
directory. The environment variable LOGTALKUSER should point to a directory 
in your home directory where you want to store the user-specific Logtalk files
(by default, "$HOME/logtalk" on POSIX systems and "My Documents\Logtalk" on 
Windows"). Both environment variables may be set for all users by a user with 
administration privileges. The two environment variables can have the same 
value if you are the only Logtalk user on your computer and if you have full 
permissions to the Logtalk installation directory.

>> POSIX systems:

If you use a csh shell, add the following line to your ~/.cshrc file:

	setenv LOGTALKHOME /your/logtalk/installation/directory
	setenv LOGTALKUSER $HOME/logtalk

If you use a bash shell, add the following lines to your ~/.profile file:

	LOGTALKHOME=/your/logtalk/installation/directory
	LOGTALKUSER=$HOME/logtalk

When using the provided shell script for installing Logtalk, a symbolic link 
to the Logtalk installation directory is automatically created. The link is 
named "logtalk". In this case, you may use this symbolic link to define the 
LOGTALKHOME environment variable in order to avoid breaking it when upgrading <commit_msg>Added a note to the Logtalk installation instruction about limitations of some Prolog compilers when handling environment variables. Thanks to <NAME> for the bug report.<commit_after>================================================================
Logtalk - Open source object-oriented logic programming language
Release 2.36.1

Copyright (c) 1998-2009 <NAME>.        All Rights Reserved.
Logtalk is free software.  You can redistribute it and/or modify
it under the terms of the "Artistic License 2.0" as published by 
The Perl Foundation. Consult the "LICENSE.txt" file for details.
================================================================


The recommended way of installing Logtalk is to use, whenever possible, one 
of the provided installers. This file contains detailed instructions for 
manual installation and configuration of Logtalk. You should also consult 
the "scripts/NOTES.txt" and "integration/NOTES.txt" files for a description 
of a set of shell scripts that might be used for Logtalk installation on 
some operating-systems and for easy Logtalk integration with popular Prolog 
compilers.

Note that the broad compatibility of Logtalk, both with Prolog compilers and 
operating-systems, together with all the possible user scenarios, means that 
installation can vary from very simple by running a couple of scripts to the 
need of patching both Logtalk and Prolog compilers to workaround the lack of 
strong Prolog standards.


1. LOGTALK BASIC INSTALLATION

Installing Logtalk can be as simple as decompressing the downloaded archive 
and copying the resulting directory to a suitable location. This location 
depends on the working environment and on the number of users. The Logtalk 
directory can reside in any user accessible location. Whenever possible, it 
is recommended that Logtalk be installed by a user with administrative rights, 
as described below. This leads to a setup where each Logtalk user may freely 
try and modify the provided examples, library, and configuration files with 
the option of, at any time, restoring the files to its original state by 
simply running one of the provided scripts.


* Installing for a single user with no administrative rights:

In the case of a single user with no administrative rights, the Logtalk 
directory may simply be copied to the user home directory.


* Installing for one or more users by a user with administrative rights:

In the case of installation by a user with administrative rights, the Logtalk 
directory can be copied to any location that its accessible by all the users 
(assuming that copying the Logtalk directory to each user home directory is, 
for some reason, not feasible or desired).

The "scripts" sub-directory contains shell scripts for easy installation of 
Logtalk on POSIX operating systems (see the "scripts/NOTES.txt" file for 
details). Starting from the Logtalk directory, type:

	% cd scripts
	% sudo ./install.sh

This installation script makes all files read-only for non-admin users in 
order to avoid user tempering. This is a convenient setup for computer labs, 
given that making directories world-writable is a security risk.


2. SETTING LOGTALK ENVIRONMENT VARIABLES

You need to set two environment variables, LOGTALKHOME and LOGTALKUSER. The 
environment variable LOGTALKHOME should be set to the Logtalk installation 
directory. The environment variable LOGTALKUSER should point to a directory 
in your home directory where you want to store the user-specific Logtalk files
(by default, "$HOME/logtalk" on POSIX systems and "My Documents\Logtalk" on 
Windows"). Both environment variables may be set for all users by a user with 
administration privileges. The two environment variables can have the same 
value if you are the only Logtalk user on your computer and if you have full 
permissions to the Logtalk installation directory.

>> POSIX systems:

If you use a csh shell, add the following line to your ~/.cshrc file:

	setenv LOGTALKHOME /your/logtalk/installation/directory
	setenv LOGTALKUSER $HOME/logtalk

If you use a bash shell, add the following lines to your ~/.profile file:

	LOGTALKHOME=/your/logtalk/installation/directory
	LOGTALKUSER=$HOME/logtalk

Don't use relative paths such as "../" or "./" in the definition of the 
environment variables. Some Prolog compilers don't expand environment 
variables, resulting in "file not found" errors when attempting to use 
the Logtalk integration scripts.

When using the provided shell script for installing Logtalk, a symbolic link 
to the Logtalk installation directory is automatically created. The link is 
named "logtalk". In this case, you may use this symbolic link to define the 
LOGTALKHOME environment variable in order to avoid breaking it when upgrading 
{'fraction_non_alphanumeric': 0.06134969325153374, 'fraction_numerical': 0.0035056967572304996, 'mean_word_length': 4.659640421574705, 'pattern_counts': {'":': 0, '<': 6, '<?xml version=': 0, '>': 10, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4061205', 'n_tokens_mistral': 2267, 'n_tokens_neox': 2134, 'n_words': 1295}