* Font objects
@ 2008-02-26 12:15 Johan Bockgård
2008-02-27 1:33 ` Kenichi Handa
0 siblings, 1 reply; 4+ messages in thread
From: Johan Bockgård @ 2008-02-26 12:15 UTC (permalink / raw)
To: emacs-devel
This internal-looking type shows up in Lisp land:
(font-at 0 nil "x")
=> #<save_value ptr=0x018c03b0 int=8>
--
Johan Bockgård
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Font objects
2008-02-26 12:15 Font objects Johan Bockgård
@ 2008-02-27 1:33 ` Kenichi Handa
2008-02-27 11:35 ` Johan Bockgård
0 siblings, 1 reply; 4+ messages in thread
From: Kenichi Handa @ 2008-02-27 1:33 UTC (permalink / raw)
To: Johan =?ISO-2022-JP-2?B?Qm9ja2c=GyQoRCspGyhCcmQ=?=; +Cc: emacs-devel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=ISO-2022-JP-2, Size: 451 bytes --]
In article <yoijejaz3odu.fsf@remote2.student.chalmers.se>, bojohan+news@dd.chalmers.se (Johan Bockg^[$(D+)^[(Brd) writes:
> This internal-looking type shows up in Lisp land:
> (font-at 0 nil "x")
>>> #<save_value ptr=0x018c03b0 int=8>
Does it cause any problem? In the future, I'd like to
implement a font-object not as Lisp_Misc_Save_Value type but
as some of pseudovector type. That is much cleaner.
---
Kenichi Handa
handa@ni.aist.go.jp
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Font objects
2008-02-27 1:33 ` Kenichi Handa
@ 2008-02-27 11:35 ` Johan Bockgård
2008-02-27 11:51 ` Kenichi Handa
0 siblings, 1 reply; 4+ messages in thread
From: Johan Bockgård @ 2008-02-27 11:35 UTC (permalink / raw)
To: emacs-devel
Kenichi Handa <handa@m17n.org> writes:
> bojohan+news@dd.chalmers.se (Johan Bockgård) writes:
>
>> This internal-looking type shows up in Lisp land:
>
>> (font-at 0 nil "x")
>>>> #<save_value ptr=0x018c03b0 int=8>
>
> Does it cause any problem? In the future, I'd like to implement a
> font-object not as Lisp_Misc_Save_Value type but as some of
> pseudovector type. That is much cleaner.
`type-of' crashes when given this object.
--
Johan Bockgård
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Font objects
2008-02-27 11:35 ` Johan Bockgård
@ 2008-02-27 11:51 ` Kenichi Handa
0 siblings, 0 replies; 4+ messages in thread
From: Kenichi Handa @ 2008-02-27 11:51 UTC (permalink / raw)
To: Johan =?ISO-2022-JP-2?B?Qm9ja2c=GyQoRCspGyhCcmQ=?=; +Cc: emacs-devel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=ISO-2022-JP-2, Size: 982 bytes --]
In article <yoijtzju1vkr.fsf@remote2.student.chalmers.se>, bojohan+news@dd.chalmers.se (Johan Bockg^[$(D+)^[(Brd) writes:
> Kenichi Handa <handa@m17n.org> writes:
> > bojohan+news@dd.chalmers.se (Johan Bockg^[$(D+)^[(Brd) writes:
> >
>>> This internal-looking type shows up in Lisp land:
> >
>>> (font-at 0 nil "x")
>>>>> #<save_value ptr=0x018c03b0 int=8>
> >
> > Does it cause any problem? In the future, I'd like to implement a
> > font-object not as Lisp_Misc_Save_Value type but as some of
> > pseudovector type. That is much cleaner.
> `type-of' crashes when given this object.
Ummm, I didn't know. I want to do the work of implementing
a real font-object at the same time as I make the
font-backend the mandatory and remove all legary font
handling code. But, as I'm now so overloaded, I can't start
that work. If fixing this problem is urgent, I welcome
anyone to change the current font-object representation to a
real object.
---
Kenichi Handa
handa@ni.aist.go.jp
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-02-27 11:51 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-26 12:15 Font objects Johan Bockgård
2008-02-27 1:33 ` Kenichi Handa
2008-02-27 11:35 ` Johan Bockgård
2008-02-27 11:51 ` Kenichi Handa
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).