From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: I can't change startitemize[n]--> startitemize[1]
Date: Thu, 23 Jul 2009 17:46:19 +0200 [thread overview]
Message-ID: <fe8d59da0907230846g624813d3g5edbb7201b806b62@mail.gmail.com> (raw)
In-Reply-To: <98480CAB-3F1A-401D-9D3B-574359605E56@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 962 bytes --]
On Thu, Jul 23, 2009 at 5:33 PM, Wolfgang Schuster <
schuster.wolfgang@googlemail.com> wrote:
>
> Am 23.07.2009 um 17:16 schrieb luigi scarso:
>
> hmm, where do you see the problem ?
>>
>
> As programmer it's no problem to use a namespace for macros but how
> do you convince users to use them,
it's up to us make an easy convention.
> should they write
>
> \startprivate[foo]
>
> \definenote[footnote][...]
>
> \defineregister[index][...]
>
> ...
>
> \stopprivate
>
> and use them with
>
> 'fooindex', 'foofootnote' ...
>
> in their documents?
>
true, but what about
\startprivate[texns:Logo='www.logosrl.it/context']
\definenote[Footnote][...]
\defineregister[Index][...]
...
\stopprivate
\LogoFootnote
\LogoIndex
Not so horrible; one can easily see in the
source own private macros.
>
>
> In this case it would be better to write to write commands like \MyNote
>
Yes, it's a discipline problem.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 2214 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-07-23 15:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 12:06 Xan
2009-07-23 12:45 ` Wolfgang Schuster
2009-07-23 14:05 ` Hans Hagen
2009-07-23 14:33 ` Xan
2009-07-23 14:37 ` Hans Hagen
2009-07-23 14:48 ` luigi scarso
2009-07-23 14:58 ` Wolfgang Schuster
2009-07-23 15:05 ` luigi scarso
2009-07-23 15:10 ` Wolfgang Schuster
2009-07-23 15:16 ` luigi scarso
2009-07-23 15:26 ` luigi scarso
2009-07-23 15:33 ` Wolfgang Schuster
2009-07-23 15:46 ` luigi scarso [this message]
2009-07-23 15:05 ` Aditya Mahajan
2009-07-23 15:11 ` luigi scarso
2009-07-23 15:16 ` Wolfgang Schuster
2009-07-23 15:52 ` Aditya Mahajan
2009-07-23 15:57 ` luigi scarso
2009-07-23 16:04 ` Hans Hagen
2009-07-23 15:42 ` Xan
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=fe8d59da0907230846g624813d3g5edbb7201b806b62@mail.gmail.com \
--to=luigi.scarso@gmail.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).