editor settings

What's your tab width (4)? Do you use spaces or tabs (tabs) ? What's your text width (100)?

100
fucking faggot

2 spaces, width 255

4 spaces, no width limit

I follow PEP 8 religiously
THREAD OVER

adjusting spaces of indent is stupid, all that is better controlled by using the right font. the type of font you use can double the horizontal length of your text

I dont use tabs except for make files

Hey, we can't program for shit so let's talk about our shitty style guidelines !!

4/80
11pt font
Monitor in portrait mode

4, space, 80. Also,
>tabs
>100
IHBT

>>5
PEP MY ANUS

1 space, 128 width

3 spaces (yes, three), width 80 or 128.

8, tabs, 80

My indentation follows the Fibonacci sequence beginning at F₂.

4 space 80

8, tabs, 80

4, spaces, 95

4, splaces, 100

4 spaces +inf

>2011
>Still limits lines to 80
-_-

>>20
When you're programming large projects it's nice to have multiple pages of source open side by side, therefore it's nice to have each page limited to 80 characters, but you probably wouldn't understand since you're probably still writing hello world functions.

>>21
Why 80 and not 120?

>>22
80 was the forced limitation on old terminals so it became the standard. As the limitation dissolved, the standard remained for a variety of reasons:

1. A lot of OS/kernels/software that are still used and maintained were already written this way and consistency is important.
2. It encourages programmers to use concise statements rather than complicated one-liners.
3. It encourages programmers to think about logical breaks that could be split into subroutines rather than nested into one complicated function.
4. It allows power-coders to view multiple pages at fixed width without having to worry about vertical scrolling.

Lastly, there are really no benefits to using more than 80 columns. "I need 50% more width so I can write 50% longer lines that are 50% more levels of logic deeper" isn't going to convince anybody. For something hideous like Java I could see how 10-20 extra columns might be nice, but that's it. The Linux kernel is written with 80 columns with something like 8 tab spaces and I haven't heard about it hindering any of the contributors abilities. Seems like asking for more is just an excuse to write bad code.

>>19
+inf
cue in faggot troll in 3... 2...

>>21
cool superiority complex bro. now go, you're needed at cash register 3.

>>23
I know, but it was. Also, Lisp procedures usually are just one, big expression, and code grows vertically rather than horizontally.

>>26
Nobody even mentioned Lisp, dipshit.

>>27
FIOC grows vertically too.

>>28
Nobody even mentioned FIOC, dipshit.

>>27,29
Polecat Kebabs

I've read some complicated python, and the best of it so well designed you rarely see FIOC past three indents.  An if in a def in a class is about as indented as you'll see.

Functional programs have a different shape from imperative
ones. The structure in a functional program comes entirely from the composition
of arguments within expressions, and since arguments are indented, functional
code will show more variation in indentation. Functional code looks fluid 1 on the
page; imperative code looks solid and blockish, like Basic.

Example:
(defun bad-reverse (lst)
  (let* ((len (length lst))
         (ilimit (truncate (/ len 2))))
    (do ((i 0 (1+ i))
         (j (1- len) (1- j)))
        ((>= i ilimit))
      (rotatef (nth i lst) (nth j lst)))))

(defun good-reverse (lst)
  (labels ((rev (lst acc)
             (if (null lst)
                 acc
                 (rev (cdr lst) (cons (car lst) acc)))))
   (rev lst nil)))

>>30
Nobody even mentioned /b/, dipshit.

>>33
Nobody even mentioned dipshits, dipshit.

>>34
Nobody even mentioned mentioning dipshits, dipshit.

>>32
thank you.

>>36
No problem.

>>32
scheme version pl0x?

tab characters should be handled by markup standards. Should not have been added to character sets.

>>32
PIG DISGUSTING

>>38
pl0x
*Cringe*