At the elisp-
wielding-user-visible level this manifests in what you pass to and
get back from x-list-fonts, as well as any font-setting functions,
Could you explain what "font-setting functions" means?
Could you name some "font-setting functions"?
setting font as a frame p
On Oct 11, 2005, at 10:44 AM, Richard M. Stallman wrote: (I guess I was trying to say, "drop XLFD, and if some functionality is lost, update the lisp syntax to fix it".)We don't need to change Emacs for that. You should be able, already,to do whatever you like in Emacs without using
To do something to make the whole thing more usable, one can simply
ensure that on each operating system the local standard font
selection user interface is used. All systems offer some standard
dialog to do that, and it would be a good idea if users can specify
the list
On 11 Oct 2005, at 15:44, Richard M. Stallman wrote:
.default {
font-family: courier;
font-size: 13pt;
font-weight: bold;
font-style: italic;
}
I don't think that is useful in an Emacs context.
It is no easier to type, no more concise, than a list
of face attributes
On Oct 11, 2005, at 4:01 AM, YAMAMOTO Mitsuharu wrote:
On Fri, 07 Oct 2005 10:53:22 -0400, Adrian Robert
<[EMAIL PROTECTED]> said:
In addition, I've been integrating the Cocoa port's font handling
with xfaces.c, and can say it's onerous for developers. All of
these structures and functi
(I guess I was
trying to say, "drop XLFD, and if some functionality is lost, update
the lisp syntax to fix it".)
We don't need to change Emacs for that. You should be able, already,
to do whatever you like in Emacs without using XLFD syntax. What is there
that cannot be done ex
> On Fri, 07 Oct 2005 10:53:22 -0400, Adrian Robert <[EMAIL PROTECTED]>
> said:
> In addition, I've been integrating the Cocoa port's font handling
> with xfaces.c, and can say it's onerous for developers. All of
> these structures and functions concerned with creating, parsing, and
> st
>> I'm not against the introduction of a new font specification style,
>> but I think it is mainly for developers and power-users. Emacs
>> already has a mechanism that enables users to specify fonts in a
>> simpler way at the face level.
> You're right.. But the population of "power users" in t
On Oct 9, 2005, at 2:16 PM, Richard M. Stallman wrote:
You're right.. But the population of "power users" in this
case for
whatever reason seems fairly large (just subjective
impression), and
the requirement to learn XLFD (to compose a fontset, or whatever
else) and partake
You're right.. But the population of "power users" in this case for
whatever reason seems fairly large (just subjective impression), and
the requirement to learn XLFD (to compose a fontset, or whatever
else) and partake of the pleasures of asterisk-counting seems onerous.
Is
On Sep 28, 2005, at 4:30 AM, YAMAMOTO Mitsuharu wrote:
On 25 Sep 2005 10:20:31 -0400, Adrian Robert
<[EMAIL PROTECTED]> said:
Even in X11, while XLFD is needed at the lowest level to interact
with the windowing system, is it really necessary to expose the user
to it? In the old days whe
> On 25 Sep 2005 10:20:31 -0400, Adrian Robert <[EMAIL PROTECTED]> said:
> Even in X11, while XLFD is needed at the lowest level to interact
> with the windowing system, is it really necessary to expose the user
> to it? In the old days when emacs-X11 was first developed, X11
> users were use
YAMAMOTO Mitsuharu <[EMAIL PROTECTED]> writes:
>>> On Thu, 22 Sep 2005 22:42:41 +0200, Jesper Harder <[EMAIL PROTECTED]> said:
>
>> I think one thing that would be very helpful is to give intructions
>> on how to set up fonts for comprehensive coverage of unicode (if
>> it's even possible).
>
> So
> > screen. I was also trying to maintain backwards compatibility of
> old > XLFDs, which I'm starting to think was unwise. I've made two
> attempts at
> Regarding this, I think it would be good for people working on
> Emacs.app, w32, and Xft to get together and try to figure out what to
> do w
I've updated man/macos.texi.
Thank you.
According to admin/FOR-RELEASE, it is
subject to proofreading by at least two persons before release.
It would be a good idea for two people to check your writing.
I see that nobody is listed so far as having check
> "YAMAMOTO" == YAMAMOTO Mitsuharu <[EMAIL PROTECTED]> writes:
YAMAMOTO> Unfortunately, the URL
YAMAMOTO> ftp://mac-emacs.sourceforge.net/pub/mac-emacs/GNU-fonts.smi.bin
YAMAMOTO> mentioned in mac/INSTALL is not accessible as of today. Does
anyone
YAMAMOTO> know whether it i
> On Thu, 22 Sep 2005 22:42:41 +0200, Jesper Harder <[EMAIL PROTECTED]>
> said:
> I think one thing that would be very helpful is to give intructions
> on how to set up fonts for comprehensive coverage of unicode (if
> it's even possible).
Sorry, I'm not sure if it is possible or not. S
YAMAMOTO Mitsuharu <[EMAIL PROTECTED]> writes:
> I've updated man/macos.texi. According to admin/FOR-RELEASE, it is
> subject to proofreading by at least two persons before release.
> Because this is my first time to edit Texinfo files, there may be some
> "texi"cal and grammatical errors. Corre
> screen. I was also trying to maintain backwards compatibility of old
> XLFDs, which I'm starting to think was unwise. I've made two attempts at
Regarding this, I think it would be good for people working on Emacs.app,
w32, and Xft to get together and try to figure out what to do with the
fon
> On Wed, 21 Sep 2005 23:12:43 -0700, Steven Tamm <[EMAIL PROTECTED]> said:
> It would probably be easier to graft on the parts of the Aqua (sic)
> port into the font/calculation/drawing portions than to convert from
> QDText to ATSU. Unless someone has the time or the inclination to
> implem
To correctly use ATSUI, the way that fonts are cached and handled
would have to change. The cost of creating an ATSUStyle structure is
ridiculously high and a new caching system would have to be added to
maintain performance. Furthermore, the calculations of line height
and character widt
I've updated man/macos.texi. According to admin/FOR-RELEASE, it is
subject to proofreading by at least two persons before release.
Because this is my first time to edit Texinfo files, there may be some
"texi"cal and grammatical errors. Corrections of such errors are
also appreciated.
BTW, there
22 matches
Mail list logo
