all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Nice fonts for emacs 22 GTK on Linux ?
Date: Fri, 08 Feb 2008 14:51:57 +1100	[thread overview]
Message-ID: <87ve50gl5u.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: f474dd72-8a82-431b-b349-9b7612e42ad2@n20g2000hsh.googlegroups.com

Brian Adkins <lojicdotcom@gmail.com> writes:

> On Feb 6, 6:38 pm, Nick Roberts <nick...@snap.net.nz> wrote:
>>  > I used this branch:
>>  >
>>  > cvs -z3 -d:pserver:anonym...@cvs.savannah.gnu.org:/sources/emacs co -r emacs-unicode-2 emacs
>>  >
>>  >
>>  > Details here:
>>  >
>>  >http://www.emacswiki.org/cgi-bin/wiki/XftGnuEmacs
>>
>> If you check that link it points out that emacs-unicode-2 has recently been
>> merged to the trunk and that
>>
>> cvs -z3 -d:pserver:anonym...@cvs.savannah.gnu.org:/sources/emacs co emacs
>>
>> should be enough now.
>>
>> To update from the trunk, instead ofemacs-unicode-2, just do
>>
>> cvs update -A
>>
>> as further Unicode development will happen there.
>>
>> --
>> Nick                                          http://www.inet.net.nz/~nickrob
>
> Thanks guys! I don't know how I got the impression that the emacss22
> package was all I needed - what a frustrating experience. By the way,
> if someone could edit that wiki page to make it more clear, it might
> be helpful. As I explained in my blog post:
>

Hi Brian. You write a nice blog and obviously have good communication
skills. Given that emacswiki is a eh wiki and given you know where it
could be improved, why not just jump in an do it?

> http://lojic.com/blog/2008/02/07/nice-fonts-for-gnu-emacs-on-ubuntu-linux/
>
> After hours of Googling, I became too hasty, and when I read the
> statement:
>
> "Note: Since the emacs-unicode-2 branch which had the xft support is
> merged into trunk, the current page is obsolete."
>
> I thought it applied to the entire wiki page even though the correct
> solution immediately follows that statement. It was my mistake, but it
> may happen to others also. How about simply removing the obsolete
> information, or moving it to an archived page?
>
> Also, can this information be put on the main emacs page?:
>
> http://www.gnu.org/software/emacs/
>
> I'm not sure making people work so hard to get nice fonts on emacs is
> such a good idea :(
>
> One last question. How bleeding edge is 23.0.60.2 ? For my current
> research purposes, it's not a problem, but if I do end up switching
> and relying on emacs for my day-to-day editing needs, is it fairly
> stable?
>
> Thanks,
> Brian Adkins

I've been running CVS emacs for quite some time and update usually every
week or so. Generally, I've found no problems and its very stable - you
may get minor niggles from time to time. 

What I tend  to do is run two cvs working areas and alternate between
them. If the latest version is less stable than the version I already
had, I can switch back to it. 

Tim

-- 
tcross (at) rapttech dot com dot au


  parent reply	other threads:[~2008-02-08  3:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 22:15 Nice fonts for emacs 22 GTK on Linux ? Brian Adkins
2008-02-06 22:50 ` Bill O'Connor
2008-02-06 23:38   ` Nick Roberts
2008-02-06 23:45   ` Peter Dyballa
     [not found]   ` <mailman.7067.1202341142.18990.help-gnu-emacs@gnu.org>
2008-02-07 16:21     ` Brian Adkins
2008-02-07 16:45       ` Peter Dyballa
2008-02-07 17:17       ` Tom Rauchenwald
     [not found]       ` <mailman.7119.1202404821.18990.help-gnu-emacs@gnu.org>
2008-02-07 17:57         ` Brian Adkins
2008-02-07 19:33           ` Joel J. Adamson
2008-02-08  3:51       ` Tim X [this message]
2008-02-08 14:32         ` Joel J. Adamson
2008-02-09  2:00         ` Xavier Maillard
2008-02-06 22:53 ` Tom Rauchenwald
     [not found] ` <mailman.7063.1202338362.18990.help-gnu-emacs@gnu.org>
2008-02-06 23:11   ` Jason Rumney

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=87ve50gl5u.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.