Re[2]: bash 4.3: "Clear Scrollback and Reset" (Ctrl-Shift-X) in konsole stopped to work as expected when upgrading from upstream bash 4.2 to upstream bash 4.3

2014-12-03 Thread Askar Safin
ion will be uploaded to Debian. So, I will not close the bug (right?). == Askar Safin http://vk.com/safinaskar Kazan, Russia

Re[3]: bash 4.3: "Clear Scrollback and Reset" (Ctrl-Shift-X) in konsole stopped to work as expected when upgrading from upstream bash 4.2 to upstream bash 4.3

2014-12-03 Thread Askar Safin
>> Please stop mischaracterizing the issue. It's not a bug: it's a case of >> konsole's mismatched expectations. Since the mechanism it uses is not >> documented, and relies on something in readline that is not documented, it >> can't fairly be called a bug. >Should long text line move when user

Re[2]: bash 4.3: "Clear Scrollback and Reset" (Ctrl-Shift-X) in konsole stopped to work as expected when upgrading from upstream bash 4.2 to upstream bash 4.3

2014-11-30 Thread Askar Safin
> Please stop mischaracterizing the issue. It's not a bug: it's a case of > konsole's mismatched expectations. Since the mechanism it uses is not > documented, and relies on something in readline that is not documented, it > can't fairly be called a bug. Should long text line move when user chang

Re[2]: bash 4.3: "Clear Scrollback and Reset" (Ctrl-Shift-X) in konsole stopped to work as expected when upgrading from upstream bash 4.2 to upstream bash 4.3

2014-11-29 Thread Askar Safin
rminal + bash 4.2 | bad | good gnome-terminal + bash 4.3 | bad | bad konsole + bash 4.2| good | good konsole + bash 4.3| bad | bad (And this gnome-terminal may be too old, i. e. Pádraig Brady just reported his gnome-terminal works, he probably uses newer version.) == Askar Safin http://vk.com/safinaskar Kazan, Russia

Re[2]: bash 4.3: "Clear Scrollback and Reset" (Ctrl-Shift-X) in konsole stopped to work as expected when upgrading from upstream bash 4.2 to upstream bash 4.3

2014-11-28 Thread Askar Safin
roduces this behavior (git bisect, again). But still this branch doesn't seem as real devel history. This is just weekly snapshots. Does bash have real SCM (non-git ones is OK)? Where is SCM you use for development? == Askar Safin

Re[2]: bash 4.3: "Clear Scrollback and Reset" (Ctrl-Shift-X) in konsole stopped to work as expected when upgrading from upstream bash 4.2 to upstream bash 4.3

2014-11-28 Thread Askar Safin
Shift-X except for me, so, you think this Ctrl-Shift-X-bug isn't worth fixing. But everybody resize his terminal window, so now I found real bug, ahaha! :) Reproduces using 4.3-11 from Debian and doesn't reproduce using 4.2+dfsg-0.1+deb7u3 from Debian. And thank you, Chet for the idea. :) == Askar Safin http://vk.com/safinaskar Kazan, Russia

Re[2]: bash 4.3: "Clear Scrollback and Reset" (Ctrl-Shift-X) in konsole stopped to work as expected when upgrading from upstream bash 4.2 to upstream bash 4.3

2014-11-28 Thread Askar Safin
.savannah.gnu.org/cgit/bash.git appears to be incomplete: "git bisect" shows that the problem is in http://git.savannah.gnu.org/cgit/bash.git/commit/?id=ac50fbac377e32b98d2de396f016ea81e8ee9961 , but this is a huge commit. Where can I download more detailed history? == Askar Safin http://vk.com/safinaskar Kazan, Russia

bash 4.3: "Clear Scrollback and Reset" (Ctrl-Shift-X) in konsole stopped to work as expected when upgrading from upstream bash 4.2 to upstream bash 4.3

2014-11-27 Thread Askar Safin
Trusty (with bash 4.3) remote machine and doesn't reproduce with Debian Wheezy (with bash 4.2) one. Then I understand that the bug is not related to ssh at all and this is just bash+konsole bug. So, because of this very confusing nature of the bug, I gave it priority "important".

Re[2]: 1 is not safe, unusual PID value

2011-12-27 Thread Askar Safin
> For the purposes of that code fragment, 1 is both safe and unusual. OK

1 is not safe, unusual PID value

2011-12-25 Thread Askar Safin
In jobs.c we see: #if defined (RECYCLES_PIDS) if (last_asynchronous_pid == mypid) /* Avoid pid aliasing. 1 seems like a safe, unusual pid value. */ last_asynchronous_pid = 1; #endif 1 is not safe, unusual PID value, because: 1. Linux kernel sometimes start with option "ini