Dear Hans,
Thank you for your new module for math.
If possible, I prefer to use
$ \sqrt(x) = \compute\sqrt[.3N] {2} $
$ \pi = \mathexpr[.40N]{pi}$
It is more direct to use and good to write a text in which we need some math
calculation.
It is another good news for me.
I
> Am 21.05.2021 um 15:15 schrieb Hans Hagen :
>
> I uploaded an lmtx update (only m-mathfun added).
>
> Attached a short description of this (windy stormy friday afternoon) math
> experiment. The question is, what similar features using this trickery come
> to mind.
Thank you!
I can
On Fri, 21 May 2021, Otared Kavian wrote:
> By the way, what does
>
> \complexexpr{123 + new(456,789)}
>
> mean?
Haven't look at the code yet, but I'd guess `new(a,b) = a + bi`.
Aditya
___
If your question
Hi,
It was in fact not really "working", but it just happened that it
looked more or less correct in one case, but not in the other.
For example: The path Pkt[1]--dir(194)*10mm for example is not given
by the two points Pkt[1] and "Pkt[1] shifted 10mm in direction 194
degrees", but Pkt[1] and
I have updated LMTX and indeed seems to be working now
Thanks
Op do 20 mei 2021 om 21:05 schreef Aditya Mahajan :
> On Thu, 20 May 2021, Jeroen wrote:
>
> > I have the following working example with hatching. This works fine, but
> > when I uncomment the sketching commands, no figure is
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
Hi Jairo!
thank you so much, this is precisely what I need.
Still I am wondering why this is not working starting at the Pkt[2] but working
when starting from Pkt[1].
Kind regards
Willi
> On 21 May 2021, at 13:15, Jairo A. del Rio wrote:
>
> Hi!
>
> Do
>
> p[102] :=
On 5/21/2021 5:24 PM, Otared Kavian wrote:
Hi Hans,
Thanks for the new features you have introduced in the module mathfun.
Actually I have been using commands such as the one mentioned by Aditya,
\ctxlua{myfunction(args)}
but for the formatting of the output, that is when one wants only
Hi Hans,
Thanks for the new features you have introduced in the module mathfun.
Actually I have been using commands such as the one mentioned by Aditya,
\ctxlua{myfunction(args)}
but for the formatting of the output, that is when one wants only 3 or four
decimal digits, that approach is
On 5/21/2021 4:37 PM, Aditya Mahajan wrote:
On Fri, 21 May 2021, Hans Hagen wrote:
I uploaded an lmtx update (only m-mathfun added).
Attached a short description of this (windy stormy friday afternoon) math
experiment. The question is, what similar features using this trickery come to
mind.
On Fri, 21 May 2021, Hans Hagen wrote:
> I uploaded an lmtx update (only m-mathfun added).
>
> Attached a short description of this (windy stormy friday afternoon) math
> experiment. The question is, what similar features using this trickery come to
> mind.
Personally, I can see occasionally
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 5/21/2021 00:16, Wolfgang Schuster wrote:
Rik Kabel schrieb am 21.05.2021 um 04:31:
In the following example:
\definelabel[BB][alternative=inright,headcolor=red,text=]
\startTEXpage
Where is the label?\BB
\stopTEXpage
The label is not displayed if a TEXpage is used, but if
On 5/21/2021 00:26, Wolfgang Schuster wrote:
Aditya Mahajan schrieb am 21.05.2021 um 04:47:
On Thu, 20 May 2021, Rik Kabel wrote:
Consider the following example:
\define \HighlightColor {red}
Why not just use:
\definecolor[HighlightColor][red]
and then use color=HighlightColor, etc.
Hi,
I uploaded an lmtx update (only m-mathfun added).
Attached a short description of this (windy stormy friday afternoon)
math experiment. The question is, what similar features using this
trickery come to mind.
Hans
-
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,
On 21/05/2021 14:14, Taco Hoekwater wrote:
It looks like textext.dflt is undefined in the latest lmtx because it is now
renamed to textext.dlft :)
As we say in dutch: een kniesoor die daar op let
;-)
___
If your
the line preventing the output from showing uo seems to be be:
draw textext.dflt("DFLT-" & MonTexte) shifted PB;
If I remove that, I'll get output.
___
If your question is of interest to others as well, please add
Hi,
It looks like textext.dflt is undefined in the latest lmtx because it is now
renamed to textext.dlft :)
> On 21 May 2021, at 14:03, Floris van Manen wrote:
>
> Using the example from the wiki
> https://wiki.contextgarden.net/textext_positioning
>
> then using the latest version of lmtx
>
Using the example from the wiki
https://wiki.contextgarden.net/textext_positioning
then using the latest version of lmtx
$ context --version
mtx-context | ConTeXt Process Management 1.04
mtx-context |
mtx-context | main context file:
Hi!
Do
p[102] := (origin--dir(194)*10mm) shifted Pkt[1];
and
p[103] := (origin--dir(166)*10mm) shifted Pkt[2];
do what you need?
Jairo
El vie, 21 de may. de 2021 a la(s) 05:57, Willi Egger (cont...@boede.nl)
escribió:
> Hello MP Gurus!
>
> I wanted to make a technical drawing. However the
Hello MP Gurus!I wanted to make a technical drawing. However the enclosed mwe does not give me the required results.While the vector from point 1 is directing in the desired direction of 194 degrees, the second vector from point 2 does not as defined point in the direction of 166 degrees.What am I
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
On 2021-05-21, Hans Hagen wrote:
> On 5/21/2021 10:50 AM, Nicola wrote:
>> On 2021-05-20, Hans Hagen wrote:
>>
One thing he asked is what I was asking you: it
would be useful if there were a way to sync in the other direction as
well.
>>> You mean sort of trying to deduce from the
On 5/21/2021 10:50 AM, Nicola wrote:
On 2021-05-20, Hans Hagen wrote:
One thing he asked is what I was asking you: it
would be useful if there were a way to sync in the other direction as
well.
You mean sort of trying to deduce from the synctex file where to go in
the pdf?
Yes. You provide
On 2021-05-20, Hans Hagen wrote:
>> One thing he asked is what I was asking you: it
>> would be useful if there were a way to sync in the other direction as
>> well.
> You mean sort of trying to deduce from the synctex file where to go in
> the pdf?
Yes. You provide a .tex file and a line
26 matches
Mail list logo
