Bug 229165 - Enable xft support for emacs
Enable xft support for emacs
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: emacs (Show other bugs)
rawhide
All Linux
medium Severity low
: ---
: ---
Assigned To: Chip Coldwell
:
: 231769 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-18 22:12 EST by Stephen
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-22 12:07:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stephen 2007-02-18 22:12:54 EST
Please configure emacs with the additional options:

  --enable-font-backend --with-xft

to enable true type font support.

The new font backend is only enabled if emacs is started as:

  emacs --enable-font-backend

So should be safe.
Comment 1 Alexandre Oliva 2007-02-19 02:47:23 EST
Is this about xemacs?  I don't see any such options in GNU emacs' configure
script sources or documentation.
Comment 2 Stephen 2007-02-19 09:18:39 EST
I think this should be available in the new emacs 22 (as shipped in rawhide).

http://www.emacswiki.org/cgi-bin/wiki/XftGnuEmacs

Did I get this wrong? Has this feature been bumped to emacs 23?
Comment 3 dann 2007-02-22 11:41:04 EST
(In reply to comment #2)
> I think this should be available in the new emacs 22 (as shipped in rawhide).

No, it is not. Emacs-23 will have it after the emacs-unicode-2 branch will be
merged to emacs mainline... 


Comment 4 Stephen 2007-02-22 12:07:16 EST
OK. Waiting for emacs 23...
Comment 5 Bill Nottingham 2007-03-02 12:45:34 EST
Moving to 'devel' as discussed on
https://www.redhat.com/archives/fedora-devel-list/2007-March/msg00095.html.
Comment 6 Chip Coldwell 2007-03-12 10:11:09 EDT
*** Bug 231769 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.