[texworks] windows and mac binaries (r.352)
jfkthame at googlemail.com
Mon Aug 3 19:41:25 CEST 2009
On 3 Aug 2009, at 18:31, Bruno Voisin wrote:
> Le 2 août 09 à 19:04, Jonathan Kew a écrit :
>> A significant change is that the typesetting tool (or "engine")
>> definitions are moved from the main "preferences" file to a
>> separate .ini file in the texworks configuration folder (alongside
>> things like syntax coloring and auto-indent patterns). This should
>> make things easier for distributions that want to provide a custom
>> set of preconfigured tools. For existing users, your tool
>> definitions should be automatically converted to the new .ini file.
> Does this mean there can be two sets of configuration files:
> - One system-wide in /Library/TeXworks on the Mac (and similar
> locations on Windows and Linux I imagine).
> - The other user-specific in ~/Library/TeXworks on the Mac (and ...).
No, there's just one set of configuration files, found in ~/Library/
TeXworks/configuration (alongside the other resource directories such
as templates and completion lists). These are user-specific. Default
files are automatically created here on first run if they're not
already there, but will not replace pre-existing ones.
The exception to this would be if you use a texworks-setup.ini file to
set a new (system-wide) location for the whole texworks resources
directory, including the config files and other resources. In this
case, they would be shared between all users running that particular
copy of the application. This is how you can configure a "portable"
setup that runs entirely from a USB stick, for example, without
installing files onto the local machine.
(Personally, I think this whole "portable mode" thing is quite
confusing, but some people seem to really want it.)
> And if so:
> - Do the completion-rules and typesetting tools etc. in the user-
> specific files add up to or replace those in the system-wide files?
> - What do the typesetting tools entered through the pref window
> modify? The user-specific files (I suppose), or the system-wide ones
> (I suppose not)? Does this mean the system-wide config files have to
> be written in a text editor (as opposed to the pref GUI)?
> Bruno Voisin
More information about the texworks