Oh, I forgot the main point I wanted to raise here.  With variables
wrapped, and each subsequent line indented, it makes it harder for the
eye to see what lines are wrapped and what lines are part of an
expanded variable.  You get stuff like (I hope my indentation survives
this email):

myvariable: [1,
  2, 3, 4, 'a s
  tring']
  0: 1
  1: 2
  2: 3
  3: 4
  4: 'a strin
    g'

(here, I made the column width 16 to make ie easier to type).

I suggest replacing the first of the two spaces in front of the first
line in an internal variable with another character.  The best I can
think of is +.  So it would look like:

myvariable: [1,
  2, 3, 4, 'a s
  tring']
+ 0: 1
+ 1: 2
+ 2: 3
+ 3: 4
+ 4: 'a strin
    g'

Deeply nested items would look like:

alist: [1, [2, 3]]
+ 0: 1
+ 1: [2, 3]
+ + 0: 2
+ + 1: 3

This would be a trivial change to make, but I just want to know if you
are OK with it first.

Aaron Meurer

On Sun, Aug 7, 2011 at 1:23 AM, Aaron Meurer <[email protected]> wrote:
> I implemented the preliminary version of this in my wrap branch.
> There are still a few things to do (see the TODO in the commit
> message).  I will go ahead and open a pull request for it, though you
> might hold off on actually merging it until I am completely finished.
>
> And regarding unicode, it is possible to tell if a terminal supports
> unicode or not (I'll see what SymPy does, or maybe urwid has something
> built in).  I think I will use that.
>
> Aaron Meurer
>
> On Tue, Aug 2, 2011 at 7:41 AM, Andreas Kloeckner
> <[email protected]> wrote:
>> On Mon, 1 Aug 2011 18:31:20 -0600, Aaron Meurer <[email protected]> wrote:
>>> So PuDB requires a unicode terminal?
>>
>> I suppose not. I guess that was a bad idea.
>>
>> Andreas
>>
>>
>

_______________________________________________
Pudb mailing list
[email protected]
http://lists.tiker.net/listinfo/pudb

Reply via email to