all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "John Wells" <lists@sourceillustrated.com>
To: help-gnu-emacs@gnu.org
Subject: Load path and custom compiling cvs on Debian
Date: Fri, 14 Dec 2007 12:46:10 -0500	[thread overview]
Message-ID: <44dddf400712140946l5df0fe41jf73948e7552467bd@mail.gmail.com> (raw)

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.

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?

Sorry for so many questions...I'm learning quickly, but there's a lot to learn!

Thanks!
John

             reply	other threads:[~2007-12-14 17:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14 17:46 John Wells [this message]
2007-12-14 18:23 ` Load path and custom compiling cvs on Debian 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
     [not found] <mailman.5036.1197654377.18990.help-gnu-emacs@gnu.org>
2007-12-15  2:43 ` 方旭亮
2007-12-17  9:05 ` Tim X
2007-12-17 10:04   ` Thierry Volpiatto
2007-12-17 14:47   ` Sven Joachim
2007-12-19  7:26     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44dddf400712140946l5df0fe41jf73948e7552467bd@mail.gmail.com \
    --to=lists@sourceillustrated.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.
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.