From: fxlzju@gmail.com (方旭亮)
To: help-gnu-emacs@gnu.org
Subject: Re: Load path and custom compiling cvs on Debian
Date: Sat, 15 Dec 2007 10:43:11 +0800 [thread overview]
Message-ID: <873au43cg0.fsf@step.cesc> (raw)
In-Reply-To: mailman.5036.1197654377.18990.help-gnu-emacs@gnu.org
"John Wells" <lists@sourceillustrated.com> writes:
> Guys,
>
> I've learned that anti-aliased fonts don't appear to be supported yet
> on 22, and I've also found that compiling the unicode branch out of
> CVS enables this support.
>
> I've done the compile and it works great...fonts look wonderful.
> However, the problem is the custom compiled emacs doesn't find all my
> pre-installed Debian packaged modes and utilities, like ecb,
> ruby-mode, etc.
where is your unicode version emacs install? /usr/local/share ?
>
> It appears that the dpkg's put the various installed files in:
>
> /usr/share/emacs/site-lisp
> /usr/share/emacs22/site-lisp
>
> Then, when I start emacs, these are already there, loaded.
>
> Can someone tell me what configurations settings I need to do to make
> these work with my custom compile? Is it a ./configure option? Is it
> some central emacs config file? Can I inspect where my custom compile
> is looking for modes easily through emacs itself?
>
you can put all the other modes i.e ecb ruby-mode to you home ,
.emacs.d/site-lisp
then load this in your .emacs file,so whenever you install other
version emacs, it can find those
> Sorry for so many questions...I'm learning quickly, but there's a lot to learn!
>
> Thanks!
> John
>
>
--
The designer knows he was arrived at perfection not when there is no
longer anything to add,but when there is no longer anything to take away
next parent reply other threads:[~2007-12-15 2:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5036.1197654377.18990.help-gnu-emacs@gnu.org>
2007-12-15 2:43 ` 方旭亮 [this message]
2007-12-17 9:05 ` Load path and custom compiling cvs on Debian Tim X
2007-12-17 10:04 ` Thierry Volpiatto
2007-12-17 14:47 ` Sven Joachim
2007-12-19 7:26 ` Tim X
2007-12-14 17:46 John Wells
2007-12-14 18:23 ` Peter Dyballa
2007-12-14 19:44 ` John Wells
2007-12-14 22:47 ` Peter Dyballa
2007-12-15 4:28 ` Kevin Rodgers
[not found] ` <mailman.5054.1197784667.18990.help-gnu-emacs@gnu.org>
2007-12-18 7:09 ` Tim X
2007-12-18 11:46 ` Richard G Riley
2007-12-19 7:31 ` Tim X
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=873au43cg0.fsf@step.cesc \
--to=fxlzju@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).