From: Hraban <angerweit@gmx.net>
Subject: Re: strange behaviour
Date: Fri, 20 Oct 2000 19:58:56 +0200 [thread overview]
Message-ID: <39F087DF.2F19A59C@gmx.net> (raw)
In-Reply-To: <3.0.6.32.20001020181342.0151cd00@pop.wxs.nl>
Hans Hagen wrote:
> >- I defined chapters with page=yes, but some (not all) chapters
> > get chained without page breaks. What could cause this?
> should go ok, no changes
*should*, really! Do you have an idea, what I should check?
> >- Some long tables with \splitfloat split after a half full page,
> > and the following pages are overfull (table reaches to the pagina
> > line!)
> split is kind of tricky
Is there anything to look after? What must I do, that it will work?
> >- Some tabulates write some two lines together (looks like CR without LF)
> do you miss any \NC ?
I'll check it again, but I had the same problem at other places, there
I wrote exactly the same line below and commented out the "wrong" one,
and it worked. I checked the file with an hex editor, if there were any
control codes, but didn't find any.
> >(2) chapter depending error
> >One of my chapters doesn't want to run. The whole book without it runs,
> Do you redefine a command? Or have a grouping error?
I defined a lot of new commands, but as far I see I didn't touch existing.
And I used no other commands in this special chapter than in others.
> >! Undefined control sequence.
> ><write> ...{}{formal}{}{\realfolio }{\@@cvset 345
> this is a conversion call, but 234 should be a keyword/value not a number,
> so, did you define your old commands without using CapInTheName?
Yes, there are some only lower case commands. Is that not allowed?
(I'm sure that they didn't exist before.)
> >What could be the reason for this?
> this looks like a missing } or \stop... error
Thought of sort of this, but found no missing stop.
And I think the error should come also with other chapters --
it's only with this combination!
> >Everything together looks for me like some wrong configuration
> >of something fundamental -- but what?
> maybe, actually you use macros that haven't changed, so don't panic. We run
> pretty complicated big files here daily -)
I did not mean that "something fundamental" was your fault.
--
Grüßlis vom Hraban!
---
http://angerweit.tikon.ch/
next prev parent reply other threads:[~2000-10-20 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-20 12:58 Hraban
2000-10-20 16:13 ` Hans Hagen
2000-10-20 17:58 ` Hraban [this message]
2000-10-22 18:23 ` Hans Hagen
2000-10-23 16:50 ` Hraban
[not found] ` <39F5C05B.9F161FE1@gmx.net>
2000-10-25 8:02 ` Hans Hagen
2000-10-27 8:57 ` Hraban
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=39F087DF.2F19A59C@gmx.net \
--to=angerweit@gmx.net \
/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).