Disconnect3d

@zachriggle the problem is there with colored/escaped things e.g.: ``` In : print('x'+red('x').ljust(3)+'y') xxy In : print('x'+'x'.ljust(3)+'y') xx y ```

@anthraxx bump :P

Thx for creating issue for that! Probably this could be handled in `ArgparsedCommand` itself - https://github.com/pwndbg/pwndbg/issues/244

PR containing those changes should also add information to use stdlib logging instead of prints in [.github/CONTRIBUTING.md](.github/CONTRIBUTING.md)

By the way, moving to `ArgparsedCommand` makes docstrings useless, e.g.: ```python @pwndbg.commands.ArgparsedCommand(argparse.ArgumentParser(description='ASDASDASD')) @pwndbg.commands.OnlyWithFile def checksec(file=None): ''' Prints out the binary security settings. Attempts to call the binjitsu checksec first, and...

@GrosQuildu can you extend the `bugreport` command with the debugged file? I think this should also be optional with e.g. `--attach-debugged-file` flag.

Is this issue about using `starti` for `entry` (`start`) commands? What about `ptype`? Use `dt` as an alias for `ptype`? I mean, for GDB>=8.1 ofc

This is how `ptype` with offsets looks like compared to `dt`: ``` pwndbg> help ptype Print definition of type TYPE. Usage: ptype[/FLAGS] TYPE | EXPRESSION Argument may be any type...

Given that our `start` and `entry` does sth else than `starti` I am leaving `start` and `entry` as they are and will just improve their description to match certain standards...

@roman-soft Are you using the latest pwndbg version? I had the same setup as you few months ago and had similar issue which I have reported here: https://github.com/pwndbg/pwndbg/issues/132#issuecomment-264697778 - and...