From: Leo <sdl.web@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Copy things out of Emacs
Date: Thu, 24 May 2007 11:09:19 +0100 [thread overview]
Message-ID: <m2sl9mzg6o.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: 87hcq27fpe.fsf@lion.rapttech.com.au
----- Tim X (2007-05-24) wrote:-----
> Hmm, that must be some issue with the unicode branch of emacs 22. I'm
> running the main branch and have been for a long time now. I was
> running the older X toolkit version, but have switched to the GTK
> version about 6 weeks ago. I run almost exclusively within native X
> and have no stability problems or any load issues. I've had perhaps
> one or two crashes in over 18 months and some problems with tramp
> (which turned out to be due to an add-on package. I live in emacs
> pretty much every day all day, at work and at home.
Actually I have just upgraded from the main branch. I have now converted
all .el to Emacs 23. It takes time to go back.
[...]
> As the unicode branch is still under active development and given the
> likely impact of the changes in that branch, I suspect you will find
> many packages that don't quite work correctly. Changing something as
> large as emacs to use unicode is not trivial and there are many emacs
> packages that have been written with the assumption of character sets
> being single byte etc.
However it seems to under-manpower to fix bugs.
> I have found the UTF-8 support in the main branch of eamcs 22 to be
> very good and reliable. If that is enough for you, I'd suggest trying
> the main 22 branch within an xterm and seeing if that improves the
> situation for you (is the XFT stuff even relevant if your running
> within an xterm anyway? wouldn't the xterm be handling all of that?)
>
> Tim
It might be time to try the multi-tty branch ;)
--
Leo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)
next prev parent reply other threads:[~2007-05-24 10:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.831.1179525659.32220.help-gnu-emacs@gnu.org>
2007-05-18 22:37 ` Copy things out of Emacs poppyer
2007-05-18 23:36 ` Leo
2007-05-19 4:30 ` Tim X
2007-05-19 7:13 ` Leo
[not found] ` <mailman.851.1179558915.32220.help-gnu-emacs@gnu.org>
2007-05-19 8:07 ` Tim X
2007-05-22 20:06 ` Leo
2007-05-22 21:09 ` Peter Dyballa
2007-05-23 22:37 ` Xavier Maillard
2007-05-23 22:59 ` Peter Dyballa
2007-05-24 21:45 ` Xavier Maillard
[not found] ` <mailman.1031.1179868194.32220.help-gnu-emacs@gnu.org>
2007-05-22 21:17 ` poppyer
2007-05-23 4:55 ` Tim X
[not found] ` <mailman.1020.1179864472.32220.help-gnu-emacs@gnu.org>
2007-05-23 4:47 ` Tim X
2007-05-23 17:29 ` Leo
2007-05-23 22:36 ` Xavier Maillard
[not found] ` <mailman.1094.1179941717.32220.help-gnu-emacs@gnu.org>
2007-05-24 9:07 ` Tim X
2007-05-24 10:09 ` Leo [this message]
2007-05-24 21:45 ` Xavier Maillard
[not found] ` <mailman.1199.1180044455.32220.help-gnu-emacs@gnu.org>
2007-05-25 5:08 ` Tim X
2007-05-18 21:58 Leo
2007-05-22 4:38 ` Xavier Maillard
2007-05-22 23:49 ` John Steele Scott (t-tec)
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2sl9mzg6o.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@gmail.com \
--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.
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).