Re: Colour support in editline

In article , ZNV wrote: >-=-=-=-=-=- > >Hi! > >Is there any interest in adding colour support to editline? > >It is a known issue that editline doesn't support colour prompts.

Re: building current - signal 6

In article <5729be9e.5030...@libero.it>, Riccardo Mottola wrote: >Hi Erik, > > >Erik Fair wrote: >> #define SIGABRT 6 /* abort() */ >> >> See also signal(7) and abort(3). >> >> It would appear that make(1) called abort(3) since rm(1) doesn’t >have any

Re: building current - signal 6

In article <33d21884-f50f-4933-a887-337520338...@netbsd.org>, Erik Fair wrote: >In /usr/include/sys/signal.h find: > >#define SIGABRT 6 /* abort() */ > >See also signal(7) and abort(3). > >It would appear that make(1) called abort(3) since rm(1) doesn’t have >any

daily CVS update output

Updating src tree: P src/doc/roadmaps/storage P src/sbin/modload/main.c P src/sbin/modunload/main.c P src/share/man/man9/namei.9 P src/sys/arch/aarch64/conf/Makefile.aarch64 P src/sys/arch/evbarm64/conf/std.a64emul P src/sys/arch/evbarm64/conf/std.evbarm64 P src/tests/dev/usb/t_hid.c Updating

Colour support in editline

Hi! Is there any interest in adding colour support to editline? It is a known issue that editline doesn't support colour prompts. http://stackoverflow.com/questions/21240181/how-to-colorize-the-prompt-of-an-editline-application We are also interested in some editor-like features, including

Re: building current - signal 6

Hi Erik, Erik Fair wrote: #define SIGABRT 6 /* abort() */ See also signal(7) and abort(3). It would appear that make(1) called abort(3) since rm(1) doesn’t have any direct calls to it that I could find by reading the base source. Cursory grep through/usr/src/usr.bin/make/*

Re: building current - signal 6

In /usr/include/sys/signal.h find: #define SIGABRT 6 /* abort() */ See also signal(7) and abort(3). It would appear that make(1) called abort(3) since rm(1) doesn’t have any direct calls to it that I could find by reading the base source. Cursory grep through

Re: bash job control broken?

On Wed, Apr 27, 2016 at 05:24:54PM +0200, Thomas Klausner wrote: > Hi! > > I see strange behaviour on NetBSD-current with bash (sh, zsh are > fine). Here's a simple test case: > > # cat /dev/zero >&/dev/null > CTRL-Z > [1]+ Stopped cat /dev/zero &> /dev/null > # bg > [1]+ cat

Re: Lock /mutex issue with i916 on HP620

Hi, Riccardo Mottola wrote: I was able to take a screenshot with a ddb stacktrace. I canno t attach them here apparently, where may I post them (some pastebin but for images) / send them in private ? here are my screenshots: http://imgur.com/a/bd5wl Riccardo

Re: Lock /mutex issue with i916 on HP620

On Thu, May 05, 2016 at 12:40:49PM +0200, Riccardo Mottola wrote: > Hi, > > to help debugging the Wireless stuff with Christos on my HP620, I compiled a > kernel with DEBUG+LOCKDEBUG. > > The kernel does not complete booting! it stops with a turnstile issue and a > LOCKDEBUG bug. > > Mutex

Lock /mutex issue with i916 on HP620

Hi, to help debugging the Wireless stuff with Christos on my HP620, I compiled a kernel with DEBUG+LOCKDEBUG. The kernel does not complete booting! it stops with a turnstile issue and a LOCKDEBUG bug. Mutex error: lockdebug_wantlock: acquiring sleep lock from interrupt context <.. hex