From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: image instance/specifier/instantiator
Date: 24 Nov 1998 10:36:09 +0100 [thread overview]
Message-ID: <m3n25hph4m.fsf@sparky.gnus.org> (raw)
In-Reply-To: Hrvoje Niksic's message of "22 Nov 1998 14:09:35 +0100"
Hrvoje Niksic <hniksic@srce.hr> writes:
> That's quite strange. Anyway, if I were you, I'd try with
> (glyph-width (annotation-glyph ...)) and
> (glyph-height (annotation-glyph ...)).
Thanks; this does the trick.
> BTW, why do you create image specifiers at all? I don't think you
> need to do that -- an instantiator should suffice.
Er... I though
(make-image-specifier
(vector (intern type) :data (buffer-string)))
was the simplest way to create an image? This can later be fed to
`make-annotation' for insertion into the buffer...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-11-24 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-21 6:06 Lars Magne Ingebrigtsen
1998-11-22 13:09 ` Hrvoje Niksic
1998-11-24 9:36 ` Lars Magne Ingebrigtsen [this message]
1998-11-24 11:46 ` Hrvoje Niksic
1998-11-24 19:57 ` Lars Magne Ingebrigtsen
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=m3n25hph4m.fsf@sparky.gnus.org \
--to=larsi@gnus.org \
/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).