From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: completion grouping
Date: Fri, 5 Nov 1999 07:20:29 +0000 [thread overview]
Message-ID: <991105072029.ZM29130@candle.brasslantern.com> (raw)
In-Reply-To: <199911040932.KAA11903@beta.informatik.hu-berlin.de>
On Nov 4, 10:32am, Sven Wischnowsky wrote:
} Subject: Re: completion grouping
}
} Bart Schaefer wrote:
}
} > I'm also never sure what to expect from "sorted by priority." In this
} > case a smaller number is a higher priority, right? But a negative
} > number is treated as bigger than any positive one? That's a bit weird.
} > Or am I misunderstanding?
}
} No. Only tags with a positive (or zero) priority are used and then
} smaller numbers mean higher priorities (hm, maybe we should change
} that if people think that that would feel more natural).
Not necessarily "more natural."
} > } comptag option+='*dvi*=1'
} > }
} > } the `+=' means that the definition is prepended to the already
} > } existing definition
} >
} > Hrm. I would have expected += to *append* rather than *prepend* (my
} > C++ is showing).
}
} Looking at my mail again I noticed that I forgot to mention that `+='
} prepends and `=+' appends. With that said this hopefully looks more
} sensible ;-)
Hmm.
} But I'd like think about changing this function anyway. I.e. I hope to
} find a somewhat easier interface. Currently this is still too near to
} the way things are stored in `$comptags' and I think the user shouldn't
} have to worry/know about the internal representation.
I don't see how you can avoid having the user know *something* about at
least the ordering of the alternatives for a given tag, so although I'm
not entirely happy with the syntax I don't mind the semantics.
} we probably should think about some standard structure for defining
} styles. Things like multiple styles (separated by commas?), styles
} with values (`[style_a=foo,style_b=bar]' or something like that). If
} this turns out to be useful, I would like change `_tags' to report
} styles in a format that is easier to parse in the calling functions.
I repeat my suggestion that this be enveloped in a mini-language, as with
the _arg_compile function.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-11-05 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-04 9:32 Sven Wischnowsky
1999-11-05 7:20 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-11-05 15:40 Sven Wischnowsky
1999-11-05 10:52 completion grouping (PLEASE read this) Sven Wischnowsky
1999-11-05 14:54 ` completion grouping Oliver Kiddle
1999-11-04 13:50 Sven Wischnowsky
1999-11-04 17:46 ` Bart Schaefer
1999-11-03 13:41 Sven Wischnowsky
1999-11-03 17:12 ` 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=991105072029.ZM29130@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).