unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: ken <gebser@speakeasy.net>
Subject: Re: Installing mew (editing Makefile.in)
Date: Wed, 13 Sep 2006 20:44:36 -0400	[thread overview]
Message-ID: <4508A5F4.4080200@speakeasy.net> (raw)
In-Reply-To: <1158176051.025364.132680@m73g2000cwd.googlegroups.com>

Ryo wrote:
> ken wrote:
> [. . .]
>> Thanks very much, Ryo.  I hope mew works.  I've just downloaded and
>> untarred mew-5.1 and know I need to edit the values of some variables in
>> Makefile.in:
>>
>> prefix=@prefix@
>> exec_prefix=@exec_prefix@
>> libdir=@libdir@
>> datadir=@datadir@
>> infodir=@infodir@
>>
>> These are very much standard variables; I've installed emacs from a
>> tarball several times before and it's always been a guessing game,
>> trying to figure out what the values of these should be.  This guessing
>> game is complicated a bit more this time because mew is to work with an
>> installation of emacs which was installed, not for the entire
>> machine/system, but just for one user.  I.e., emacs v.22.0.50.1 was
>> installed under a user's $HOME just for the use of this one user.
> 
> Brave you, Ken. :) I've given up installing emacs for myself for a
> long time, so I'm afraid I can't help you here.  I still install
> small packages from tarballs or sources from time to time, but
> big ones like emacs and TeX are too time-consuming to me.  I use
> Debian GNU/Linux, where most things are available in the form of
> binary packages.  Add-ons to emacs (such as mew) are provided as
> separate packages, which are installed for various versions emacs
> (xemacs, emacs20, emacs21, etc.) automatically.  I know this
> doesn't install things under your home directory. 

I used to install everything from tarballs.  The first Linux I ever
installed, Slackware, was nothing but tarballs.  (It took two or three
weeks to download the distro-- using a 2400bd modem-- and then a day to
install and configure!)  I think since tarballs was all there was and
*everyone* was using them, the documentation was better.  You could see
and understand much better what was going on and it was easier to fix
things that didn't go right.  But Linux systems have gotten more complex
while, at the same time, the documentation has gotten worse, so much so
that it's just not fun anymore.  And it's not just me saying this.  All
my old Linux buddies say the same.


> 
> Anyway, I don't know if it's of any help to you, but I found elisp
> files and their byte-compiled versions of mew in
> /usr/share/emacs21/site-lisp/mew/ .  I hope experts on emacs will
> help you.

Thanks.  Yeah, that sounds like where they should go... normally.  But
again, I'm installing, not for the whole system, but just for the use of
one user.  So the whole install should go under that one user's $HOME.
So the site-lisp directory is at ~/linux/tarballs/emacs/site-lisp/.
Well, so I guess after I install mew there should be a mew directory
there.  We'll see how that goes.


> 
> Regards,
> Ryo

Thanks, Ryo.

  parent reply	other threads:[~2006-09-14  0:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  4:28 emacs MUAs with working smtp authentication? Bill White
2006-08-30  9:24 ` Peter Dyballa
2006-08-30  9:34 ` Alok G. Singh
2006-08-30 10:27 ` Phillip Lord
2006-08-30 12:33 ` Eli Zaretskii
     [not found] ` <mailman.6017.1156941211.9609.help-gnu-emacs@gnu.org>
2006-08-30 14:39   ` Bill White
2006-08-30 17:01     ` Eli Zaretskii
2006-08-30 20:41     ` Ralf Angeli
2006-08-31 11:11   ` Phillip Lord
2006-09-01  8:53     ` Eli Zaretskii
2006-09-01 14:58       ` ken
2006-09-01 17:04         ` Eli Zaretskii
     [not found]         ` <mailman.6141.1157130256.9609.help-gnu-emacs@gnu.org>
2006-09-04 10:42           ` Phillip Lord
     [not found]     ` <mailman.6127.1157100814.9609.help-gnu-emacs@gnu.org>
2006-09-01 11:43       ` Phillip Lord
2006-09-01 17:44       ` Ralf Angeli
2006-09-04  6:39     ` Patricia J. Hawkins
2006-09-06  2:35 ` Ryo
2006-09-06  3:23   ` Eli Zaretskii
2006-09-13 18:04   ` Installing mew (editing Makefile.in) ken
     [not found]   ` <mailman.6890.1158170711.9609.help-gnu-emacs@gnu.org>
2006-09-13 19:34     ` Ryo
2006-09-13 20:15       ` Peter Dyballa
2006-09-14  0:44       ` ken [this message]
2006-09-13 22:32     ` Miles Bader
2006-09-14  0:24       ` ken
     [not found]       ` <mailman.6908.1158193497.9609.help-gnu-emacs@gnu.org>
2006-09-14  1:02         ` Miles Bader
     [not found]           ` <4508AF57.9070905@speakeasy.net>
     [not found]             ` <fc339e4a0609131848w705ed1den1b57dd8a2e2942a4@mail.gmail.com>
2006-09-15  1:39               ` ken
2006-09-15  7:58                 ` Peter Dyballa
2006-09-18 11:20 ` emacs MUAs with working smtp authentication? Paul Puschmann

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=4508A5F4.4080200@speakeasy.net \
    --to=gebser@speakeasy.net \
    /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).