Great! Thank you! Debian 13 trixie entered full freeze today and is planned to be released on August 9th, so I'll integrate bvi 1.5.0 in Debian unstable after that date. Have a nice day, :) Étienne.
patch for various issues caught by lintian
Fixed in 1.5.0
bvi fails to build with gcc-15/C23
Fixed in 1.5.0
bvi fails to build with gcc-15/C23
Good day, I had a closer look at the errors and found out the Debian build branches to function prototypes with unspecified argument types, but there exists also function prototypes with specified argument types when the ANSI macro is defined for most functions. If I ensure that the build branches to typed arguments in every cases, then it builds fine with -stdc=gnu23; this also does not introduce regressions with -stdc=gnu89. I plan to use the patch in attachment which relies on STDC to implement...
Links look to have dropped off the ticket. They were supposed to be: 1: https://bugs.debian.org/1096399 2: https://people.debian.org/~emollier/logs/bvi/bvi_1.4.2-3_amd64.build 3: https://gcc.gnu.org/gcc-15/porting_to.html
bvi fails to build with gcc-15/C23
patch for various issues caught by lintian
patch for various issues caught by lintian
Mixed licenses
Fixed in 1.4.2
Segmentation fault occurs on undo.
Fixed in 1.4.2
Segmentation fault occurs on substitution in 32-bit systems.
Fixed in 1.4.2
Fixed in 1.4.2
Handling inputs larger than 2^31 bytes
Dixed in 1.4.2
Some incorrect function prototypes in ANSI mode
Fixed in 1.4.2
Some incorrect function prototypes in ANSI mode
Hallo Gerhard, tatsächlich habe ich bis jetzt nur read-only mit bvi gearbeitet. Für große Dateien muss man tatsächlich einen write Befehl patchen. Mit dem Commit hier funktioniert das Schreiben aber: https://github.com/koeppl/bvi/commit/b7386b2aca85ec2c83e9c85c6f1cb9b14c2e9891 Grüße Dominik
Am 14.03.2022 um 08:25 schrieb "Dominik Köppl": Hallo Gerhard, vielen Dank für das positive Feedback! Hallo Dominik, jetzt ist mir der Gedanke gekommen, dass wir ja auch noch einen "write" system call haben. Da besteht das Problem nicht? (Falls du's schon ausprobiert hast oder immer solche Monsterdateien vorrätig hast) ;-) Grüße, Gerhard
Hallo Gerhard, vielen Dank für das positive Feedback!
Am 09.03.2022 um 09:29 schrieb "Dominik Köppl": I have exchanged all |read| calls in |io.c|, and it seems to work. Here is the diff: https://github.com/koeppl/bvi/commit/57f35c9779977914c1b45afbb019698d740052ca [bugs:#13] https://sourceforge.net/p/bvi/bugs/13/ Handling inputs larger than 2^31 bytes When reading files larger than 2^31 bytes, |bvi| correctly determines the size, but shows all bytes after the 2^31-st byte as \0 byte. I think that the C routine reading in the input file uses a single...
I have exchanged all read calls in io.c, and it seems to work. Here is the diff: https://github.com/koeppl/bvi/commit/57f35c9779977914c1b45afbb019698d740052ca
Handling inputs larger than 2^31 bytes
Segmentation fault occurs on substitution in 32-bit systems.
Segmentation fault occurs on undo.
Mixed licenses
^Y does suspend
The Control-y key sequence suspends bvi and send it to the background. To avoid this behaviour use: stty dsusp undef
'set columns' prevents filename display in commandline
Fixed in 1.4.1
Compile warning: implicit declaration of function ‘save_chk’
Fixed in 1.4.1
Compile warning: implicit declaration of function ‘save_chk’
'set columns' prevents filename display in commandline
Fixed in 1.4.0
Offset handling (-b) considers files empty unless -s given
b B w W movement
Fixed in 1.4.0
Fixed in 1.4.0
bvi opens to end
Fixed in 1.4.0
'g' and columns <= 8