ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Exceptions to assignment syntax [was: Re: labeltext assignment]
Date: Tue, 12 Jun 2012 16:24:13 +0200	[thread overview]
Message-ID: <20120612162413.7ea0408d@homerow> (raw)
In-Reply-To: <4FD74AEB.8000201@wxs.nl>

On 2012-06-12 Hans Hagen <pragma@wxs.nl> wrote:

> On 12-6-2012 13:42, Marco wrote:
> > On 2012-06-11 Philipp Gesang <gesang@stud.uni-heidelberg.de> wrote:
> >
> >> Dear others, please contribute if you know about further setups
> >> whose parameters behave in a non-standard way.
> >
> > Here's another candidate: \usepath
> >
> > http://article.gmane.org/gmane.comp.tex.context/75727
> 
> that's one that can be dealt with (I'll adapt that one)

While you're at it, check \usesubpath as well. I didn't test, but
assume it has the same issue.

> >> As this is quite counterintuitive, I’d like to wikify any known
> >> exceptions somewhere over here:
> >
> > How about unifying the interface? IMO that would make more sense
> > then bury the “caveats” somewhere deep in the wiki.
> 
> that's currently not feasable for all

What's the reason? Performance of backwards compatibility?

Personally, I would sacrifice some runtime in favour of a more
uniform interface. That's one of the main ideas that define ConTeXt
and set it apart from other TeX macro packages.

Regarding the backwards compatibility, wasn't MkIV the chance to
introduce incompatible changes (changes for improving the user
interface :)?


Marco


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2012-06-12 14:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  8:01 labeltext assignment Philipp Gesang
2012-06-11  9:03 ` Hans Hagen
2012-06-11 19:06   ` Philipp Gesang
2012-06-11 19:27     ` Wolfgang Schuster
2012-06-11 21:33       ` Exceptions to assignment syntax [was: Re: labeltext assignment] Philipp Gesang
2012-06-11 22:15         ` Aditya Mahajan
2012-06-11 22:22           ` Aditya Mahajan
2012-06-11 22:34             ` Philipp Gesang
2012-06-12 10:24             ` Wolfgang Schuster
2012-06-11 22:27           ` Philipp Gesang
2012-06-12 11:42         ` Marco
2012-06-12 13:58           ` Hans Hagen
2012-06-12 14:24             ` Marco [this message]
2012-06-12 14:33               ` Hans Hagen
2012-06-12 14:41                 ` Philipp Gesang
2012-06-12 17:13                   ` Hans Hagen
2012-06-16 13:19                     ` Philipp Gesang
2012-06-18  9:46                       ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120612162413.7ea0408d@homerow \
    --to=netuse@lavabit.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).