From: Bill Meahan <wmeahan94@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt and SciTE
Date: Wed, 20 Jun 2012 12:11:58 -0400 [thread overview]
Message-ID: <4FE1F64E.9090503@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.02.1206201109590.1798@ybpnyubfg.ybpnyqbznva>
[-- Attachment #1.1: Type: text/plain, Size: 719 bytes --]
On 06/20/2012 11:24, Aditya Mahajan wrote:
> On Wed, 20 Jun 2012, Hans Hagen wrote:
>
>> On 20-6-2012 05:04, Bill Meahan wrote:
>>
>>> Anybody got a ctags file for ConTeXt? :-)
>>
>> what are ctags
>
> They allow you to jump around to specific locations in a file.
>
SciTE also uses them to generate auto-completion/insertion of language
commands so a ctags file for ConTeXt itself would be useful.
--
Bill Meahan, Westland, Michigan USA
“Writing is a combination of intangible
creative fantasy and appallingly
hard work.”
—Anthony Powell
This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 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:[~2012-06-20 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 4:54 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 [this message]
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-20 14:03 ` Thomas Fehige
2016-04-20 14:25 ` Wolfgang Schuster
2016-04-22 11:35 ` glyph substitution Thomas Fehige
2016-04-22 20:28 ` Hans Hagen
2016-04-25 12:48 ` Thomas Fehige
2016-04-25 18:12 ` Thomas Fehige
2016-04-25 20:44 ` Wolfgang Schuster
2016-04-27 14:27 ` Thomas Fehige
2016-04-27 15:10 ` 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-07 10:49 ` Thomas Fehige
2016-05-09 11:02 ` Thomas Fehige
2016-05-15 19:29 ` Thomas Fehige
2016-05-16 14:34 ` ConTeXt and Scite Thomas Fehige
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=4FE1F64E.9090503@gmail.com \
--to=wmeahan94@gmail.com \
--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).