On Mon, Sep 19, 2011 at 08:38:44AM -0400, Greg Wooledge wrote:
On Sun, Sep 18, 2011 at 10:11:17PM -0800, Roger wrote:
On Mon, Sep 19, 2011 at 01:37:22AM -0400, Mike Frysinger wrote:
On Monday, September 19, 2011 01:18:02 Roger wrote:
I'm stumped on this as my history is in the format of:
OK, thanks for the clarification. I see the problem. It's an incorrect
calculation of the `next history line' in operate_and_get_next() that
mishandles this particular case.
By default, bash limits the size of the history to 500 commands, which
means you get the commands you executed and
On 9/10/11 11:13 AM, Antoine Balestrat wrote:
Hello !
I've just run cppcheck (a static C/C++ code analyzer) against the latest
bash code (freshly cloned from the git repo), and it points out some
interesting issues.
You can see the log here : http://pastebin.com/pZHQShJp
Thanks for the
On Tue, Sep 20, 2011 at 1:34 AM, Roger rogerx@gmail.com wrote:
On Mon, Sep 19, 2011 at 08:38:44AM -0400, Greg Wooledge wrote:
On Sun, Sep 18, 2011 at 10:11:17PM -0800, Roger wrote:
On Mon, Sep 19, 2011 at 01:37:22AM -0400, Mike Frysinger wrote:
On Monday, September 19, 2011 01:18:02 Roger
On 9/20/11 6:52 AM, gregrwm wrote:
The code has been this way for over 20 years, so this is a
very-infrequently-encountered problem. I will have to look at the startup
hook the command uses to see if I can fix it up there.
I fixed the problem, and the fix will be in the next version.
fwiw
