>> >> Thanks. I have updated to version 2021.05.23 and run `mtxrun
>> >> --generate`. Syntax highlighting is fine, but with LMTX I'm still
>> >> getting an en-dash. Below, a MWE.
>> >
>> > Can you test if the file tests/vim/21-en-dash.tex works fine at your end:
>> >
>> >
On Thu, 27 May 2021, Nicola wrote:
> On 2021-05-27, Aditya Mahajan wrote:
> > On Thu, 27 May 2021, Nicola wrote:
> >
> >> On 2021-05-24, Aditya Mahajan wrote:
> >> > On Fri, 21 May 2021, Nicola wrote:
> >> >
> >> >> I have only a minor annoyance: I have just noticed that -- is typeset as
> >>
On 2021-05-27, Aditya Mahajan wrote:
> On Thu, 27 May 2021, Nicola wrote:
>
>> On 2021-05-24, Aditya Mahajan wrote:
>> > On Fri, 21 May 2021, Nicola wrote:
>> >
>> >> I have only a minor annoyance: I have just noticed that -- is typeset as
>> >> an en-dash in LMTX (but not in MKIV, as
On Thu, 27 May 2021, Nicola wrote:
> On 2021-05-24, Aditya Mahajan wrote:
> > On Fri, 21 May 2021, Nicola wrote:
> >
> >> I have only a minor annoyance: I have just noticed that -- is typeset as
> >> an en-dash in LMTX (but not in MKIV, as documented). Could you look into
> >> that?
> >
> >
On 2021-05-24, Aditya Mahajan wrote:
> On Fri, 21 May 2021, Nicola wrote:
>
>> I have only a minor annoyance: I have just noticed that -- is typeset as
>> an en-dash in LMTX (but not in MKIV, as documented). Could you look into
>> that?
>
> Fixed in the new release.
Thanks. I have updated to
On Fri, 21 May 2021, Nicola wrote:
> I have only a minor annoyance: I have just noticed that -- is typeset as
> an en-dash in LMTX (but not in MKIV, as documented). Could you look into
> that?
Fixed in the new release.
Aditya
On Sun, 23 May 2021, Hans Hagen wrote:
> On 5/22/2021 6:15 PM, Aditya Mahajan wrote:
> > On Sat, 22 May 2021, Hans Hagen wrote:
> >
> > > On 5/21/2021 9:37 PM, Nicola wrote:
> >
> > > > I have only a minor annoyance: I have just noticed that -- is typeset as
> > > > an en-dash in LMTX (but not
On 5/22/2021 6:15 PM, Aditya Mahajan wrote:
On Sat, 22 May 2021, Hans Hagen wrote:
On 5/21/2021 9:37 PM, Nicola wrote:
I have only a minor annoyance: I have just noticed that -- is typeset as
an en-dash in LMTX (but not in MKIV, as documented). Could you look into
that?
best is that the
On Sat, 22 May 2021, Hans Hagen wrote:
> On 5/21/2021 9:37 PM, Nicola wrote:
> > I have only a minor annoyance: I have just noticed that -- is typeset as
> > an en-dash in LMTX (but not in MKIV, as documented). Could you look into
> > that?
>
> best is that the module uses:
>
>
On 5/21/2021 9:37 PM, Nicola wrote:
On 2021-05-21, Aditya Mahajan wrote:
nvim was 8-10% faster than vim in my tests:
https://adityam.github.io/context-blog/post/vim-vs-neovim/
Interesting, thanks for sharing.
I actually want t-vim (or rather t-filter) to support more
editors/syntax
On 2021-05-21, Aditya Mahajan wrote:
> nvim was 8-10% faster than vim in my tests:
>
> https://adityam.github.io/context-blog/post/vim-vs-neovim/
Interesting, thanks for sharing.
> I actually want t-vim (or rather t-filter) to support more
> editors/syntax highlighters. At some stage I had
On Fri, 21 May 2021, Nicola wrote:
> On 2021-05-21, Nicola wrote:
> > For some reason, the vim module has stopped highlighting code associated
> > to custom filetypes (it still works for built-in filetypes).
>
> I think I have found the culprit. In t-vim.tex, lines 63-88, Vim is
> called with
On 2021-05-21, Nicola wrote:
> For some reason, the vim module has stopped highlighting code associated
> to custom filetypes (it still works for built-in filetypes).
I think I have found the culprit. In t-vim.tex, lines 63-88, Vim is
called with --clean. That option appears *after* -u,
For some reason, the vim module has stopped highlighting code associated
to custom filetypes (it still works for built-in filetypes).
For instance, typeset this:
\usemodule[vim]
\startvimrc[name=foo]
set nocompatible
set runtimepath+=~/foo/
\stopvimrc
14 matches
Mail list logo
