On Wed, Sep 26, 2012 at 11:39 PM, Hans Hagen wrote:
Hi,
Is minimals.contextgarden.net offline?
Until we figure out what exactly is wrong one can use the mirror:
rsync://metatex.org/minimals/
http://minimals.metatex.org/
Mojca
Hi there,
Not quite sure if this is the right place. I wanted to send this directly to
Khaled Hosny, but then I thought it might be good to have some additional
opinion on some of these issues (I am not quite sure if some of this is
intended behaviour).
I have collected some examples for
Hi all,
As I understand it, \define[2] is preferred over \def#1#2 because it
refuses to overwrite existing commands.
\define[2]\mycommand{code code code}
defines a command to be invoked with
\mycommand{...}{...}
Can I use \define, or a related command, to define a command that
takes
On 09/27/2012 05:45 PM, Sietse Brouwer wrote:
Hi all,
As I understand it, \define[2] is preferred over \def#1#2 because it
refuses to overwrite existing commands.
\define[2]\mycommand{code code code}
defines a command to be invoked with
\mycommand{...}{...}
Can I use \define, or a related
2012-09-27 Sietse Brouwer sbbrou...@gmail.com:
Hi Sietse,
As I understand it, \define[2] is preferred over \def#1#2 because it
refuses to overwrite existing commands.
\define overwrites existing commands with pleasure. In contrast to
\def it prints a message to the log file: “\mycommand is
Hi all,
I've found a helper function that does this:
utilities.parsers.settings_to_hash('ape=1, note=2, mice=3')
--
{
[ape] = 1,
[note] = 2,
[mice] = 3
}
This makes me very happy. This function and its friends are stored
under utilities.parsers, and defined in util-prs.lua; I've listed
On Thu, Sep 27, 2012 at 04:58:11PM +0200, Andreas Mang wrote:
Hi there,
Not quite sure if this is the right place. I wanted to send this
directly to Khaled Hosny, but then I thought it might be good to have
some additional opinion on some of these issues (I am not quite sure
if some of this
On Thu, 27 Sep 2012, Khaled Hosny wrote:
On Thu, Sep 27, 2012 at 04:58:11PM +0200, Andreas Mang wrote:
Hi there,
Not quite sure if this is the right place. I wanted to send this
directly to Khaled Hosny, but then I thought it might be good to have
some additional opinion on some of these
On Thu, Sep 27, 2012 at 01:01:35PM -0400, Aditya Mahajan wrote:
On Thu, 27 Sep 2012, Khaled Hosny wrote:
None of those glyphs were changed in XITS, they are exactly the same as
the ones in STIX fonts, so possibly ConTeXt is using the wrong Unicode
character for those symbols. The later two
This is a problem originally posted in TeX/StackExchange. However, since
I have not had any luck in finding a solution I post it here too. I am
confident that somebody here should know the answer.
http://tex.stackexchange.com/questions/73970/problem-with-context-mkiv-hebrew-and-ligatures
Hello,
Can someone indicate how to typeset
$L_{α+β}$
as verbatim text?
(\arg{} doesn't help here...)
Furthermore, I suppose that typesetting Greek characters verbatim
depends also upon which \tt font is being used.
Alan
Can someone indicate how to typeset
$L_{α+β}$
as verbatim text?
(\arg{} doesn't help here...)
Untested:
\type{...} should work. (Definitely did work a couple of months ago).
Furthermore, I suppose that typesetting Greek characters verbatim
depends also upon which \tt font is being used.
CM
Thank you for yor time, Peter. But this is not what I wanted... :-(
Is there a way to know the directory of the currently being processed
source file?
This works with mkiv:
\starttext
PWD: \cldcontext{io.popenpwd:read()}
\stoptext
This gives the directory where the context command was
Hi all,
the background mechanism of tabulations is quite simplistic: it
extends only to the first line of a cell irrespective of its
length. Example:
···
\starttext
\starttabulate[|p|r|]
\CM [red] \input knuth \NC was said by
On Fri, 28 Sep 2012, Philipp Gesang wrote:
Hi all,
the background mechanism of tabulations is quite simplistic: it
extends only to the first line of a cell irrespective of its
length. Example:
···
\starttext
I want to know a function that returns
/fullpath_to_project/products/
when I call it from the script products/product.tex. And I want it to return
/fullpath_to_project/products/product/
when I call it from the script products/product/article.tex.
Finally found it, after lots of
Hi Marco,
(PS for Hans),
Marco wrote:
\in{figure}[alpha,beta,gamma]
This outputs “figure 1”. What I'd like to have is “figure 1-3”.
The attached quasi-module seems to do it! On my computer, at least. (I
call it 'quasi' because it is really nothing more than code in a file
of its own. No
17 matches
Mail list logo