From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Style mechanism discussion
Date: Fri, 10 Dec 1999 09:07:44 +0100 (MET) [thread overview]
Message-ID: <199912100807.JAA19359@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Bart Schaefer's message of Thu, 9 Dec 1999 17:06:38 -0800 (PST)
Bart Schaefer wrote:
> On Thu, 9 Dec 1999, Peter Stephenson wrote:
>
> > Sven Wischnowsky wrote:
> > > Another question is whether we should at least try to group the styles
> > > in some sensible way. Probably even using subsections. Opinions?
> >
> > As long as they've got obvious names, I don't think it matters. Calling
> > things e.g. section.foo and section.bar is only better than foo and bar if
> > section is really adding to the information, and even in that case it's
> > probably easier just to change the name to section_foo and section_bar ---
> > I don't think use of different namespaces is really necessary here. Unless
> > I've missed the point of this.
>
> I think Sven is talking entirely about organizing the documentation into
> sections, not renaming the styles themselves.
That's what I meant. Putting things together that belong together.
Like auto-description+format+verbose or the styles that are now used
on a per-group or per-match basis. Should also make it easier to
document how they are used without repeating it too often.
I haven't really tried to categorize them yet, though.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-12-10 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-10 8:07 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-12-09 10:35 PATCH: cleanup Sven Wischnowsky
1999-12-09 23:47 ` Style mechanism discussion Peter Stephenson
1999-12-10 1:06 ` Bart Schaefer
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=199912100807.JAA19359@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).