[#3228] Core support for Gems, and namespace — "Luke A. Kanies" <luke@...>

Hi all,

21 messages 2004/07/27
[#3230] Re: Core support for Gems, and namespace — Austin Ziegler <halostatue@...> 2004/07/27

On Tue, 27 Jul 2004 11:39:08 +0900, Luke A. Kanies <luke@madstop.com> wrote:

[#3234] Re: Core support for Gems, and namespace — "Luke A. Kanies" <luke@...> 2004/07/27

On Tue, 27 Jul 2004, Austin Ziegler wrote:

[#3238] Re: Core support for Gems, and namespace — Austin Ziegler <halostatue@...> 2004/07/27

On Wed, 28 Jul 2004 00:14:29 +0900, Luke A. Kanies <luke@madstop.com> wrote:

Re: [doc] Inconsistent indentation of rdoc entries ?

From: Dave Thomas <dave@...>
Date: 2004-07-05 22:01:22 UTC
List: ruby-core #3139
On Jul 5, 2004, at 13:23, Johan Holmberg wrote:
> I think it would be good to use one type of indentation
> systematically for the documentation of all methods.

I agree absolutely

>
> Personally I prefer alternative 1) above.
> When 2 or more spaces are used, it becomes increasingly difficult to
> see visually how many spaces should actually be used, for example in
> a description with several paragraphs with normal text, and
> interspersed examples (like Array#pack).

In general I have tried to have directives (such as call-seq) line up 
with the body text, and code examples indented 2 spaces past that. 
However, I know that the stuff in there now isn't 100% consistent. 
Partly that's lazy editing on my part (the conversion from the original 
TeX was at times a tad ugly), and partly that's just a set of 
oversights.

Apart from fixing errors, I'm not sure it's worth anyone's time to go 
through and change existing entries just to reset margins. However, if 
anyone is already editing an entry and wants to make the margins 
consistent, that'd be great..


Cheers

Dave


In This Thread