From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kayborad layout
Date: Thu, 25 Mar 2004 13:58:50 +0100 [thread overview]
Message-ID: <4351bbc250065a3710ed9abae0e8ca69@plan9.escet.urjc.es> (raw)
In-Reply-To: <0634c73cd642b5ea78ed90c2ac4cf00f@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Don't worry. It's always impressive how short
the problem detection <-> problem fixed cycle can be on
Plan 9. Our local unix users tend not to believe that I may talk
to them about a problem and then tell them it's fixed
in a day or even hours :-)
thanks a lot once moreⁱ
ⁱ - I think I'm going to write this line in an automated .signature to save
some work ☺
[-- Attachment #2: Type: message/rfc822, Size: 4145 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 91 bytes --]
Sorry about that. I'ld changed it a week ago on our systems and forgot
to update sources.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 2083 bytes --]
From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kayborad layout
Date: Thu, 25 Mar 2004 13:46:11 +0100
Message-ID: <cb546c164ec126554ccf284a7bfe9cf8@plan9.escet.urjc.es>
> I was expecting you to put /boot/es (or whatever in plan9.ini).
> Your change does sayve people that whopping 6 chars but I kind
> of liked it being explicit.
I think I created a patch fixing ascii too. It must not only
fix Spec, but also include all runes in all tables; to let kbmap(1)
recover to a known state before switching a map.
next prev parent reply other threads:[~2004-03-25 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 11:43 Tiit Lankots
2004-03-25 11:50 ` David Presotto
2004-03-25 12:46 ` Fco.J.Ballesteros
2004-03-25 12:54 ` David Presotto
2004-03-25 12:58 ` Fco.J.Ballesteros [this message]
2004-03-25 14:06 ` andrey mirtchovski
2004-03-25 11:45 Tiit Lankots
2004-03-25 11:56 Tiit Lankots
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4351bbc250065a3710ed9abae0e8ca69@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).