On Sun, 07 Feb 2010 05:49:28 +, Nobody wrote:
>> The size-8 tabs look really bad in an editor configured with tab size 4,
>> as is common in Windows. I'm concluding that the CPython programmers
>> configure their Visual Studio's to *nix convention.
>
> 8-column tabs aren't a "*nix convention"
Aahz:
> BTW, in case anyone is confused, it's "svn blame" vs "cvs annotate".
Possibly earlier versions of SVN only supported "blame" but the
variants "annotate", "ann", and "praise" all work with the version of
SVN (1.6.5) I have installed.
Neil
--
http://mail.python.org/mailman/listinfo/
On 2/7/2010 7:39 AM, Steve Holden wrote:
Clearly written by someone who has never *used* a mechanical typewriter.
The original mechanisms had "tab set" and "tab clear" keys, so you had
variable tabbing according to the needs of the particular document you
were working on. Look under "T" in
h
Dennis Lee Bieber wrote:
> On Sun, 07 Feb 2010 05:49:28 +, Nobody
> declaimed the following in gmane.comp.python.general:
>
>
>> 8-column tabs aren't a "*nix convention"; that's been the norm since
>> the mechanical typewriter.
>>
> Really? None of the various Royal, Remington, and Oli
Nobody wrote:
> On Sat, 06 Feb 2010 21:31:52 +0100, Alf P. Steinbach wrote:
>
>> The size-8 tabs look really bad in an editor configured with tab size 4,
>> as is common in Windows. I'm concluding that the CPython programmers
>> configure their Visual Studio's to *nix convention.
>
> 8-column tab
In article ,
Neil Hodgson wrote:
>Alf P. Steinbach:
>>
>> Anyways, I would suggest converting all those tabs to spaces, as e.g.
>> the Boost library project does -- no tabs allowed.
>
> This would damage the usefulness of source control histories (svn
>annotate) as all of the converted lines
* Nobody:
On Sat, 06 Feb 2010 21:31:52 +0100, Alf P. Steinbach wrote:
The size-8 tabs look really bad in an editor configured with tab size 4,
as is common in Windows. I'm concluding that the CPython programmers
configure their Visual Studio's to *nix convention.
8-column tabs aren't a "*nix
On Sat, 06 Feb 2010 21:31:52 +0100, Alf P. Steinbach wrote:
> The size-8 tabs look really bad in an editor configured with tab size 4,
> as is common in Windows. I'm concluding that the CPython programmers
> configure their Visual Studio's to *nix convention.
8-column tabs aren't a "*nix conventi
Le Sat, 06 Feb 2010 22:26:55 +, Benjamin Peterson a écrit :
> Neil Hodgson gmail.com> writes:
>>This would damage the usefulness of source control histories (svn
>> annotate) as all of the converted lines would show this recent cosmetic
>> change rather than the previous change which is li
Alf P. Steinbach start.no> writes:
> Anyways, I would suggest converting all those tabs to spaces
This has been discussed to death of Python-dev. We use spaces for all new files
and tabs for historical reasons in old files. Mixed ones should be converted one
way or the other.
>
> That's much m
Neil Hodgson gmail.com> writes:
>This would damage the usefulness of source control histories (svn
> annotate) as all of the converted lines would show this recent cosmetic
> change rather than the previous change which is likely to be a
> substantive modification.
That's not completely true
"Alf P. Steinbach" writes:
> Just trying to delve into the CPython source code.
>
> Pleasant surprise: while e.g. the gcc compiler is written in K&R C
> (1975 style C), CPython seems to be written in almost modern C (1989
> and on).
>
> But, hey, TABS used for indenting, combined haphazardly and
Alf P. Steinbach:
> The size-8 tabs look really bad in an editor configured with tab size 4,
> as is common in Windows. I'm concluding that the CPython programmers
> configure their Visual Studio's to *nix convention.
Most of the core developers use Unix.
> Anyways, I would suggest converting
* Andrej Mitrovic:
On Feb 6, 9:31 pm, "Alf P. Steinbach" wrote:
Just trying to delve into the CPython source code.
Pleasant surprise: while e.g. the gcc compiler is written in K&R C (1975 style
C), CPython seems to be written in almost modern C (1989 and on).
But, hey, TABS used for indenting
On Feb 6, 9:31 pm, "Alf P. Steinbach" wrote:
> Just trying to delve into the CPython source code.
>
> Pleasant surprise: while e.g. the gcc compiler is written in K&R C (1975 style
> C), CPython seems to be written in almost modern C (1989 and on).
>
> But, hey, TABS used for indenting, combined h
Just trying to delve into the CPython source code.
Pleasant surprise: while e.g. the gcc compiler is written in K&R C (1975 style
C), CPython seems to be written in almost modern C (1989 and on).
But, hey, TABS used for indenting, combined haphazardly and randomly with SPACES
used for indenti
16 matches
Mail list logo
