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


Groups > comp.lang.python > #74157

Re: PEP8 and 4 spaces

References (1 earlier) <CAGGBd_rOg+EX1OxryW9-6+2b6yqzzKL9xN1K7+TPSP77tJz=bQ@mail.gmail.com> <mailman.11567.1404694875.18130.python-list@python.org> <lpdbjc$qf7$1@dont-email.me> <mailman.11614.1404782560.18130.python-list@python.org> <53bbb047$0$2926$c3e8da3$76491128@news.astraweb.com>
Date 2014-07-08 19:05 +1000
Subject Re: PEP8 and 4 spaces
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.11619.1404810317.18130.python-list@python.org> (permalink)

Show all headers | View raw


On Tue, Jul 8, 2014 at 6:48 PM, Steven D'Aprano <steve@pearwood.info> wrote:
> If editors were to standardise on the convention "display a
> HORIZONTAL TAB character as visibly distinct from a sequence of
> spaces" (e.g. by shading the background a different colour, or overlying
> it with an arrow)

DeScribe Word Processor has (had? it hasn't been developed in about a
decade... but it still runs just fine) a whole lot of visual guides
for metacharacters, which can be turned on or off. Normally, we prefer
not to have a little dot to mark every 0x20 space, but you can have
'em if you want 'em; tabs get shown as diamonds; paragraph markers as
pilcrows; line breaks as a small circle; and so on. (The difference
between a paragraph and a line break isn't a normal one in most text
editors, so I'd be looking at representing U+000A newlines with a
pilcrow, probably.) Obviously you need a means of distinguishing the
end-of-line marker from an actual character, since PILCROW SIGN is a
perfectly acceptable character; but if the metacharacters are shown
in, say, a pale blue, rather than the usual black text, it'd be easy
enough.

ChrisA

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: PEP8 and 4 spaces Ben Finney <ben@benfinney.id.au> - 2014-07-07 11:00 +1000
  Re: PEP8 and 4 spaces Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-07 02:28 +0000
    Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-07 12:50 +1000
  Re: PEP8 and 4 spaces Dan Sommers <dan@tombstonezero.net> - 2014-07-07 05:35 +0000
    Re: PEP8 and 4 spaces Ben Finney <ben@benfinney.id.au> - 2014-07-08 11:22 +1000
      Re: PEP8 and 4 spaces wxjmfauth@gmail.com - 2014-07-08 00:03 -0700
      Re: PEP8 and 4 spaces Steven D'Aprano <steve@pearwood.info> - 2014-07-08 08:48 +0000
        Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-08 19:05 +1000
        Re: PEP8 and 4 spaces Marko Rauhamaa <marko@pacujo.net> - 2014-07-08 12:09 +0300
          Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-08 20:28 +1000
            Re: PEP8 and 4 spaces Marko Rauhamaa <marko@pacujo.net> - 2014-07-08 14:13 +0300
              Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-08 21:37 +1000
        Re: PEP8 and 4 spaces Ben Finney <ben@benfinney.id.au> - 2014-07-09 12:41 +1000
          Re: PEP8 and 4 spaces wxjmfauth@gmail.com - 2014-07-09 01:19 -0700

csiph-web