ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thomas Floeren <thfl@mac.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: BBEdit Language Module for ConTeXt
Date: Tue, 16 Jun 2015 20:20:53 +0200	[thread overview]
Message-ID: <C942D35C-5C2B-4F47-8F1A-DFEDA5036C6D@mac.com> (raw)
In-Reply-To: <14DDECED-4738-49BD-9A4F-05635824E410@andrew.cmu.edu>


> On 16 Jun 2015, at 15:04, Paul Mazaitis <pm39@andrew.cmu.edu> wrote:
> 
> I've been working on a BBEdit language module to support editing ConTeXt files:
> 
> 	https://github.com/pmazaitis/ConTeXtBBLM
> 
> ...with binary releases here:
> 
> 	https://github.com/pmazaitis/ConTeXtBBLM/releases
> 
> If there are other BBEdit users here with interest, I'd appreciate feedback. Notes on feature gaps (math?), outright bugs, improvements, and/or fiddly details are all welcome.


Hi,

thanks a lot for sharing your module. I was using my own CLM for ConTeXt, but probably I’ll switch to yours now :-)

(I especially love the addition of the "callouts" (TODO, etc.) to the functions/sections menu!)


Some quick observations/suggestions/thoughts:


## Key/value options [] and content arguments {}

The highlighting is broken when there is a space between the command word and the [bracketed options] {or arguments}; unfortunately that’s the way I use to write it ;-)

It breaks also when there are line breaks involved, which is often the case when you write longer, "vertical" definitions, for example

\setupitemgroup [Legtext] [each]
[stopper=,
before={\setupwhitespace[none]\blank[small]},
style=\bf,
inbetween={\blank[small]},
after={\blank[medium]},
width=1.8em, 
…]


## Command words

\,\;\: : In things like "3000\,mm" the whole "\,mm" gets highlighted. [This may ne a legacy problem, as I should better use directly an appropriate Unicode space.]

Highlighting should probably not include chars like "()|": For example in "\starttabulate [|lw(.65\textwidth)|rw(.25\textwidth)|]" the whole "\textwidth)|rw(.25\textwidth)|" part gets command-highlighted.


## Default highlight colors

After installation the default highlight colors were all set to black, except for comments. (BBEdit 11.1.2 (3733).)
(Though this might be as well a BBEdit problem, since they are still fighting highlighting bugs that have been introduced with the color scheme changes of vs. 11)


## Commands / keywords

It’s interesting that you are offering both Command words (via pattern) and Keywords (custom list). In ConTeXt I always thought of them as the same. I’ll surely find a nice use for that :-)


Thanks again,
best,

-- 
Tom







___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2015-06-16 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 13:04 Paul Mazaitis
2015-06-16 18:20 ` Thomas Floeren [this message]

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=C942D35C-5C2B-4F47-8F1A-DFEDA5036C6D@mac.com \
    --to=thfl@mac.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).