From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: List of unresolved issues
Date: Fri, 14 Apr 2000 14:57:41 +0000 [thread overview]
Message-ID: <1000414145741.ZM23428@candle.brasslantern.com> (raw)
In-Reply-To: <200004140818.KAA23909@beta.informatik.hu-berlin.de>
On Apr 14, 10:18am, Sven Wischnowsky wrote:
} Subject: Re: List of unresolved issues
}
} > } > 10187 combining multiple zstyle commands into one
} >
} > Actually, I now think the shell function implementation is fine.
}
} I don't understand why it uses case instead of if/else, though:
Easier to change later if any other options need special-casing. When
I started writing it I thought some might.
} The `zMULTstyle' and the missing `builtin's: I would be against naming
} it just `zstyle' for two reasons: 1) speed in the completion functions
} which don't need this shortcut syntax because it's only for defining
} styles
No problem. Name it something else, alias it back to zstyle, and make
sure the completion autoloads use -U.
} and 2) _complete_help needs to define a zstyle function itself
Too bad we can't declare `local functions[zstyle]'. Pretend I didn't
just suggest that.
} So, I haven't added/committed this because there probably is a better
} name than zmultstyle. Yes?
Is "zstyle+" bad because it would mean a file with a '+' in it's name?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-14 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-14 8:18 Sven Wischnowsky
2000-04-14 14:57 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-13 12:46 Sven Wischnowsky
2000-04-13 15:55 ` Bart Schaefer
2000-04-12 6:14 Bart Schaefer
2000-04-12 15:56 ` Andrej Borsenkow
2000-04-12 20:55 ` Peter Stephenson
2000-04-13 0:26 ` Bart Schaefer
2000-04-13 8:56 ` 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=1000414145741.ZM23428@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).