[NTG-context] Re: defining macros

2025-01-14 Thread Hans Hagen
macros are – then we should forget about MkLX mode? i meant 'if supported by the engine' but mklx are only named when you define them adnm internalized as #1 ... Did I understand correctly, that bracketed = optional parameters is just a convention, i.e. only the handling of arguments

[NTG-context] Re: defining macros

2025-01-14 Thread Henning Hraban Ramm
-macros, at least tried to…): While I liked \define, it looks like it just doesn’t make sense anymore if I need (\tolerant)\def for anything advanced anyway? You stress how costly named macros are – then we should forget about MkLX mode? Did I understand correctly, that bracketed = optional

[NTG-context] Re: defining macros

2025-01-11 Thread Hans Hagen via ntg-context
the explanation! I guess you meant \tolerant instead of \optional? yes, (i sometimes localy uise that as aliasm, sorry) .. consider that you just past the examn Did you know that we can have #A..#E as well. So 15 parameters instead of 9? I still need to use that more (deep down). That I kne

[NTG-context] Re: defining macros

2025-01-11 Thread Henning Hraban Ramm
nstead of \optional? Did you know that we can have #A..#E as well. So 15 parameters instead of 9? I still need to use that more (deep down). That I knew. At least in mkvi/mklx mode. If I use even 4 params I lose count of them. Don't worry, you don't want to know what I forget. Sure.

Re: [NTG-context] how to setup path of ConTeXtLMTX for MacVim?

2021-12-14 Thread Jan-Erik Hägglöf via ntg-context
ewFile,BufRead *.latex,*.sty,*.dtx,*.ltx,*.bbl setf tex "au BufNewFile,BufRead *.texcall dist#ft#FTtex() and instead adding " ConTeXt au BufNewFile,BufRead *.tex,*.ctx,*.mkii,*.mkiv,*.mkvi,*.mkxl,*.mklx setf context It works for Me who only using context as a ty

Re: [NTG-context] upload

2020-11-23 Thread Otared Kavian
ne 315 > > wiped cache; run mtxrun --generate without problems; but context --make has > this error. > > Do I miss something? > > Thanks > Christian > > Am Mo., 23. Nov. 2020 um 18:56 Uhr schrieb Hans Hagen : > Hi, > > I uploaded a next iteration of lmtx. F

Re: [NTG-context] upload

2020-11-23 Thread Christian Prim
mething? Thanks Christian Am Mo., 23. Nov. 2020 um 18:56 Uhr schrieb Hans Hagen : > Hi, > > I uploaded a next iteration of lmtx. From now on there are dedicated sub > directories for mklx and mpxl, which is an indication that we&#

Re: [NTG-context] upload

2020-11-23 Thread Pablo Rodriguez
On 11/23/20 6:55 PM, Hans Hagen wrote: > Hi, > > I uploaded a next iteration of lmtx. From now on there are dedicated sub > directories for mklx and mpxl, which is an indication that we're on the > way to a full code split. Hi Hans, I’m afraid that there is an error that prev

[NTG-context] upload

2020-11-23 Thread Hans Hagen
Hi, I uploaded a next iteration of lmtx. From now on there are dedicated sub directories for mklx and mpxl, which is an indication that we're on the way to a full code split.

Re: [NTG-context] Official file ending?

2020-02-05 Thread Philipp A.
> Since there are already *.mkxl files in the ConTeXt distribution, I > > think it may make sense to name the LMTX version MkXL. > > > > In any case, MkXL is simpler and clearer that MkIV with LMTX. > mkiv (four) : files that expect mkiv (or lmtx) > mkvi (

Re: [NTG-context] Official file ending?

2020-02-05 Thread Hans Hagen
r that MkIV with LMTX. mkiv (four) : files that expect mkiv (or lmtx) mkvi (six): mkiv (or lmtx) files that pass a filter mkxl (fourty) : files that expect lmtx mklx (sixty) : lmtx files that pass a filter (there are some more, like template files and so) I suppose that latex syntax high