zsh-workers
 help / color / mirror / code / Atom feed
From: Raúl Núñez de Arenas Coronado <dervishd@jazzfree.com>
To: zsh-workers@sunsite.dk
Subject: How about MODDIR being configure'able?
Date: Mon, 15 Oct 2001 15:44:07 +0200	[thread overview]
Message-ID: <E15t82J-0007k1-00@DervishD> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]

    Hello all :))

    I'm new to this list an a-kinda-new for ZSH, and I would like to
follow and contribute to its development.

    I have a suggestion (I don't remember if I posted this a few
months ago, when I first used ZSH), for the next version 4.0.3:

    I would like to set up the MODDIR (directory where binary modules
of ZSH reside) through 'configure', and not by defining MODDIR prior
to compile and install using make.

    Defining the variable is quite error prone and I think that the
modules directory should be fully configurable.

    How about it?. I'm not familiar to autoconf, so I'm afraid I
cannot make the appropriate patches.

    Moreover, there is a call to mktemp that should be replaced with
a call to mkstemp in 'utils.c' for safety.

    BTW, is there any place where I can get the current development
version of ZSH for testing?

    That's all, an thanks a lot for ZSH :)

    Raúl


             reply	other threads:[~2001-10-15 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-15 13:44 Raúl Núñez de Arenas Coronado [this message]
2001-10-15 15:33 ` Bart Schaefer
2001-10-15 17:41   ` Clint Adams
2001-10-16  3:42     ` O_EXCL (was: How about MODDIR being configure'able?) Wayne Davison
2001-10-16  4:12       ` Clint Adams
2001-10-16 11:58   ` How about MODDIR being configure'able? Peter Stephenson
2001-10-16 18:35 Raúl Núñez de Arenas Coronado

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=E15t82J-0007k1-00@DervishD \
    --to=dervishd@jazzfree.com \
    --cc=zsh-workers@sunsite.dk \
    /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 public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).