GNU bug report logs - #4016
23.1.50; docview: scrolling up breaks after setting a slice

Previous Next

Package: emacs;

Reported by: Paer Kurlberg <kurlberg <at> math.kth.se>

Date: Sun, 2 Aug 2009 14:15:04 UTC

Severity: normal

Tags: moreinfo

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Tassilo Horn <tassilo <at> member.fsf.org>
To: Paer Kurlberg <kurlberg <at> math.kth.se>
Cc: 4016 <at> debbugs.gnu.org
Subject: bug#4016: Acknowledgement (23.1.50; docview: scrolling up breaks after setting a slice)
Date: Mon, 03 Aug 2009 08:46:27 +0200
Paer Kurlberg <kurlberg <at> math.kth.se> writes:

> In case it might be helpful: below is a backtrace.  It seems that the
> problem is that image-get-display-property (called in the function
> image-next-line) returns the list
>
> ((slice 0 0 1100 1600) (image :type png :file
>   "/tmp/docview1000/arnold.dvi-b04e9949bb98146d331479915a45fc5b/page-1.png"
>   :pointer arrow))
>
> and therefore image-size complains since a "proper image" should be a
> list whose car equals 'image.

I can reproduce the error.  But I'm not too sure where the bug is
located.  According to the docs, the display property may be a single
display spec, or a list or vector of such.

,----[ (info "(elisp)Display Property") ]
| The value of the `display' property should be a display specification,
| or a list or vector containing several display specifications.
`----

So in that respect the slice + image spec are ok.

I think that maybe the C function

  int valid_image_p (object) Lisp_Object object;

in image.c should be adapted to accept lists/vectors including one image
spec.

Bye,
Tassilo



This bug report was last modified 3 years and 308 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.