Opened 13 years ago
Closed 13 years ago
#33752 closed defect (duplicate)
emacs slow on start + no anti-aliased font anymore
Reported by: | eric.lebigot@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.4 |
Keywords: | emacs, x11, fonts | Cc: | duncan.rumbold@…, ryandesign (Ryan Carsten Schmidt) |
Port: | emacs |
Description
Today, I updated all my installed ports, and emacs (23) is now very slow on start (a lot of system time spent, not user time) and my usual font (-*-fixed-*-*-*-*-5-*-*-*-*-*-*-*) is not antialiased anymore.
Is there a new package that I should install in order to get the font back to its antialiased form? would this likely solve the new slow start issue?
Change History (5)
comment:1 Changed 13 years ago by duncan.rumbold@…
comment:2 follow-up: 3 Changed 13 years ago by eric.lebigot@…
Thank you so much, Duncan. You nailed it down: I observe the same things as you; in particular, reverting fontconfig to 2.8 solved the problems. I'll file a bug report for fontconfig.
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
comment:4 Changed 13 years ago by eric.lebigot@…
This is now fixed (I'm not sure whether I can mark this ticket as not being a "new defect" anymore). See #33769.
comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | duncan.rumbold@… ryandesign@… added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Replying to eric.lebigot@…:
This might have something to do with the fontconfig upgrade from 2.8.0 to 2.9.0. I've found that all my X applications (awesome, rxvt-unicode, vim) are taking in the order of 10 - 20 seconds to start since this upgrade. However, if I reactivate the old fontconfig instead (2.8.0) then all is OK. You can test this by seeing how long the font cache takes to update with an 'fc-cache -vf'. I'm finding that it doesn't seem to create any cache files, thus fc-cache takes in the order 10 - 20 seconds every time because it doesn't think it's cached anything before. I'm sure that this time corresponds to the new time that applications take to launch.
Duncan.