On Wed, Jun 29, 2011 at 03:34:32PM -0700, Lyndon Nerenberg wrote:
>
> I'd be curious to see what you came up with.
>
It was the emulation of a handset, on screen, driving an interface
adapter that communicated digitally with a small PABX. I can post the
ancient Inferno code as is on my web site,
I wrote a SIP proxy in Limbo, a decade and a bit apast. Can't find it
off-hand. Maybe it's in VNI or discarded by the the IBU mafia.
brucee
On Thu, Jun 30, 2011 at 5:45 PM, Lucio De Re wrote:
> On Wed, Jun 29, 2011 at 03:34:32PM -0700, Lyndon Nerenberg wrote:
>>
>> I'd be curious to see what you
>Maybe it's in VNI or discarded by the the IBU mafia.
the latter, i'm afraid. i never saw it.
On Wed, Jun 29, 2011 at 07:43:08PM -0400, Karljurgen Feuerherm wrote:
>[...]
First to make clear what I was refering to (and making a false
generalization) : the XeTeX FAQ:
"However, standard Unicode-compliant fonts do not include ligatures for
these sequences, as the normal expectation is that
> But, as the present state allows the use for every character set that
> fits in eight bits, by using (for Plan9 users) tcs(1) to feed TeX with
> what it expects, I will not delay forever the release of 1.0 waiting for
> this next solution.
good grief. how hard is it to write this code!? this b
i may have a copy on an ancient laptop. it's worth it, it was icky.
brucee
On Thu, Jun 30, 2011 at 10:08 PM, Charles Forsyth wrote:
>>Maybe it's in VNI or discarded by the the IBU mafia.
>
> the latter, i'm afraid. i never saw it.
>
>
On Thu, Jun 30, 2011 at 09:14:10AM -0400, erik quanstrom wrote:
> > But, as the present state allows the use for every character set that
> > fits in eight bits, by using (for Plan9 users) tcs(1) to feed TeX with
> > what it expects, I will not delay forever the release of 1.0 waiting for
> > this
check output of
% grep 'proto=p9sk1' /mnt/factotum/ctl
make sure the right key is on top of the list.
2011/6/29 Nicolas Bercher :
> Hi,
>
> I read the man page saying how to unlock the screenshot. But for sure
> typing the password and then enter didn't work for me. Moreover, it is a
> little d
Thanks for this. Two notes:
>Re-reading it, it's not "all ligatures" that are gone with
"Unicode-compliant fonts", but it spoke about the em- and en-dashes and
double quotes. So on these ones, I plead guilty.
Alright. Not a big deal, it seems to me.
>But starting with "modern fonts", "modern sy
On Thu Jun 30 10:52:40 EDT 2011, yari...@gmail.com wrote:
> check output of
> % grep 'proto=p9sk1' /mnt/factotum/ctl
>
> make sure the right key is on top of the list.
that doesn't seem like a reasonable way to select a key.
i don't see anything in factotum(4) that says that the the ctl
file has
On Thu, Jun 30, 2011 at 10:51 AM, Karljurgen Feuerherm
wrote:
> Thanks for this. Two notes:
>
>>Re-reading it, it's not "all ligatures" that are gone with
> "Unicode-compliant fonts", but it spoke about the em- and en-dashes and
> double quotes. So on these ones, I plead guilty.
>
> Alright. Not a
> also, the `protocol' of creating new /dev/pts/* is somewhat sensible, too. no
> ioctl(), just open /dev/pmtx, read a textual representation of an integer N
> and open /dev/pts/N.
nah, slave name is obtained with ptsname(master) which does
ioctl(TIOCGPTN) on Linux.
...
open("/dev/ptmx", O_RDWR|O
On Thu, Jun 30, 2011 at 10:51:53AM -0400, Karljurgen Feuerherm wrote:
> [...]
>
> >But starting with "modern fonts", "modern system", "archaic" and the
> like, it's like starting with: "only Adolf Hitler would still use not
> Unicode fonts".
>
> Looking here: http://scripts.sil.org/cms/scripts/pa
> I don't despise XeTeX. Nor Unicode. And I will take Unicode as is. But I
> will take TeX conventions as is too, since I'm working on TeX, and not
> another formatting system; since these conventions are confined to the
> ASCII subrange and only diverging from ASCII for the not glyph
> positions.
On Thu, Jun 30, 2011 at 12:31:17PM -0400, erik quanstrom wrote:
> > I don't despise XeTeX. Nor Unicode. And I will take Unicode as is. But I
> > will take TeX conventions as is too, since I'm working on TeX, and not
> > another formatting system; since these conventions are confined to the
> > ASCI
On Thu, Jun 30, 2011 at 07:00:48PM +0200, tlaronde wrote:
>
> This does not preclude the user from directly entering the unicode
> codepoint: in the TFM, if you want, the glyph information is duplicated,
> in the conventional plain TeX position, and as a literal in the unicode
> position.
More pr
--- On Tue, 28/6/11, erik quanstrom wrote:
>> Speaking of device numbers, I was surprised that Plan 9 has a similar
>> notion. However, they are only useful with kernel resident device
>> numbers. Does Plan 9 have some other mechanism that allow one to
>> identify the class of device/file ser
you still have to do something when multiple keys
match a particular operation. factotum uses the first.
> Sorry, I meant structured like the files in net. So, the uart could
> instead by structured as:
>
> eia/
> 0/
>ctl data status
> 1/
>ctl data status
usb serial does this, but unfortunately with a different naming
convention, and it's unfortunate since usb serial is then
19 matches
Mail list logo
