summaryrefslogtreecommitdiff
path: root/python3
AgeCommit message (Collapse)Author
2020-03-29Merge pull request #446 from StotoV/444HEADmasterIke Devolder
Source window jumps to correct buffer with one item stack
2020-03-23SOURCE WINDOW JUMPS TO CORRECT BUFFER WHEN THE SOURCE WINDOW BUFFER IS ↵Tom Stock
SWITCHED MANUALLY #444
2020-02-29fix log and breakpoint miss hit on win osguantion
2020-02-04added commaJJP7
2019-08-04Merge branch 'master' of github.com:pceuropa/vdebugRafal Marguzewicz
2019-08-04ChangesRafal Marguzewicz
Remove unused packages: 1 dbgp.py|2 col 1 error| 'socket' imported but unused [F401] [python/flake8] 2 dbgp.py|3 col 1 error| 'sys' imported but unused [F401] [python/flake8] 3 dbgp.py|4 col 1 error| 'time' imported but unused [F401] [python/flake8] Standard PEP8: 4 dbgp.py|162 col 28 error| E225 missing whitespace around operator [python/pep8] 5 dbgp.py|162 col 28 error| missing whitespace around operator [E225] [python/flake8] 6 dbgp.py|254 col 28 error| E226 missing whitespace around arithmetic operator [python/pep8] 7 dbgp.py|254 col 28 error| missing whitespace around arithmetic operator [E226] [python/flake8] 8 dbgp.py|257 col 29 error| E226 missing whitespace around arithmetic operator [python/pep8] 9 dbgp.py|257 col 29 error| missing whitespace around arithmetic operator [E226] [python/flake8] 10 dbgp.py|276 col 50 error| E226 missing whitespace around arithmetic operator [python/pep8] Changes to be committed: modified: python3/vdebug/dbgp.py
2019-07-13move default layouts in python and have layout optionBlackEagle
Use layout in vdebug_options to have a vertical or horizontal layout, these are now fixed layouts. Later we could add a custom layout if that would be desired. Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2019-07-13Merge branch 'debugger-layouts' of https://github.com/Garethp/vdebug into ↵BlackEagle
Garethp-debugger-layouts * 'debugger-layouts' of https://github.com/Garethp/vdebug: Fixing bad config Another way to let people choose between layouts Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2019-07-07Merge pull request #419 from vim-vdebug/check-if-is-connectedIke Devolder
first check if there is a connection before acting on some events
2019-07-07Merge pull request #413 from Garethp/stack-changingIke Devolder
Adding the ability to change stacks
2019-07-07first check if there is a connection before acting on some eventsBlackEagle
The events 'step over', 'step in', 'step out', 'run to cursor' can only ben done when there is an active debug session. So first check if we are actually connected before allowing the rest of the code to run Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2019-07-06convert status to str first and check if it existsBlackEagle
Then start checking for interactive or stopping/stopped fixes #362 Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2019-07-05Merge pull request #416 from vim-vdebug/fix-detach-no-sessionIke Devolder
first check connection before detaching
2019-07-05Merge pull request #415 from vim-vdebug/fix-395Ike Devolder
when coming back from eval, pass context 0 to the event
2019-07-05first check connection before detachingBlackEagle
When there is no connection and you were detaching you just got a stacktrace. So first check if there is an actual connection to detach from. Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2019-07-05when coming back from eval, pass context 0 to the eventBlackEagle
this will return us to the local variables context from the eval. fixes #395 Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2019-07-05Adding the ability to change what stack is being shown in the watch windowGareth Parker
2019-07-05Allow removing a breakpoint from an empty lineGareth Parker
2019-07-05Another way to let people choose between layoutsGareth Parker
2019-07-04Revert "Adding a heartbeat"Ike Devolder
2019-07-04Merge pull request #407 from Garethp/port-checkingIke Devolder
Reports to the user if the port they want is already taken
2019-07-04Merge pull request #406 from Garethp/heartbeatIke Devolder
Adding a heartbeat
2019-07-04Merge pull request #404 from Garethp/breakpoint-toggleIke Devolder
Adding support for breakpoint enabling/disabling (Solve #393)
2019-07-04simplified status, take it into account for all printing in StatusWindowBlackEagle
Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2019-07-04simplified status, also use a glyph for listeningBlackEagle
Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2019-07-04Adding a breakpoint status as well as as a tri-state breakpoint cyclingGareth Parker
2019-07-04Reports to the user if the port they want is already takenGareth Parker
2019-07-03Adding a heartbeatGareth Parker
2019-07-03Adding support for breakpoint enabling/disablingGareth Parker
2019-06-20Making the window height/width and status bar configurableGareth Parker
2019-05-10fix not-"expanded" mode in watch windowJason Woofenden
2018-11-29Handled UnicodeDecodeError on invalid string valueGildas Quéméner
2018-10-20fix exception when setting wrong options in vim window via pythonBlackEagle
Signed-off-by: BlackEagle <ike.devolder@gmail.com>
2018-10-04Do not use deprecated method base64.encodestringLucas Hoffmann
Reported by pylint.
2018-10-04Add consistent empty lines before classesLucas Hoffmann
2018-10-04Remove else after returnLucas Hoffmann
Pylint reports these and it flattens the if-else cascades a bit.
2018-10-04Remove object as explicit parent classLucas Hoffmann
That is not needed in python3.
2018-10-04Remove unused methodsLucas Hoffmann
2018-10-04Use some more idiomatic python instead of vim.evalLucas Hoffmann
2018-08-11Remove python2 import workaroundsLucas Hoffmann
The switch to python3 is now complete so we don't need these workarounds to run on both python2 and python3 any longer.
2018-08-09Merge pull request #375 from lucc/py3-cleanupIke Devolder
Remove __future__ imports
2018-08-08Remove superfuous :silentLucas Hoffmann
2018-08-08Group all autocommands into the Vdebug groupLucas Hoffmann
2018-08-08Remove __future__ importsLucas Hoffmann
They are currently not needed with python3.
2018-08-02Move python code to python3 folderLucas Hoffmann
As the code now only works with python3 it should not be in the pythonx directory any longer. That would suggest that it could be used with both versions.