search

adityam / filter

ConTeXt module to process contents of a start-stop environment through an external program
45 stars 10 forks source link

css path is inserted wrongly #43

Closed hernot closed 3 years ago

hernot commented 3 years ago

Hi It too me a long time to finally test what we have achieved last year til june on my lecturenotes. What i have figured now is that when adding the css using

\setupexport[ ... , ... ,cssfile=\vimtypingcssfile]

Than the following line is included on my linux system using below mentioned standalone installation of context.

<!-- *-div.html -->
<link type="text/css" rel="stylesheet" href="styles/<prefixpath>/tex/texmf-modules/tex/context/third/vim/vimtyping-default.css" />

<!-- *-div.xhtml -->
<!-- not included and thus missing-->

<!-- *-raw.xml -->
<?xml-stylesheet type="text/css" href="styles/<prefixpath>/tex/texmf-modules/tex/context/third/vim/vimtyping-default.css" ?>

<!-- *-tag.xml -->
<?xml-stylesheet type="text/css" href="styles/<prefixpath>/tex/texmf-modules/tex/context/third/vim/vimtyping-default.css" ?>

I can't tell whether this is the fault of t-filter or t-vim module or a bug in context. The default workarround is to once include using \vimtypingscriptfile to get it copied and than for the next runs replace by cssfile=vimtyping-default.css.

mtx-context     | ConTeXt Process Management 1.04
mtx-context     |
mtx-context     | main context file: <prefixpath>/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context     | current version: 2021.02.14 16:39
mtx-context     | main context file: <prefixpath>/tex/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context     | current version: 2021.02.14 16:39

<prefixpath> ... the base directory path standalone context installation was installed to

ps.: I think i also have found why line numbering and vim-typing does not play well in float environments. I still have to check home with latest context installation and github t-vim sources. keep you posted

adityam commented 3 years ago

Just so that I understand correctly, the desired behavior is to copy the css file to the export/css directory?

hernot commented 3 years ago

Yes. It assumes user copied any file which is listed in cssfile parameter there.

adityam commented 3 years ago

This is an upstream bug. I have reported it to the context mailing list and it should be fixed soon.

adityam commented 3 years ago

This has been fixed upstream (relevant commit: 0d3005).

hernot commented 3 years ago

Ok thanks wait till next standalone release can be grabed via install.sh