On Wed, 27 Dec 2017 19:53:58 +0100, Pablo Rodriguez wrote:
> could you enable issues in your Bitbucket repository?
Issues are enabled now.
Cheers,
Christoph
___
If your question is of interest to others as well, pleas
On Tue, 26 Dec 2017, Pablo Rodriguez wrote:
On 12/21/2017 10:53 PM, Aditya Mahajan wrote:
[...]
Can you post a minimal working example. I don't use XML so it is difficult
for me to understand how these commands are used in practice.
Aditya,
many thanks for your reply and your help.
A minim
On 12/21/2017 10:16 PM, Christoph Reller wrote:
>
> My module does not come in standard context. You have to download it
> from https://bitbucket.org/philexander/context-highlight. If general
> interest is high enough I can ask to
> add it.
Christoph,
could you enable issues in your Bitbucket r
On 12/27/2017 02:14 AM, SteamedFish wrote:
> You can try vim module.
>
> It supports all the formats that vim is able to support and it is a builtin
> module.
Aditya suggested this possibility to me in a previous message in this
thread.
But my sources are XML, so the minimal sample is more comp
You can try vim module.
It supports all the formats that vim is able to support and it is a builtin
module.
\usemodule[t-vim]
\definevimtyping [TEX] [syntax=context]
\definevimtyping [XML] [syntax=xml]
\definevimtyping [LUA] [syntax=lua]
\starttext
\startTEXpage[offset=2em]
a \TEX\ inline
On 12/21/2017 10:53 PM, Aditya Mahajan wrote:
> [...]
> Can you post a minimal working example. I don't use XML so it is difficult
> for me to understand how these commands are used in practice.
Aditya,
many thanks for your reply and your help.
A minimal sample would be:
\startbuffer[demo]
On 12/21/2017 10:16 PM, Christoph Reller wrote:
> On Thu, 21 Dec 2017 21:16:45 +0100, Pablo Rodriguez wrote:
>> [...]
>> It is really a pity that it lacks TeX, since I’m focused on ConTeXt yet
>> (after all, it would be a Spanish introduction to ConTeXt ;-)). XML will
>> come later.
>
> Maybe, if
On Thu, 21 Dec 2017, Pablo Rodriguez wrote:
On 12/21/2017 08:05 PM, Aditya Mahajan wrote:
On Thu, 21 Dec 2017, Pablo Rodriguez wrote:
[...]
I don’t remember which were the options in t-vim, but I need the
options from \setuptyping and \setuptype.
Currently vim does not support these primari
On Thu, 21 Dec 2017 21:16:45 +0100, Pablo Rodriguez wrote:
> On 12/21/2017 05:04 PM, Christoph Reller wrote:
>> Dear Pablo,
>>
>> At least for XML you could use my module highlight-xml:
>>
>> \usemodule[highlight-xml]
>> \definetype[xml][option=xml]
>> [...]
>> Note that even partial XML is highl
On 12/21/2017 08:05 PM, Aditya Mahajan wrote:
> On Thu, 21 Dec 2017, Pablo Rodriguez wrote:
>> [...]
>> I don’t remember which were the options in t-vim, but I need the
>> options from \setuptyping and \setuptype.
>
> Currently vim does not support these primarily because I don't use XML so
> I
On 12/21/2017 05:04 PM, Christoph Reller wrote:
> Dear Pablo,
>
> At least for XML you could use my module highlight-xml:
>
> \usemodule[highlight-xml]
> \definetype[xml][option=xml]
> [...]
> Note that even partial XML is highlighted correctly.
Dear Christoph,
many thanks for your reply.
Your
On 12/20/2017 10:18 PM, Hans Hagen wrote:
> On 12/20/2017 8:45 PM, Pablo Rodriguez wrote:
>> [...]
>> Would it be possible that there are two SnippetComments for all lexers:
>> SnippetCommentMark and SnippetCommentText?
> > very low priority ... there is some logic behind these that i don't want
>
On Thu, 21 Dec 2017, Pablo Rodriguez wrote:
On 12/20/2017 12:20 AM, Aditya Mahajan wrote:
On Tue, 19 Dec 2017, Pablo Rodriguez wrote:
[...]
I checked your t-vim module months ago and I don’t remember which were
the problems, but I had to discard it.
Just try your document with t-vim. It shou
On 12/20/2017 12:20 AM, Aditya Mahajan wrote:
> On Tue, 19 Dec 2017, Pablo Rodriguez wrote:
>> [...]
>> I checked your t-vim module months ago and I don’t remember which were
>> the problems, but I had to discard it.
>
> Just try your document with t-vim. It should be as simple as subsituting
>
>
On Tue, Mon, 18 Dec 2017 23:50:09 +0100, Pablo Rodriguez wrote:
> I have the following sample:
>
> \definetype[context][option=tex]
> \definetype[lua][option=lua]
> \starttext
> \startTEXpage[offset=2em]
>
> a \TEX\ inline comment: \context{ag%befe}
>
> \Lua\ inline comment
On 12/20/2017 8:45 PM, Pablo Rodriguez wrote:
On 12/20/2017 12:53 PM, Hans Hagen wrote:
On 12/18/2017 11:50 PM, Pablo Rodriguez wrote:
[...]
% Differs per lexer:
\definestartstop
[XmlSnippetComment]
[color=,
style=]
I’m afraid that the scite module isn’t an option for me.
On 12/20/2017 12:53 PM, Hans Hagen wrote:
> On 12/18/2017 11:50 PM, Pablo Rodriguez wrote:
>> [...]
> % Differs per lexer:
>
> \definestartstop
> [XmlSnippetComment]
> [color=,
> style=]
>
>> I’m afraid that the scite module isn’t an option for me.
>
> Then you need to configure t
On 12/18/2017 11:50 PM, Pablo Rodriguez wrote:
Hans,
sorry for insisting, but I really need this.
I have the following sample:
\definetype[context][option=tex]
\definetype[lua][option=lua]
\starttext
\startTEXpage[offset=2em]
a \TEX\ inline comment: \context{ag%befe}
On Tue, 19 Dec 2017, Pablo Rodriguez wrote:
On 12/19/2017 08:26 PM, Aditya Mahajan wrote:
On Mon, 18 Dec 2017, Pablo Rodriguez wrote:
[...]
Would it be possible that all comments in type and typing (at least, for
Lua, XML and TeX) would have the same formatting for the whole comment
contents,
On 12/19/2017 08:26 PM, Aditya Mahajan wrote:
> On Mon, 18 Dec 2017, Pablo Rodriguez wrote:
>> [...]
>> Would it be possible that all comments in type and typing (at least, for
>> Lua, XML and TeX) would have the same formatting for the whole comment
>> contents, including the comment signs?
>>
>>
On Mon, 18 Dec 2017, Pablo Rodriguez wrote:
\definetype[context][option=tex]
\definetype[lua][option=lua]
\starttext
\startTEXpage[offset=2em]
a \TEX\ inline comment: \context{ag%befe}
\Lua\ inline comment: \lua{agb --efe}
\startTEX
This is text. % a comment, not \comm
21 matches
Mail list logo