- ntg-context - Mailing Lists

unwanted page break in contents
by Jeong Dal 26 Aug '18

26 Aug '18

Hi, In the table of contents, there is a unwanted blank space after chapter 2. There is a page break if the remaining space is not enough to cover the list of the next chapter. For example, page break after ch 2. in the following example. Is it possible to list them continuously? Best regards, Dalyoung %%%%%%%% \starttext \definepagebreak[emptyodd][yes,header, footer, odd] \setuphead[chapter][page=emptyodd] \setuphead[title][incrementnumber=list] \setupcombinedlist[content][list={title,chapter,section,subsection}] \setuplist[chapter, title][width=5mm, style=,textcommand={\ss\bf }] \setuplist[section][width=10mm, style=,textcommand={\ss }] \showframe \startfrontmatter \completecontent \page[empty] \stopfrontmatter \startbodymatter \dorecurse{9} {\chapter{Ch \recurselevel} \dorecurse{8} {\section{Section \recurselevel}} } \stopbodymatter \stoptext %%%%%%%%

2 2

Some questions about an extreme table
by Fabrice Couvreur 26 Aug '18

26 Aug '18

Hello, In the table, how to have a. b. c. in each line instead of a. a. a ? Is the macro to place the figures on the baseline of the labels to be improved ? Thanks. Fabrice \useMPlibrary[dum] \switchtobodyfont[pagella,12pt] \unexpanded\def\Item#1{\framed[frame=off,location=hanging]{#1}} \setuplayout [topspace=10mm, header=10mm, footer=10mm, height=middle, backspace=20mm, width=middle] \starttext \startxtable[frame=on,bodyfont=10pt] \startxrow \startxcell[width=2cm] Expression \\ \m{B'(x)} \stopxcell \startxcell \startitemize[packed,a] \startitem \m{B'(x)=-x²+24x-117} \stopitem \stopitemize \stopxcell \startxcell \startitemize[packed,a] \startitem \m{B'(x)=-3x²+48x-117} \stopitem \stopitemize \stopxcell \startxcell \startitemize[packed,a] \startitem \m{B'(x)=-3x²+48x-317} \stopitem \stopitemize \stopxcell \stopxrow \startxrow \startxcell Tableau de \\ signes de \\ \m{B'(x)} \stopxcell \startxcell \startitemize[packed,a] \startitem \Item{{\externalfigure[dummy]}} \stopitem \stopitemize \stopxcell \startxcell \startitemize[packed,a] \startitem \Item{\externalfigure[dummy]} \stopitem \stopitemize \stopxcell \startxcell \startitemize[packed,a] \startitem \Item{\externalfigure[dummy]} \stopitem \stopitemize \stopxcell \stopxrow \startxrow \startxcell Tableau de \\ variations\\de \m{B} \stopxcell \startxcell \startitemize[packed,a] \startitem \Item{\externalfigure[dummy]} \stopitem \stopitemize \stopxcell \startxcell \startitemize[packed,a] \startitem \Item{\externalfigure[dummy]} \stopitem \stopitemize \stopxcell \startxcell \startitemize[packed,a] \startitem \Item{\externalfigure[dummy]} \stopitem \stopitemize \stopxcell \stopxrow \stopxtable \stoptext

3 2

Error running first-setup.bat
by Joseph Canedo 25 Aug '18

25 Aug '18

Hi all, When trying to install latest beta for ConTeXt I get the Following error : sent 55901 bytes received 21842221 bytes 306267.44 bytes/sec total size is 26889592 speedup is 1.23 c:\ConTeXt\test\bin\mtxrun.lua:612: module 'socket.http' not found: no field package.preload['socket.http'] no file 'c:\ConTeXt\test\bin\lua\socket\http.lua' no file 'c:\ConTeXt\test\bin\lua\socket\http\init.lua' no file 'c:\ConTeXt\test\bin\socket\http.lua' no file 'c:\ConTeXt\test\bin\socket\http\init.lua' no file '.\socket\http.lua' no file 'c:\ConTeXt\test\bin\socket\http.dll' no file 'c:\ConTeXt\test\bin\loadall.dll' no file '.\socket\http.dll' no file 'c:\ConTeXt\test\bin\socket.dll' no file 'c:\ConTeXt\test\bin\loadall.dll' no file '.\socket.dll' Command line is (Win10 64 bits): first-setup.bat --modules=all --engine=luatex Many thanks Best regards Joseph

1 0

How to enable Ligatures
by Michael Zhu 24 Aug '18

24 Aug '18

Hi all, Fira Code is Monospaced font with programming ligatures. I don't know how to enable ligatures feature. I hope someone can give me an example. https://github.com/tonsky/FiraCode Michael

3 2

Blocks in margin with overflow of text
by Fabrice Couvreur 22 Aug '18

22 Aug '18

Hello, The idea is to put all the examples of the course in the margin. I see that the text is sometimes overflowing. How to improve the code ? Thanks. Fabrice \definemeasure[Margin][3.5cm] \setuplayout [ backspace=20mm, width=120mm, height=middle, footer=\bodyfontsize, header=3\bodyfontsize, headerdistance=\bodyfontsize, bottom=3\bodyfontsize, location={middle}, margin=\measure{Margin}, rightmargin=4.5cm, marking=on, ] \definefloat [recipe] [figure] \setupfloat [recipe] [default={margin,none}] \defineconversionset [digit] [] [n] \setupenumerations [before={\blank}, after={\blank}, alternative=serried, title=yes, distance=1em, %headcommand=\groupedcommand{}{~---~}, distance=none, prefix=yes, prefixsegments=chapter, way=bychapter, prefixconversionset=digit, titlestyle=bold, width=broad] \defineenumeration [example] [text=Exemple, style=italic] \showframe \starttext \startchapter[title=First chapter] \placerecipe{}{ \startexample \input ward \stopexample} \stopchapter \startchapter[title=Second chapter] \placerecipe{}{ \startexample \input ward \stopexample} \stopchapter \stoptext

1 0

Synctex + Sumatra + TextPad
by Procházka Lukáš Ing. 21 Aug '18

21 Aug '18

Hello, this question extends the "[NTG-context] future versions - synctex" thread. I'm using TextPad for editing Ctx source files, PdfXChange Viewer to view PDFs, both on Windows. After reading some recent posts and after studying some web sources - especially [a] https://www.sumatrapdfreader.org/docs/DDE-Commands.html for SumatraPDF viever and [b] https://tex.stackexchange.com/questions/116981/how-to-configure-texniccente… for inspiration how to make TXC interoperate with Sumatra, I would like to provide "click-in-PDF-go-to-source" functionality - be Sumatra the viewer for this case. Questions are: 1. How to run Sumatra so that it opens a PDF file AND reacts somehow to a mouse click, in order to provide a command to get to the corresponding place in the source file? (IIUC, Sumatra provides such functionality, as e.g. TeXnic Center use it. [b].) I guess that I have to configure Sumatra somehow, or to launch Sumatra with some command line parameters, so that when I click a point in the PDF (maybe while also holding CTRL or something - but it is a detail), a command is launched to open the source file in the editor and go to a particular line. 2. What should be the command line parameters passed to Sumatra to provide the linkage "open PDF-source at line"? I deduce also that such command should call "mtxrun --script synctex" somehow (which will call "...\tex\texmf-context\scripts\context\lua\mtx-synctex.lua") as the "mtx-synctex" is able to read the .synctex produced during compilation of .tex files. I deduce also that "mtx-synctex" calls the editor (which the user uses to edit source files) in the manner that it tells the editor "open file (...) and go to line (...). Existing "mtx-synctex" is "aware" of "scite" editor, which is - next to "console" - the only editor pre-configured. So: 3. What code should be added into "mtx-synctex" in order to make TextPad an editor known to "mtx-synctex"? I found and tried that command e.g. 'C:\Program Files\TextPad 7\system\ddeopn32.exe" TextPad.dde Test.mkiv(40)' successfully opens "Test.mkiv" (being open before) and scrolls to line #40. (TextPad location may vary - depending on version installed - can be e.g.: C:\Program Files\TextPad 7 C:\Program Files (x86)\TextPad 7 C:\Program Files\TextPad 8 ... ) Any idea would be appreciated... Best regards, Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS:nrpt3sn Bezová 1658 147 14 Praha 4 Mob.: +420 702 033 396

2 1

Spurious breaks in export when blank line ends paragraph
by Rik Kabel 21 Aug '18

21 Aug '18

List, My understanding of start/stop macros such as \startparagraph...\stopparagraph has been that blank lines are allowed between the block of text and the macros, as \startparagraph This is the text of the paragraph \stopparagraph However, in xml exports the blank line before \stopparagraph leads to spurious break elements in some circumstances, as shown in the following: \setupbackend [export=yes,xhtml=yes] \starttext \startsection[title=trailing blank line] \startparagraph Xxx xxxxxxxxxxx xx xxxxxxxxx xxxxxx xxx xxxxxxxx xx xxxxxxxxxx xxxxxx. Xxx xxxxxxxx xxxxx, \inleft{z} xxxxx xxxxxxxx xx xxxxxxxxx xx xxxx xxxxxxxxx xx xxxxxxx xxxx xx xxxxx, xxx xxxx xxxxxxxx xx xxx xxxxxxx xxxxxxx xx xxxxxxxx xxx xxxxxxxx xx Xxxxxxxx xxxx, xxx xxxx xxxx xxxxxxxxx xx xxxxxxxx xxxxx xxxxxx xxxx. Xxx xxxxxxxxx xxxxxxx xxx xxx xxxxxxxxxx xx xxxxxxxx xxxx xxxxxxx,xxxxxxxxx xxxxxx x xxxxxx, xxxxxxxx xxx xxxxxxxxxxx xxx xxxxx xxxx. Xxxx xxx xxxxxx xx xxx xxxxxxx xxxx, xxxxxxxx xxxx xxxx xxx xxxxxxxxx xx xxxxx xxxxxxxxx, xxx xxx xxxxx xxx xxxxxxxxxxx xx xxxxxx xxxxxx \inleft{zz}. Xxxxxxxx xxxx xxxxx xx xxxx xxxxxxxx (xxxxx, xxxxxxx, xx xxx xxxxxx). \stopparagraph \stopsection \startsection[title=no blank line] \startparagraph Xxx xxxxxxxxxxx xx xxxxxxxxx xxxxxx xxx xxxxxxxx xx xxxxxxxxxx xxxxxx. Xxx xxxxxxxx xxxxx, \inleft{z} xxxxx xxxxxxxx xx xxxxxxxxx xx xxxx xxxxxxxxx xx xxxxxxx xxxx xx xxxxx, xxx xxxx xxxxxxxx xx xxx xxxxxxx xxxxxxx xx xxxxxxxx xxx xxxxxxxx xx Xxxxxxxx xxxx, xxx xxxx xxxx xxxxxxxxx xx xxxxxxxx xxxxx xxxxxx xxxx. Xxx xxxxxxxxx xxxxxxx xxx xxx xxxxxxxxxx xx xxxxxxxx xxxx xxxxxxx,xxxxxxxxx xxxxxx x xxxxxx, xxxxxxxx xxx xxxxxxxxxxx xxx xxxxx xxxx. Xxxx xxx xxxxxx xx xxx xxxxxxx xxxx, xxxxxxxx xxxx xxxx xxx xxxxxxxxx xx xxxxx xxxxxxxxx, xxx xxx xxxxx xxx xxxxxxxxxxx xx xxxxxx xxxxxx \inleft{zz}. Xxxxxxxx xxxx xxxxx xx xxxx xxxxxxxx (xxxxx, xxxxxxx, xx xxx xxxxxx). \stopparagraph \stopsection \startsection[title=Another section] \startparagraph This is here to show the bottom of the previous section. \stopparagraph \stopsection \stoptext Note that the pdf output does not display the problem, but the pdf output is not why one runs an export. The breaks disappear in shorter paragraphs, and disappear when the margintext is not present, but appear when margintext is present and the paragraph exceeds some length which I have not worked to determine. Is my understanding of the space rules incorrect, or is this a bug? Since some breaks perhaps should be present, it is difficult to remove these with CSS, or XSLT. One thing that might help is to add a class identifier to breaks indicating what lead to their creation. Of course, not generating these would be better still. -- Rik

1 0

scite
by Hans Hagen 21 Aug '18

21 Aug '18

Hi, does anyone know where one can download a scite 3.80 (long term stable) https://sourceforge.net/projects/scintilla/files/scintilla/3.8.0/ or do we need to start compiling it ourselves Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

2 2

future versions
by Hans Hagen 21 Aug '18

21 Aug '18

Hi, Around the upcoming context meeting we expect to release luatex 1.09 (or 1.10 ... yet undecided) which is the prelude to the next year tex live version. It's another step towards a stable version in terms of functionality as we don't expect much more to be added (in fact, I'm wondering if it makes sense to come up with a leaner and meaner version at some point because context can probably benefit from that). Of course under the hood there are improvements possible and we have some ideas (that might materialize at some point) but generally spoken, this is what one gets. That said, a logical question is how about next versions of context. Are there fundamental features missing? Is more needed? Keep in mind that we're not talking of desk top publishing (click and point and place stuff) and also not of word processing (office like stuff) but of mostly automated structured document rendering. Also, keep in mind the landscape that we operate in (context development is mostly user driven as publishers imo long ago lost interest in any research and development and the potential of tex and friends is largely unknown elsewhere). It's not my intention to implement each possible feature as core feature (no one would document it anyway). Also, as development is basically a spare time effort, don't expect complex commercially interesting niches to come for free either as in that case one can wait till I a find a reason for implementing it for fun or development is driven by a project. When thinking of future additions, tex, lua, metapost of a mix is possible. They should be of interest for more than one user. Of course it can also be that everything needed is there. Maybe existing mechanisms can be improved in terms of functionality or performance (although i think that performance wise we're ok). But again keep in mind that the boundary conditions (all these interacting sub mechanisms) also prohibit some functionality. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

12 25

Migrating ConTeXt's Textadept settings from v9 to v10.
by cryo shock 21 Aug '18

21 Aug '18

Hi Hans, I'd surely love help you to adapt ConTeXt's settings from v9 to v10. I hope that the following quotations will help you enough. I also hope that the format doesn't get mixed up when I send this mail. --------------------- QUOTATION start source: https://foicica.com/textadept/manual.html#Migration.Guides Migration Guides Textadept 9 to 10 API Changes Old API Change New API *_G* bit32 Removed N/A *(use bitwise operators)* *buffer* brace_match(pos) Changed brace_match <https://foicica.com/textadept/api.html#buffer.brace_match>(pos, 0) *lexer* _foldsymbols Replaced add_fold_point() <https://foicica.com/textadept/api.html#lexer.add_fold_point> _rules Replaced add_rule() <https://foicica.com/textadept/api.html#lexer.add_rule> _tokenstyles Replaced add_style() <https://foicica.com/textadept/api.html#lexer.add_style> embed_lexer(parent, child, …) Renamed parent:embed <https://foicica.com/textadept/api.html#lexer.embed>(child, …) _RULES[id] Replaced get_rule <https://foicica.com/textadept/api.html#lexer.get_rule>(id) _RULES[id] = rule Replaced modify_rule <https://foicica.com/textadept/api.html#lexer.modify_rule>(id, rule) N/A Added new() <https://foicica.com/textadept/api.html#lexer.new> word_match(list, wchars, icase) Changed word_match <https://foicica.com/textadept/api.html#lexer.word_match>(words, icase) *ui* set_theme Renamed buffer.set_theme() <https://foicica.com/textadept/api.html#buffer.set_theme> *textadept.editing* match_brace Replaced N/A *(menu function)* N/A Added paste() <https://foicica.com/textadept/api.html#textadept.editing.paste> N/A Added paste_reindents <https://foicica.com/textadept/api.html#textadept.editing.paste_reindents> *textadept.session* default_session Removed Configuration Changes Textadept 10 no longer uses a *~/.textadept/properties.lua* file. Instead, all buffer settings are made in *~/.textadept/init.lua*, and apply to the first and any subsequent buffers. (In Textadept 9, any buffer settings made in *~/.textadept/init.lua* only applied to the first buffer, so a *~/.textadept/properties.lua* was required in order to define buffer settings that would affect subsequent buffers.) Simply copying the contents of your *~/.textadept/properties.lua* into *~/.textadept/init.lua* should be sufficient. Lexer Changes Lexers are now written in a more object-oriented way. Legacy lexers are still supported, but it is recommended that you migrate them <https://foicica.com/textadept/api.html#lexer.Migrating.Legacy.Lexers>. Key Bindings Changes The terminal version’s key sequence for Ctrl+Space is now 'c ' instead of 'c@'. Regex Changes Textadept now uses C++11’s ECMAScript regex syntax <https://foicica.com/textadept/manual.html#Regular.Expressions> instead of TRE <https://github.com/laurikari/tre>. Mac OSX System Requirements Textadept now requires Mac OSX 10.6 (Snow Leopard) at a minimum. The previous minimum version was 10.5 (Leopard). LuaJIT Changes The LuaJIT version of Textadept has been removed. Any LuaJIT-specific features used in external modules will no longer function. --------------------- QUOTATION end I also found this here: --------------------- QUOTATION start source: https://foicica.com/textadept/api.html#lexer.Migrating.Legacy.Lexers Migrating Legacy Lexers Legacy lexers are of the form: local l = require('lexer') local token, word_match = l.token, l.word_match local P, R, S = lpeg.P, lpeg.R, lpeg.S local M = {_NAME = '?'} [... token and pattern definitions ...] M._rules = { {'rule', pattern}, [...] } M._tokenstyles = { 'token' = 'style', [...] } M._foldsymbols = { _patterns = {...}, ['token'] = {['start'] = 1, ['end'] = -1}, [...] } return M While such legacy lexers will be handled just fine without any changes, it is recommended that you migrate yours. The migration process is fairly straightforward: 1. Replace all instances of l with lexer, as it’s better practice and results in less confusion. 2. Replace local M = {_NAME = '?'} with local lex = lexer.new('?'), where ? is the name of your legacy lexer. At the end of the lexer, change return M to return lex. 3. Instead of defining rules towards the end of your lexer, define your rules as you define your tokens and patterns using lex:add_rule() <https://foicica.com/textadept/api.html#lexer.add_rule>. 4. Similarly, any custom token names should have their styles immediately defined using lex:add_style() <https://foicica.com/textadept/api.html#lexer.add_style>. 5. Convert any table arguments passed to lexer.word_match() <https://foicica.com/textadept/api.html#lexer.word_match> to a space-separated string of words. 6. Replace any calls to lexer.embed(M, child, ...) and lexer.embed(parent, M, ...) with lex:embed <https://foicica.com/textadept/api.html#lexer.embed>(child, ...) and parent:embed(lex, ...), respectively. 7. Define fold points with simple calls to lex:add_fold_point() <https://foicica.com/textadept/api.html#lexer.add_fold_point>. No need to mess with Lua patterns anymore. 8. Any legacy lexer options such as M._FOLDBYINDENTATION, M._LEXBYLINE, M._lexer, etc. should be added as table options to lexer.new() <https://foicica.com/textadept/api.html#lexer.new>. 9. Any external lexer rule fetching and/or modifications via lexer._RULES should be changed to use lexer.get_rule() <https://foicica.com/textadept/api.html#lexer.get_rule> and lexer.modify_rule() <https://foicica.com/textadept/api.html#lexer.modify_rule>. As an example, consider the following sample legacy lexer: local l = require('lexer') local token, word_match = l.token, l.word_match local P, R, S = lpeg.P, lpeg.R, lpeg.S local M = {_NAME = 'legacy'} local ws = token(l.WHITESPACE, l.space^1) local comment = token(l.COMMENT, '#' * l.nonnewline^0) local string = token(l.STRING, l.delimited_range('"')) local number = token(l.NUMBER, l.float + l.integer) local keyword = token(l.KEYWORD, word_match{'foo', 'bar', 'baz'}) local custom = token('custom', P('quux')) local identifier = token(l.IDENTIFIER, l.word) local operator = token(l.OPERATOR, S('+-*/%^=<>,.()[]{}')) M._rules = { {'whitespace', ws}, {'keyword', keyword}, {'custom', custom}, {'identifier', identifier}, {'string', string}, {'comment', comment}, {'number', number}, {'operator', operator} } M._tokenstyles = { 'custom' = l.STYLE_KEYWORD..',bold' } M._foldsymbols = { _patterns = {'[{}]'}, [l.OPERATOR] = {['{'] = 1, ['}'] = -1} } return M Following the migration steps would yield: local lexer = require('lexer') local token, word_match = lexer.token, lexer.word_match local P, R, S = lpeg.P, lpeg.R, lpeg.S local lex = lexer.new('legacy') lex:add_rule('whitespace', token(lexer.WHITESPACE, lexer.space^1)) lex:add_rule('keyword', token(lexer.KEYWORD, word_match[[foo bar baz]])) lex:add_rule('custom', token('custom', P('quux'))) lex:add_style('custom', lexer.STYLE_KEYWORD..',bold') lex:add_rule('identifier', token(lexer.IDENTIFIER, lexer.word)) lex:add_rule('string', token(lexer.STRING, lexer.delimited_range('"'))) lex:add_rule('comment', token(lexer.COMMENT, '#' * lexer.nonnewline^0)) lex:add_rule('number', token(lexer.NUMBER, lexer.float + lexer.integer)) lex:add_rule('operator', token(lexer.OPERATOR, S('+-*/%^=<>,.()[]{}'))) lex:add_fold_point(lexer.OPERATOR, '{', '}') return lex Considerations Performance There might be some slight overhead when initializing a lexer, but loading a file from disk into Scintilla is usually more expensive. On modern computer systems, I see no difference in speed between Lua lexers and Scintilla’s C++ ones. Optimize lexers for speed by re-arranging lexer.add_rule() calls so that the most common rules match first. Do keep in mind that order matters for similar rules. In some cases, folding may be far more expensive than lexing, particularly in lexers with a lot of potential fold points. If your lexer is exhibiting signs of slowness, try disabling folding in your text editor first. If that speeds things up, you can try reducing the number of fold points you added, overriding lexer.fold() with your own implementation, or simply eliminating folding support from your lexer. Limitations Embedded preprocessor languages like PHP cannot completely embed in their parent languages in that the parent’s tokens do not support start and end rules. This mostly goes unnoticed, but code like <div id="<?php echo $id; ?>"> will not style correctly. Troubleshooting Errors in lexers can be tricky to debug. Lexers print Lua errors to io.stderr and _G.print() statements to io.stdout. Running your editor from a terminal is the easiest way to see errors as they occur. Risks Poorly written lexers have the ability to crash Scintilla (and thus its containing application), so unsaved data might be lost. However, I have only observed these crashes in early lexer development, when syntax errors or pattern errors are present. Once the lexer actually starts styling text (either correctly or incorrectly, it does not matter), I have not observed any crashes. --------------------- QUOTATION end If you could use anything else, let me know. Cheers, L.

3 2