On 26.11.23 02:19, Grisha Levit wrote:
On Sat, Nov 25, 2023, 14:03 Chet Ramey wrote:
On 11/25/23 11:41 AM, Matthias Klose wrote:
[forwarded from https://bugs.debian.org/1056314]
"""
I am getting a crash in the Python REPL in this scenario:
1. start "python3" i
[forwarded from https://bugs.debian.org/1056314]
"""
I am getting a crash in the Python REPL in this scenario:
1. start "python3" in a terminal
2. type "2+2", enter
3. type (or copy-paste) "1234+5678", enter
4. arrow-up, remove "234", page-down, arrow-up, enter
5. arrow-up, arrow-up, add "000" (
On 13.04.22 20:40, Chet Ramey wrote:
The first beta release of bash-5.2 is now available with the URLs
ftp://ftp.cwru.edu/pub/bash/bash-5.2-beta.tar.gz
https://ftp.gnu.org/pub/gnu/bash/bash-5.2-beta.tar.gz
not in the bash tarball, but in the readline 8.2 beta tarball, the generated
configure
This was reported for Debian in https://bugs.debian.org/968703 for the
interactive Python interpreter, however I also see it with gdb, e.g. trying to
run ls in gdb. readline 8.1 is in use.
$ cat .inputrc
# Based on Brendan Miller's initial bash .inputrc
# INSTALL
# to install, rename this file to
On 6/17/20 4:47 PM, Chet Ramey wrote:
> The first alpha release of bash-5.1 is now available with the URL
>
> ftp://ftp.cwru.edu/pub/bash/bash-5.1-alpha.tar.gz
Looking at the corresponding readline 8.1 alpha release, I see two symbols being
dropped compared to 8.0:
#MISSING: 8.1~alpha1# _rl_inte
small typo building the docs.
also we had release candidates before, now reverting to beta names. is this
expected?
Matthias
$ diff -u doc/rltech.texi~ doc/rltech.texi
--- doc/rltech.texi~2016-04-26 16:06:14.0 +0200
+++ doc/rltech.texi 2016-07-25 20:54:04.831406778 +0200
@@ -153
seen when entering q!, then leaving the shell with ^D
$ gdb bash
(gdb) run
Starting program: /bin/bash
doko@gb:~$ q!
q!: Befehl nicht gefunden.
doko@gb:~$
malloc: .././parse.y:2314: assertion botched
realloc: start and end chunk sizes differ
last command: q!
Aborting...
Program received signal SI
seen with bash-4.2.6 with gcc-4.5, configured on i686-linux-gnu with
--enable-targets=all --with-arch-32=i686, works with bash-4.1:
case X"${with_cpu}" in
Xgeneric|Xatom|Xcore2|Xnocona|Xx86-64|Xamdfam10|Xbarcelona|Xk8|Xopteron|Xathlon64|Xathlon-fx|Xathlon64-sse3|Xk8-sse3|X
wouldn't this changed behaviour warrent a compatibility switch?
--- Begin Message ---
# justification: breaks plenty other packages,
# and if only by way of #522255
severity 518752 grave
tags 518752 upstream confirmed
thanks
also sprach Andreas Metzler [2009.03.08.1442
+0100]:
> d. Fixed a bug
Found http://www.caliban.org/mt/archives/2007/12/please_rescue_m.html
Would anybody be interested to maintain/co-maintain bash_completion?
Matthias
10 matches
Mail list logo