zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: zmodload command-line switches and doc organization
Date: Fri, 30 Apr 1999 16:18:16 +0200 (MET DST)	[thread overview]
Message-ID: <199904301418.QAA15941@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Fri, 30 Apr 1999 03:57:55 -0700


Bart Schaefer wrote:

> I'd like to suggest some changes to the options to zmodload.  Below is
> formatted text of the reorganized info documentation.  The idea was to
> add a -b option (for "builtin") to go with the relatively new -c and -p
> options, and then to make -a consistently mean "autoload" as -u means
> un(load/define/whatever).  So instead of -a/-c/-p and -au/-cu/-pu, we
> have -ab/-ac/-ap mirrored by -ub/-uc/-up.  (I left -a and -au because
> they've been around for so long, but changed -L to not generate them.)

YES. (I just didn't dare to do that...)

> It's a three-line deletion in my patched modules.c plus a few characters
> knocked out of the doc to make it -b/-c/-p and -ub/-uc/-up, if that's
> preferable; however, my thought was that we could make -b/-c/-p (with
> neither -a nor -u) perform a listing function, e.g.
> 
>      zmodload -b [ -L ] BUILTIN ...
>            For each BUILTIN, list the module from which it was loaded
> 	   (if any).  With -L, list in the form of zmodload commands.
> 
> Similarly for -c and -p.  However, I haven't implemented that yet.

Sounds good.

> No patch yet, I want reaction to the proposed change before I send one.
> Independent of the change in switches, what do you think of the doc
> layout?

Unfamiliar (but that doesn't matter) and much more readable and
understandable, good.


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-04-30 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-30 14:18 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-04-30 10:57 Bart Schaefer
1999-04-30 11:24 ` Peter Stephenson

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=199904301418.QAA15941@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.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).