Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #82223 > unrolled thread

Re: Maintaining Maximum Line Length When Using Tabs Instead of Spaces?

Back to article view | Back to comp.lang.python

Contents

  Re: Maintaining Maximum Line Length When Using Tabs Instead of Spaces? sohcahtoa82@gmail.com.remove-cdt-this - 2014-12-09 11:32 -0500
    Re: Maintaining Maximum Line Length When Using Tabs Instead of Spaces? "Ben Finney" <ben.finney@1:249/999.remove-cdt-this> - 2014-12-09 11:32 -0500
    Re: Maintaining Maximum Line Length When Using Tabs Instead of Spaces? "Dave Angel" <dave.angel@1:249/999.remove-cdt-this> - 2014-12-09 11:32 -0500

#82223 — Re: Maintaining Maximum Line Length When Using Tabs Instead of Spaces?

  To: jtan
> On Mon, Dec 8, 2014 at 10:15 AM, Aahan Krish <kr...@aahan.me> wrote:
> My understanding from talking to different people is that many do use
> 
> tabs (instead of spaces) for indentation in their code.
> 
> 
> 
> My question is to them (because I want to use tabs too) is: how do you
> 
> maintain a line-length of 79 characters?
> 
> 
> 
> E.g. scenario: The tab setting in your editor could be 2 or 4, and in
> 
> other developer's browser it could be 8. The code will be longer than
> 
> 79 chars in the latter's editor.
> 
> 
> 
> I want to know if it's at all possible or if you use some simple and
> 
> realistic (practical) hacks.
> 
> 
> 
> *PS: Please avoid, "That's why you should use spaces," type of
> 
> comments. I would like to avoid flame wars.*
> 
> 
> 
> TY,
> 
> Aahan

On Sunday, December 7, 2014 6:26:01 PM UTC-8, jtan wrote:
> One reason why you would want max length 79 is because of working with 
terminals.  Maybe ssh to you server and check how many spaces are consumed by a 
tab?  In my boxes, it is usually 1 tab = 8 spaces.  So perhaps just use that 
setting in your editor?


My terminals are 120 columns wide.

Are there still people that are limiting their terminals to 80 columns?  If so, 
why?  I mean, I can understand if you're running on an ancient square monitor, 
but I see no reason to limit your terminal to 80 columns if you're running any 
sort of window 
environment on monitor with a horizontal resolution greater than 1280.

"Because that's how we've always done it!" is a pretty shitty reason to 
continue doing something.

--- SoupGate-Win32 v1.05
 * Origin: <SpaceSST.BBS.Fidonet<>NNTP.gateway.@.piz.noip.me> (1:249/999)
--- Synchronet 3.15b-Win32 NewsLink 1.92
SpaceSST BBS Usenet <> Fidonet Gateway

[toc] | [next] | [standalone]

#82226

  To: sohcahtoa82@gmail.com
sohcahtoa82@gmail.com writes:

> My terminals are 120 columns wide.

Mine are wider. So what?

> Are there still people that are limiting their terminals to 80
> columns?

I don't know. Terminal width is not the sole reason to keep code lines
within 80 columns.

--
 \       “The fundamental principle of science, the definition almost, |
  `\             is this: the sole test of the validity of any idea is |
_o__)                                 experiment.” —Richard P. Feynman |
Ben Finney

--- SoupGate-Win32 v1.05
 * Origin: <SpaceSST.BBS.Fidonet<>NNTP.gateway.@.piz.noip.me> (1:249/999)
--- Synchronet 3.15b-Win32 NewsLink 1.92
SpaceSST BBS Usenet <> Fidonet Gateway

[toc] | [prev] | [next] | [standalone]

#82232

  To: sohcahtoa82@gmail.com
On 12/08/2014 03:20 PM, sohcahtoa82@gmail.com wrote:
>>
>
> On Sunday, December 7, 2014 6:26:01 PM UTC-8, jtan wrote:
>> One reason why you would want max length 79 is because of working with 
terminals.  Maybe ssh to you server and check how many spaces are consumed by a 
tab?  In my boxes, it is usually 1 tab = 8 spaces.  So perhaps just use that 
setting in your editor?
>
>
> My terminals are 120 columns wide.
>
> Are there still people that are limiting their terminals to 80 columns?  If 
so, why?

I frequently have more than just one terminal open on my xserver.  I
might have several terminals, or I might also have a browser or another
application.  And I rearrange the windows so the parts I'm interested in
are showing whatever I'd like to simultaneously see.

>  I mean, I can understand if you're running on an ancient square monitor,
>  but I see no reason to limit your terminal to 80 columns if you're running 
any sort of window environment on monitor with a horizontal resolution greater 
than 1280.

What's square got to do with anything?  I have displays ranging from
about 3 inches across to about 29.  The size matters, not usually the
pixel count (my cell phone has 1920 pixels across).

>
> "Because that's how we've always done it!" is a pretty **** reason to 
continue doing something.
>
No need to throw feces around.  There are several reasons besides history.

1) physical screen size, divided by the number of simultaneous windows
one wants horizontally visible.

2) vision acuity.  When the print gets small enough, my elderly eyes
can't read it reliably.

3) Human preference and ability.  Notice that large books and newspapers
use multiple columns, or pictures & ads to break up the page.  A line
beyond some length makes it hard to take it all in at once.

4) Other media.  Sometimes we actually make listings on paper.

If code is only going to be used by one person, then it may make sense
for that person to make it as wide as the size he personally can handle,
with his abilities and equipment and usage habits.

But when there are multiple people, it sometimes makes sense to
constrain code to the most stringent of their abilities.

And one's abilities change over time, just as his equipment does.

--
DaveA

--- SoupGate-Win32 v1.05
 * Origin: <SpaceSST.BBS.Fidonet<>NNTP.gateway.@.piz.noip.me> (1:249/999)
--- Synchronet 3.15b-Win32 NewsLink 1.92
SpaceSST BBS Usenet <> Fidonet Gateway

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web