Hi all,
I'm working with a few custom macros to simplify typing a bit, like:
\def\VHDL{\small{VHDL}}
However, when I use this macro in text, like \VHDL this, it gobbles the space
after it. I've seen some references that say to solve this by writing \VHDL{}
instead, but that is of course very unp
On Fri, Nov 20, 2009 at 11:23 AM, Matthijs Kooijman wrote:
> Hi all,
>
> I'm working with a few custom macros to simplify typing a bit, like:
>
> \def\VHDL{\small{VHDL}}
>
> However, when I use this macro in text, like \VHDL this, it gobbles the space
> after it. I've seen some references that say
luigi scarso wrote:
> On Fri, Nov 20, 2009 at 11:23 AM, Matthijs Kooijman wrote:
>> Hi all,
>>
>> I'm working with a few custom macros to simplify typing a bit, like:
>>
>> \def\VHDL{\small{VHDL}}
>>
>> However, when I use this macro in text, like \VHDL this, it gobbles the space
>> after it. I'
> \autoinsertnextspace is the context version of \xspace (could be mkii
> only)
Woah, that works (in MkIV). Thanks!
Gr.
Matthijs
signature.asc
Description: Digital signature
___
If your question is of interest to ot
Hi Hans, all,
the two latest betas have trouble loading fonts from my own typescripts. All
errors point to the same line in font-syn.lua. I don't have a minimal example
yet, but here's a minimal command line that triggers the error on my box:
mtxrun --script fonts --list --pattern="*gentium*"
.
On Fri, Nov 20, 2009 at 11:41 AM, Matthijs Kooijman wrote:
>> \autoinsertnextspace is the context version of \xspace (could be mkii
>> only)
> Woah, that works (in MkIV). Thanks!
hm , some problem here
# context --version
MTXrun | main context file: context.tex
MTXrun | current version: 2009.11.1
Thomas A. Schmitz wrote:
> Hi Hans, all,
>
> the two latest betas have trouble loading fonts from my own typescripts. All
> errors point to the same line in font-syn.lua. I don't have a minimal example
> yet, but here's a minimal command line that triggers the error on my box:
>
> mtxrun --sc
Taco Hoekwater wrote:
>
> Thomas A. Schmitz wrote:
>> Hi Hans, all,
>>
>> the two latest betas have trouble loading fonts from my own typescripts. All
>> errors point to the same line in font-syn.lua. I don't have a minimal
>> example yet, but here's a minimal command line that triggers the er
Hi Luigi,
> hm , some problem here
> # context --version
> MTXrun | main context file: context.tex
> MTXrun | current version: 2009.11.10 13:30
Your example works fine for me on an older beta:
$ context --version
MTXrun | main context file: /usr/share/texmf/tex/context/base/context.tex
MTX
On Friday 20 November 2009 11:41:16 Matthijs Kooijman wrote:
> > \autoinsertnextspace is the context version of \xspace (could be mkii
> > only)
>
> Woah, that works (in MkIV). Thanks!
*Everywhere* the authors use \CONTEXT\ and \TeX\ followed by
an escaped space. (Is this space [sometimes] unbrea
On Fri, Nov 20, 2009 at 12:00 PM, Matthijs Kooijman wrote:
> Hi Luigi,
>
>> hm , some problem here
>> # context --version
>> MTXrun | main context file: context.tex
>> MTXrun | current version: 2009.11.10 13:30
>
> Your example works fine for me on an older beta:
>
> $ context --version
> MTXrun
> On Wed, 18 Nov 2009 09:58:26 -0700,
> wrote:
>
> > Does anyone use Notepad++ with the function "calltips"
feature? Checking
> > the
> > context.xml definition file, there are calltips defined for
> > \startitemize, but
> > they never appear when I'm typing, even though the auto-completio
Am 20.11.2009 um 11:45 schrieb Thomas A. Schmitz:
> Hi Hans, all,
>
> the two latest betas have trouble loading fonts from my own typescripts. All
> errors point to the same line in font-syn.lua. I don't have a minimal example
> yet, but here's a minimal command line that triggers the error on
2009/11/20 Wolfgang Schuster :
>
> Am 20.11.2009 um 11:45 schrieb Thomas A. Schmitz:
>
>> Hi Hans, all,
>>
>> the two latest betas have trouble loading fonts from my own typescripts. All
>> errors point to the same line in font-syn.lua. I don't have a minimal
>> example yet, but here's a minimal
Thomas A. Schmitz wrote:
Hi Hans, all,
the two latest betas have trouble loading fonts from my own typescripts. All
errors point to the same line in font-syn.lua. I don't have a minimal example
yet, but here's a minimal command line that triggers the error on my box:
mtxrun --script fonts --l
On Nov 20, 2009, at 1:17 PM, Wolfgang Schuster wrote:
>> Hi Hans, all,
>>
>> the two latest betas have trouble loading fonts from my own typescripts. All
>> errors point to the same line in font-syn.lua. I don't have a minimal
>> example yet, but here's a minimal command line that triggers the
Thomas A. Schmitz wrote:
On Nov 20, 2009, at 1:17 PM, Wolfgang Schuster wrote:
Hi Hans, all,
the two latest betas have trouble loading fonts from my own typescripts. All
errors point to the same line in font-syn.lua. I don't have a minimal example
yet, but here's a minimal command line that
Yanrui Li wrote:
2009/11/20 Wolfgang Schuster :
Am 20.11.2009 um 11:45 schrieb Thomas A. Schmitz:
Hi Hans, all,
the two latest betas have trouble loading fonts from my own typescripts. All
errors point to the same line in font-syn.lua. I don't have a minimal example
yet, but here's a minima
2009/11/20 Hans Hagen :
> Yanrui Li wrote:
>>
>> I did so and solved this problem. However I can not use Chinese OTF
>> fonts such as 'AdobeSongStd-Light.otf', because luatex need very very
>> large memory to load it in the stage of *enhancing* . This is a test
>> file:
>>
>> \definefont[song][name
On Nov 20, 2009, at 1:50 PM, Hans Hagen wrote:
>
> do you have a small test file?
>
Not yet. It looks like it has something to do with font features, but I can't
reproduce it with a minimal file yet (it occurs in a presentation with our
simple-slides module). I'll try and see if I can find a
> On Wed, 18 Nov 2009 09:58:26 -0700,
> wrote:
>
> > Does anyone use Notepad++ with the function "calltips"
feature? Checking
> > the
> > context.xml definition file, there are calltips defined for
> > \startitemize, but
> > they never appear when I'm typing, even though the auto-completio
Thanks, Hans. I just tested with the latest betas from the minimals, and
\completelistofacronyms works again.
Kevin
On Tue, Nov 10, 2009 at 11:54 AM, Kevin D. Robbins <
robbins.kevi...@gmail.com> wrote:
> In the latest beta from minimals, \completelistofacronyms does not typeset
> the meaning of
Kevin D. Robbins wrote:
Thanks, Hans. I just tested with the latest betas from the minimals, and
\completelistofacronyms works again.
should work ok in the beta now
-
Hans Hagen | PRAGMA A
Yanrui Li wrote:
2009/11/20 Hans Hagen :
Yanrui Li wrote:
I did so and solved this problem. However I can not use Chinese OTF
fonts such as 'AdobeSongStd-Light.otf', because luatex need very very
large memory to load it in the stage of *enhancing* . This is a test
file:
\definefont[song][name:
Hi all,
I was trying the following bib example on MkIV beta 2009.11.20 and
luatex beta-0.44.0-2009103007.
There isn't an apparent error message, but neither the bib reference or the
publication list appears in the pdf.
Observations:
1. In MkII, it works well.
2. In MkIV, if you use the [criterium
> "Taco" == Taco Hoekwater writes:
Taco> You could pre-assign a zero-padded number to each book
Taco> (Genesis=001, Exodus=002), and use that number inside the
Taco> square brackets.
Right, but that would be extremely annoying to type in all the time
:-)
I'm looking for a more a
ber...@pobox.com wrote:
"Taco" == Taco Hoekwater writes:
Taco> You could pre-assign a zero-padded number to each book
Taco> (Genesis=001, Exodus=002), and use that number inside the
Taco> square brackets.
Right, but that would be extremely annoying to type in all the time
:-)
I'm
ber...@pobox.com wrote:
"Taco" == Taco Hoekwater writes:
Taco> You could pre-assign a zero-padded number to each book
Taco> (Genesis=001, Exodus=002), and use that number inside the
Taco> square brackets.
Right, but that would be extremely annoying to type in all the time
:-)
\d
On Fri, 20 Nov 2009 09:21:34 -0700,
wrote:
After some experiments, I think the problem is that Notepad++ is
ignoring the case of the commands when searching for calltips. By
re-sorting the list I was able to get calltips to work. However, with
this new sorting the auto-complete no longer
Hi,
Change the name of the attached to end in .zip . I can confirm that the
context calltips work for this version of context.xml in Npp 5.5.1.
OTOH, the ignoreCase=no used to work, and that is something that the Npp
developers will hopefully take care of.
Richard, if you make additional
Hi all,
I have a module with lots of lua code, and I'd like to move most of the lua
code to a separate file, say t-module.lua. I have written all of the lua
code using \modulecode and \startmodulecode ... \stopmodulecode. But, when I
move the lua code to t-module.lua and load it with dofile, it se
Kevin D. Robbins wrote:
Hi all,
I have a module with lots of lua code, and I'd like to move most of the
lua code to a separate file, say t-module.lua. I have written all of the
lua code using \modulecode and \startmodulecode ... \stopmodulecode.
But, when I move the lua code to t-module.lua a
Hi Hans,
I started reading at \registerctxluafile in luat-cod.mkiv, but it wasn't
quite what I was looking for. But, I then stumbled on \definenamedlua in
luat-ini.mkiv. There, I learned of the function 'protect' in luat-ini.lua.
So, adding the line
protect("moduledata")
at the top of t-module.l
2009/11/21 Hans Hagen :
> Yanrui Li wrote:
>>
>> 2009/11/20 Hans Hagen :
>>>
>>> Yanrui Li wrote:
I did so and solved this problem. However I can not use Chinese OTF
fonts such as 'AdobeSongStd-Light.otf', because luatex need very very
large memory to load it in the stage of *en
34 matches
Mail list logo
