unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Automatic Compiling
Date: Wed, 30 Apr 2003 11:17:25 +0200	[thread overview]
Message-ID: <84n0i8jqe2.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <b8ns64$e84$1@online.de> (Ulrich Dirr's message of "Wed, 30 Apr 2003 08:58:11 +0200")

"Ulrich Dirr" <ud@art-satz.de> writes:

> At the moment /bin/emacs-21.2 have subdirs /bin, /etc, /info, /lisp,
> /lock (empty), and /site-lisp. I wanted to separate all packages which
> did not come with the standard installation (I used a precompiled bin
> version), e.g. /auctex, /leim, and /mule-ucs). Maybe the best idea is to
> put every local lisp package into /usr/local[/emacs]/site-lisp???

The Unix convention is to have a directory for a package.  The
directory for Emacs could be /usr/local/emacs-21.2.  Then this
directory contains subdirs bin, man, info, lib, share.  The bin
directory contains the programs.

So, the Emacs executable would be /usr/local/emacs-21.2/bin/emacs.

But you have a directory c:/bin (or /c/bin or whatever) which is
named bin but does not contain programs.  Instead, it contains a
subdir emacs-21.2 which contains subsubdirs...

So you could rename /c/bin to /c/sw or /c/local or /c/pkg or
something, and then David wouldn't have been surprised.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)

      reply	other threads:[~2003-04-30  9:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27  9:12 Automatic Compiling Ulrich Dirr
2003-04-27 12:06 ` Kai Großjohann
2003-04-27 16:39 ` David Kastrup
2003-04-28  7:32   ` Ulrich Dirr
2003-04-28  8:27     ` David Kastrup
2003-04-29 14:50       ` Ulrich Dirr
2003-04-29 15:29         ` David Kastrup
2003-04-29 16:16           ` Ulrich Dirr
2003-04-29 20:42             ` David Kastrup
2003-04-30  6:58               ` Ulrich Dirr
2003-04-30  9:17                 ` Kai Großjohann [this message]

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=84n0i8jqe2.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.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).