From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: "Jan D." <jan.h.d@swipnet.se>, emacs-devel@gnu.org
Subject: Re: FIX: byte-code: Wrong type argument: number-or-marker-p, (+ -21)
Date: Wed, 19 Nov 2003 22:07:39 +0100 [thread overview]
Message-ID: <m3n0as9iec.fsf@appel.flower> (raw)
In-Reply-To: <m3r804waln.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "19 Nov 2003 18:07:32 +0100")
storm@cua.dk (Kim F. Storm) writes:
> This is definitely better than before, but you still do not address
> the issue whether the new setting for top should be top/left or
> bottom/right relative, ie. whether the new top value should be (+ INT)
> or (- INT) if the old settings had that format (rather than an
> integer).
Ah. I assumed this:
`((top . ,(+ top (* lines char-height))))
to be correct, and the value of TOP wrong if not an INT, but you're
suggesting something like:
`((top . ,((if (consp top)
(cond ((eq '+ (car top))
(list '+ (+ (cadr top) (* lines char-height))))
((eq '- (car top))
(list '- (- (cadr top) (* lines char-height))))
(t 0))
,(+ top (* lines char-height))))))
but I'm not at all sure about the right arithmetic for (+/- INT) ...
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
next prev parent reply other threads:[~2003-11-19 21:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 15:33 byte-code: Wrong type argument: number-or-marker-p, (+ -21) Jan Nieuwenhuizen
2003-11-14 22:47 ` Jan D.
2003-11-17 10:15 ` FIX: " Jan Nieuwenhuizen
2003-11-17 14:06 ` Kim F. Storm
2003-11-17 13:43 ` Jan Nieuwenhuizen
2003-11-19 13:26 ` Jan Nieuwenhuizen
2003-11-19 17:07 ` Kim F. Storm
2003-11-19 21:07 ` Jan Nieuwenhuizen [this message]
2003-11-19 23:46 ` Kim F. Storm
2003-11-20 9:59 ` FIX#3: " Jan Nieuwenhuizen
2003-11-23 21:32 ` Jan D.
2003-12-06 16:14 ` Geometry interpretation change? (was: FIX#3: byte-code: Wrong type argument: number-or-marker-p, (+ -21)) Jan D.
2003-12-07 0:57 ` Kim F. Storm
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3n0as9iec.fsf@appel.flower \
--to=janneke@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).