From: "Willi Egger" <w.egger@boede.nl>
Subject: Re: subdivision prefix/suffix
Date: Sat, 16 Nov 2002 15:09:21 +0100 [thread overview]
Message-ID: <004c01c28d7a$a683feb0$0700a8c0@vademecum> (raw)
In-Reply-To: <200211141547.37729.ishamid@attbi.com>
Hello Idris,
Your problem was in a thread which I started. Hand gave the advice to place
\let\localkoprefix\empty
at the beginning of the file. - This indeed solves the error.
Success Willi
----- Original Message -----
From: "Idris S Hamid" <ishamid@attbi.com>
To: <ntg-context@ntg.nl>
Sent: Friday, November 15, 2002 12:47 AM
Subject: [NTG-context] subdivision prefix/suffix
> 2 problems:
>
> 1) I'm trying to get \subsubsection to add a suffix (namely a colon) to
every
> argument, viz.
>
> \subsubsection{Note} ===> Note:
>
> I tried
>
> \setuphead [subsubsection][style=bold,
> number=no,
> before={\blank[small]},
> after={\blank[disable]},
> prefix=-:]
>
> which results in
>
> -------------------------------
> ! Undefined control sequence.
> <argument> \localkopprefix
>
> \setupreferenceprefix [#1]->\edef \@@rfprefix {#1
> }\ifx \@@rfprefix \empty
> \l...
>
> \dodododosomekop ...renceprefix [\localkopprefix ]
> \fi \dosomebreak
\nobreak
> ...
> l.46 \subsubsection{tanbIh"}
> ----------------------------------
>
> Am I using "prefix" wrong? Is there another way I'm supposed to do this?
>
> 2) I would like to not only disable the space after \subsubsection but
also
> have the main text start immediately after the argument, viz.
>
> \subsubsection{Note}
>
> Here is some text
>
> ===>>
>
> Note: Here is some text
>
> Is this possible??
>
> Best wishes
> Idris
>
> --
> Dr. Idris S Hamid
> Department of Philosophy
> Colorado State University
> Fort Collins, CO 80523
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
prev parent reply other threads:[~2002-11-16 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 23:47 Idris S Hamid
2002-11-15 9:38 ` Hans Hagen
2002-11-16 14:09 ` Willi Egger [this message]
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='004c01c28d7a$a683feb0$0700a8c0@vademecum' \
--to=w.egger@boede.nl \
--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).