<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to patches</title><link>https://sourceforge.net/p/bashdb/patches/</link><description>Recent changes to patches</description><atom:link href="https://sourceforge.net/p/bashdb/patches/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 07 Oct 2019 18:06:11 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/bashdb/patches/feed.rss" rel="self" type="application/rss+xml"/><item><title>#5 Support for xemacs in mdb.el</title><link>https://sourceforge.net/p/bashdb/patches/5/?limit=25#0fad</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; wont-fix&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;assigned_to&lt;/strong&gt;: Rocky Bernstein&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rocky Bernstein</dc:creator><pubDate>Mon, 07 Oct 2019 18:06:11 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0b99b61e92c536c47e7da87fe1cd52f3dfb68603</guid></item><item><title>#5 Support for xemacs in mdb.el</title><link>https://sourceforge.net/p/bashdb/patches/5/?limit=25#68c1</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;We don't distubute Emacs el files anymore.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rocky Bernstein</dc:creator><pubDate>Mon, 07 Oct 2019 18:05:43 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net3bbe5bde272024b8ce931ea109ecd833de5da863</guid></item><item><title>Better emacs integration (similar to gdb-ui)</title><link>https://sourceforge.net/p/bashdb/patches/6/</link><description>Hello,
first, thanks for pydb, it's definitely the nicest python debugger I've seen,
and quite intuitive too \(especially for gdb users\).

One thing I missed from gdb was the great emacs integration, i.e. the "many
windows" mode where you have a special buffer for stack frames, local
variables, breakpoints \(and others\). So, I tried to fix the problem, and I
came up with this patch.

DESCRIPTION:
\------------

This is divided in two parts: on the python side, a patch to pydb.py.in to
introduce annotations, and a patch to pydb.el on the emacs side to exploit
them for showing more information.

On the python side, there's a new command line option, --annotate.
It produces annotations that are similar in purpose to those of GDB \(see
that manual for a description\), although the syntax is different.
they have the following format:
^Z^Zannotname
&amp;lt;arbitrary text&amp;gt;
^Z^Z
where ^Z is the ctrl-Z character, and "annotname" is the name of the
annotation. A line with only two ^Z ends the annotation \(no nesting
allowed\). In particular, three annotations are produced: "breakpoints",
"stack" and "locals". They are printed every time\(\*\) breakpoints, stack frame
or local variables change, thus allowing a client to be notified of such
changes. Their contents is exactly the information to display \(for instance,
for the "breakpoints" annotation the content is the output of the
do\_info\("breakpoints"\) command\).

\(\*\) actually, the current code is a bit conservative, and annotations might be
generated even when not necessary...


On the Emacs side, I've introduced the following changes:
\- \`gud-pydb-marker-filter' now detects annotations and treats them specially,
handing them over to the new function \`pydb-process-annotation', and not
displaying their output

\- \`pydb-process-annotation' associates each annotation to a special buffer
\(much like in gdb-ui, for breakpoints, stack frames, and locals\). Buffers
for breakpoints and stack frames have special fontification and keyboard and
mouse navigation:

\* Middle-click \(or RET\) on a breakpoint brings you to its location in the
source file
\* SPC enables/disables the current breakpoint
\* d deletes it

\* Left or middle-click \(or RET\) on the stack frame i is equivalent to the
"frame i" command

\- A customizable variable \`pydb-many-windows' controls the default layout when
invoking pydb: if t, a layout similar to what \`gdb-many-windows' produces is
displayed:

+---------------------+---------------------------+
|                     |                           |
|  PYDB buffer        |         Locals buffer     |
|                     |                           |
|                     |                           |
+---------------------+---------------------------+
|                                                 |
|                                                 |
|          Source code buffer                     |
|                                                 |
|                                                 |
|                                                 |
+---------------------+---------------------------+
|                     |                           |
|                     |                           |
| Stack frames buffer |    Breakpoints buffer     |
|                     |                           |
|                     |                           |
+---------------------+---------------------------+



The code could probably be improved, and needs some more testing \(but that's
why I'm sending this :-\), but it should work. And if some further patches are
needed, I can help afterwards \(if time permits\).


Thanks again for your work on Pydb, I hope you find this useful,

Alberto
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alberto Griggio</dc:creator><pubDate>Sun, 26 Aug 2007 09:37:55 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5ed7a52498d2cec5458020bbb5ab5c9312495191</guid></item><item><title>Support for xemacs in mdb.el</title><link>https://sourceforge.net/p/bashdb/patches/5/</link><description>This is a hack - not a portable solution. You have to add some conditionals to make it work either in emacs or xemacs.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rajish</dc:creator><pubDate>Mon, 06 Aug 2007 15:30:16 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net518771d4aa093dc78fa32c86edd594c2622f904b</guid></item><item><title>Support for xemacs in mdb.el</title><link>https://sourceforge.net/p/bashdb/patches/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 5 has been modified: Support for xemacs in mdb.el&lt;br/&gt;
Edited By: Rocky Bernstein (rockyb)&lt;br/&gt;
Status updated: u'open' =&amp;gt; u'wont-fix'&lt;br/&gt;
Owner updated: None =&amp;gt; u'rockyb'&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rajish</dc:creator><pubDate>Mon, 06 Aug 2007 15:30:16 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5b00d884d5f002ca99b359be433ea7cdd08ef1f0</guid></item><item><title>Better support for tracking position in NTEmacs</title><link>https://sourceforge.net/p/bashdb/patches/4/</link><description>The emacs regexps used to track the current line don't handle all types of path names under Windows.  This patch   adds support to both regexps for:  
\* C:\ style paths
\* spaces in path

\(diff against current cvs\)

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 22 Feb 2007 19:15:12 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net781c9c2af683f7605b976f7e20fd7e5deb334111</guid></item><item><title>Make breakpoints work for files outside cwd</title><link>https://sourceforge.net/p/bashdb/patches/3/</link><description>Setting breakpoints works only for files that are either in the current working directory of the debugger or found on sys.path. This patch makes Emacs use the full pathname of files so you can set breakpoints in any file.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jouni K Seppänen</dc:creator><pubDate>Mon, 12 Feb 2007 16:36:51 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0a22852fbee42674aa338f27d11aafb67b40f663</guid></item><item><title>With patch this time.</title><link>https://sourceforge.net/p/bashdb/patches/2/</link><description>fixed compilation issue and empty line handline for remake
I made two fixes. The first was a configure.ac thing
... my system has
readline.a, but not termcap.a ... and readline was not
getting found for want to termcap. So I added a
seperate check for termcap before readline. It works
for me.

Secondly, when interactively debugging, just hitting
enter would not
step as expected .... it just repeated the prompt. So
I messed with the logic in enter\_debugger.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 31 Mar 2005 15:28:44 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net4d2546f33b70ea7dd21f3a22d5daa8a2a67e4742</guid></item><item><title>fixed compilation issue and empty line handline for remake</title><link>https://sourceforge.net/p/bashdb/patches/1/</link><description>I made two fixes.  The first was a configure.ac thing
... my system has
readline.a, but not termcap.a ... and readline was not
getting found for want to termcap.  So I added a
seperate check for termcap before readline.  It works
for me.

Secondly, when interactively debugging, just hitting
enter would not
step as expected .... it just repeated the prompt.  So
I messed with the logic in enter\_debugger.

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 31 Mar 2005 15:25:52 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf6539170834840fecdab679e0b8c70ff20d014c6</guid></item></channel></rss>