Second option from my feedback.
Is there a way to reuse the ncurses format 1:1, the same directory
layout, file format and suffixes? This would make our version a ready
drop-in replacement and predictable behavior for $TERMINFO and similar
env(1) variables.
A benefit of this approach is to reuse
Date:Tue, 9 May 2017 19:03:59 +0200
From:"rud...@eq.cz"
Message-ID:
| FWIW, i think the "option approach" is worth the effort.
I think I agree, even if we also do the local variant (if that turns
out to be possible, I still have not attempted it.)
| If undersco
I think it would be good to make the database modular, and to stop
requiring having everything in one binary blob. I don't see any
downsides to Roy's suggestion.
Jaromir
2017-05-09 21:48 GMT+02:00 Kamil Rytarowski :
> On 09.05.2017 16:50, Roy Marples wrote:
>> On 09/05/2017 12:51, Kamil Rytarowsk
On 09.05.2017 16:50, Roy Marples wrote:
> On 09/05/2017 12:51, Kamil Rytarowski wrote:
>> I don't have a preference, but I'm surprised that our single .cdb
>> approach is going to be hybrid with support for ncurses layout.
>
> Other ideas welcome on how to allow pkgsrc to integrate terminfo
> desc
Robert Elz wrote:
I have one off list opinion that the option is a reasonable approach,
and one off-list suggestion "something derived from
``function relative line numbers'' " for the name...
But no concrete suggestions.
FWIW, i think the "option approach" is worth the effort. If underscores
On 09/05/2017 12:51, Kamil Rytarowski wrote:
> I don't have a preference, but I'm surprised that our single .cdb
> approach is going to be hybrid with support for ncurses layout.
Other ideas welcome on how to allow pkgsrc to integrate terminfo
descriptions.
Roy
signature.asc
Description: OpenP
> Interrupt transfers are very likely to lose data if not serviced fast enough
> which is very likely with ugen access.
And what can I do about that? Write a driver for that UPS USB interface?
On 05/09/17 13:48, Edgar Fuß wrote:
Sounds like a data-toggle problem.
OK, thanks. I first had to research what that is.
Hard to debug w/o a bus trace, because the host controller handles this.
I'll try to get hold of a hardware tracer then.
Would be to know host controller type when lookin
> Sounds like a data-toggle problem.
OK, thanks. I first had to research what that is.
> Hard to debug w/o a bus trace, because the host controller handles this.
I'll try to get hold of a hardware tracer then.
> Would be to know host controller type when looking at this.
OHCI, if I read my dmesg
On 09.05.2017 11:59, Roy Marples wrote:
> On 05/05/2017 20:54, Kamil Rytarowski wrote:
>> I have a pending task to write from scratch in C# for CoreFX (.NET
>> platform assemblies) support for extracting registered entries from our
>> native terminfo cdb file. (This is currently enforced to be this
On 05/05/2017 20:54, Kamil Rytarowski wrote:
> I have a pending task to write from scratch in C# for CoreFX (.NET
> platform assemblies) support for extracting registered entries from our
> native terminfo cdb file. (This is currently enforced to be this way,
> the same happens for ncurses)
Intere
11 matches
Mail list logo
