[#539] A new discussion topic ;-) — Clemens Hintze <c.hintze@...>
Hi all,
[#546] Question concerning modules (1) — clemens.hintze@...
[#548] Bug: concerning Modules! — clemens.hintze@...
[#564] Ruby 1.3.7 — Yukihiro Matsumoto <matz@...>
Ruby 1.3.7 is out, check out:
[#567] New feature request! :-) — clemens.hintze@...
On 6 Aug, Yukihiro Matsumoto wrote:
Hi,
On 6 Aug, Yukihiro Matsumoto wrote:
[#590] Bug in Array#clone! — clemens.hintze@...
Hi,
Hi,
[#600] A `File' is not a `IO'????? — clemens.hintze@...
Hi,
On 10 Aug, Yukihiro Matsumoto wrote:
Hi,
Hi,
Hi,
On 11 Aug, GOTO Kentaro wrote:
Hi,
On 11 Aug, Yukihiro Matsumoto wrote:
Hi,
[#607] How to pass by `new' method of superclass? — clemens.hintze@...
[#626] Next misbehavior (sorry :-) — clemens.hintze@...
Hi,
[#634] ANN: testsupp.rb 0.1 — Clemens Hintze <c.hintze@...>
Hi,
[#637] Backtrace of SIGSEGV — Clemens Hintze <c.hintze@...>
Hi,
Hi,
On 12 Aug, Yukihiro Matsumoto wrote:
Hi,
On 12 Aug, Yukihiro Matsumoto wrote:
Hi,
[#655] Your wish is fulfilled (erhm, almost ;-) — Clemens Hintze <c.hintze@...>
Hi Gotoken,
[#667] How do I use `callcc' — Clemens Hintze <c.hintze@...>
Hi,
[#668] Way to intercept method calls? — Clemens Hintze <c.hintze@...>
Hi,
[#679] Documentation about RD? — Clemens Hintze <c.hintze@...>
Hi,
=begin
On 18 Aug, Toshiro Kuwabara wrote:
Hi,
On 18 Aug, GOTO Kentaro wrote:
Hi,
On 19 Aug, Toshiro Kuwabara wrote:
Hi,
On 19 Aug, Toshiro Kuwabara wrote:
Hi,
Hi,
On 19 Aug, Toshiro Kuwabara wrote:
Hi
Hi,
Hi,
Hi Tosh and all,
Hi,
Hi,
Hi,
Hi,
Hi,
Hi,
Hi,
Hi,
Hi,
On 19 Aug, Yukihiro Matsumoto wrote:
Hi,
On 20 Aug, Toshiro Kuwabara wrote:
Hi,
On 21 Aug, Toshiro Kuwabara wrote:
Hi,
On 21 Aug, Toshiro Kuwabara wrote:
Hi,
Hi,
Hi,
On 24 Aug, Toshiro Kuwabara wrote:
Hi,
I thought people might be interested in this. Here's how I am plugging
On 31 Aug, Jonathan Aseltine wrote:
[#737] RD with multi charset — Minero Aoki <aamine@...>
Hi, I'm Minero Aoki. This is my first mail in this mailling list.
Hi,
Hi,
Hi,
Hi,
On 28 Aug, Minero Aoki wrote:
Hi,
[ruby-talk:00706] Re: Summary of discussion about RD (Re: Docum enta tion about RD?)
Hi,
> > In gotoken's idea, "((<...>))" has tree features (means).
> > (1) Reference to Headlines and Term part of DescList.
> > (2) Link with URL.
> > (3) Reference to Bibliography.
>
> Ah! Now I understand. But I would propose to use `((<...>))' only for
> (2) as <...> at least reminds me on email addresses. To refer to things
> like (1) or (2), I would propose `(([...]))', as references in written
> literature are most often denoted with [...] like in your example below
> ([HF90]). <--- Gotcha! ;-)
>
> Furthermore I think that references like (2) are other beasts as used
> in (1) and (2).
>
> Opinions?
Well... I suppose "((<...>))" has too much feature in gotoken's idea.
It is good idea that we use different brace for reference to Element of Doc
and resource of Internet.
And do we need reference to bibliography?? I don't think so...
> [...]
>
> > Well,so this "((<toshirok@yb3.so-net.ne.jp>))" maybe refers Headline like
> > "== toshirok@yb3.so-net.ne.jp", usage (1).
> > This is a problem of "((<mail address>))".
> > But we can regard String which contains "@" and "." and not contains /\s/
> > as Mail Address probably. Do you think this rule "valid"? and "wished"?
>
> Why restrictive? My proposal perhaps could solve the problem, couldn't
> it? :-)
You may be right.
> [...]
>
> >
> > I can't agree with this suggestion. Maybe, if non-alphanumeric
> > character runs out, we want so much feature that RD cannot accept
> > them.
>
> I didn't make that as proposal! Only to show, the way would be open. If
> there is a way doesn't mean one has to go it, neh? ;-)
Oh, that is my misunderstanding.
> [...]
>
> >
> > I see.
> > But if nobody use "((x ... x))" for Literal Meaning frequently, I think
> > using Inline Verbatim, "(('...'))", is not so bad idea.
> > What do you think?
>
> Ok! You are right :-)
>
> >
> > [...]
> >> Hmm... Why not saying that *every* `=begin <anything>' has to be
> >> ignored by the rdtool? Only plain `=begin' would be accepted. So other
> >> tools could use that feature also, to embed information in multiline
> >> comments.
> >
> > I think this feature of your suggestion is useful and powerful,
> > but too powerful. if we allow this feature, we also come to allow
> > "=begin html" maybe. I'm afraid that such a powerful feature may
> > cause some trouble.
> > I will try to think more and more deep about your suggestion, and
> > make a decision after.
>
> Perhaps you have misunderstood me. Because I didn't any longer propose
> my selective ignore proposal. But I mean to ignore *all* that doesn't
> begin with plain `=begin'.
Oh....
I assumed that your proposal include to require ANY formatter of RD to
have a feature like "-use" and "-notuse" of [ruby-talk:687]. But it is
my misunderstanding. I understand that we use "=begin <something>" for
multiline comment and proper extension of RD formatters in your porposal.
I suppose it is nice.:-)
> [...]
>
> >
> > "@input" originated from sample/rd2html.rb.
> > If you disagree with "@input", I give another choice, "<<< filename".
> > this is like a way of output to File instance, "$> << var", and also
> > like a way of shell redirection, "< filename".
> >
> > But "@input" or "<<< filename" feature has a problem. If you use it,
> > you have to make file even if you want to insert one-line of HTML.:-(
>
> That could be a good motivation to not use it too often, right? ;-)
OK!
> >
> > But do we use "=begin <someting>" only for multiline comment? OK?
> > Even if we use "@input" instead of "=begin html", we should think
> > about extention in feature.
>
> But my point remains standing, I think. *Now* we have no need for a
> certain `=begin <something>'. So rd2xxx should ignore all such
> comments. It should only work with, what is intended for it to work.
>
> >
> > And gotoken suggested to use pair of "=begin <something>" and
> > "=end <something>" in [ruby-list:16142].
>
> If in future we get a certain `=begin <something>' we could begin to
> take it into consideration with rd2xxx. But then we should only again
> only look for `=begin' and that special `=begin <something>'. All
> others are ignore!
>
> What `rd2xxx' doesn't know, should be ignored. So we are free for
> extension not coming from the `rdtool' direction.
>
> Opinions?
Sorry, my explanation wasn't enough.
In Goto's proposal, we should write "<something>" not only after "=begin"
but also after "=end" to make sure and to show that text between
"=begin <something>" and "=end <something>" is NOT RD.
This is proposal not for semantics but for grammar.
---
Tosh