From: Thomas Fehige <thomas@fehige.de>
To: ntg-context@ntg.nl
Subject: ConTeXt and Scite
Date: Mon, 16 May 2016 16:34:20 +0200 [thread overview]
Message-ID: <5739DA6C.10406@fehige.de> (raw)
In-Reply-To: <5738CE2F.2040104@fehige.de>
[-- Attachment #1.1: Type: text/plain, Size: 802 bytes --]
For the time being, I think I'm giving up on pairing ConTeXt standalone
and TeXworks on my Xubuntu machine and try to try out SciTE.
In the manual it says that
If you want to use ConTEXt, you need to copy the relevant files from
<texroot>/tex/texmf-context/context/data/scite
to the path were SciTE keeps its property files (*.properties)
Is that the only way? SciTE seems to keep its user-specific properties
files in my home directory! I don't want to clutter that up with 16
unhidden files and two directories. At least SciTE's original files are
hidden ones.
A much more polite way would be if SciTE used a hidden directory named
"~/.scite", or, better still, "~/.config/scite", to keep its config
stuff in. Can I reconfigure it to use some place like that?
Cheers -- Thomas
[-- Attachment #1.2: Type: text/html, Size: 1124 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-05-16 14:34 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 7:10 uppercase, small caps, numerals and German capital sharp s Thomas Fehige
2016-04-19 12:05 ` Wolfgang Schuster
2016-04-19 12:46 ` Thomas Fehige
2016-04-20 14:03 ` Thomas Fehige
2016-04-20 14:25 ` Wolfgang Schuster
2016-04-20 21:25 ` Thomas Fehige
2016-04-20 21:27 ` Thomas Fehige
2016-04-22 11:35 ` glyph substitution Thomas Fehige
2016-04-22 20:28 ` Hans Hagen
2016-04-25 9:53 ` Thomas Fehige
2016-04-25 12:48 ` Thomas Fehige
2016-04-25 15:49 ` Thomas Fehige
2016-04-25 18:12 ` Thomas Fehige
2016-04-25 20:44 ` Wolfgang Schuster
2016-04-26 8:42 ` Thomas Fehige
2016-04-27 14:27 ` Thomas Fehige
2016-04-27 15:10 ` Hans Hagen
2016-04-29 7:44 ` Thomas Fehige
2016-04-29 7:56 ` Hans Hagen
2016-04-29 8:38 ` Test Suite Fonts "extensions-001" Thomas Fehige
2016-04-29 9:05 ` Wolfgang Schuster
2016-05-03 9:22 ` Setting up TeXworks Thomas Fehige
2016-05-06 8:04 ` Mojca Miklavec
2016-05-06 11:39 ` L.S.-Soc&Gam
2016-05-16 15:46 ` Thomas Fehige
2016-05-16 15:55 ` Jean-Pierre Delange
2016-05-17 11:16 ` Thomas Fehige
2016-05-17 12:39 ` Thomas Fehige
2016-05-17 12:59 ` Hans Hagen
2016-05-19 14:09 ` Thomas Fehige
2016-05-17 13:22 ` Jean-Pierre Delange
2016-05-19 15:16 ` Thomas Fehige
2016-05-19 16:15 ` Jean-Pierre Delange
2016-05-07 10:49 ` Thomas Fehige
2016-05-09 11:02 ` Thomas Fehige
2016-05-15 19:29 ` Thomas Fehige
2016-05-16 14:34 ` Thomas Fehige [this message]
2016-05-03 9:51 ` Thomas Fehige
2016-05-03 10:21 ` Mojca Miklavec
2016-05-03 13:01 ` Thomas Fehige
2016-04-25 20:47 ` glyph substitution Wolfgang Schuster
2016-04-26 7:42 ` Thomas Fehige
-- strict thread matches above, loose matches on Subject: below --
2012-06-19 4:54 ConTeXt and SciTE Bill Meahan
2012-06-19 8:58 ` Hans Hagen
2012-06-19 16:48 ` Bill Meahan
2012-06-19 17:28 ` Hans Hagen
2012-06-19 20:17 ` Bill Meahan
2012-06-19 20:43 ` Hans Hagen
2012-06-19 21:27 ` Bill Meahan
2012-06-19 21:57 ` Hans Hagen
2012-06-20 16:37 ` Bill Meahan
2012-06-20 18:02 ` Hans Hagen
2012-06-20 18:44 ` Hans Hagen
2012-06-20 18:59 ` Bill Meahan
2012-06-20 19:05 ` Bill Meahan
2012-06-20 19:32 ` Hans Hagen
2012-06-20 3:04 ` Bill Meahan
2012-06-20 14:24 ` Hans Hagen
2012-06-20 14:46 ` luigi scarso
2012-06-20 15:24 ` Aditya Mahajan
2012-06-20 16:11 ` Bill Meahan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5739DA6C.10406@fehige.de \
--to=thomas@fehige.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).