On Fri, 04 Feb 2005, David Kastrup said:
Nix <nix(a)esperi.org.uk> writes:
> but the single largest RSI-saver (voice recognition) doesn't work
> well when you enunciate as poorly and variably as I do. So a Maltron
> keyboard it is, and now, after only a few weeks, I can't imagine why
> these keyboards aren't in use *everywhere*. They whip the flat
> pasty white rear of QWERTY keyboards. :)
Please remember that the "R" in "RSI" stands for
"repetitive". RSI is
something you can't predict after only a few weeks. The question is
what will happen once your usage patterns and motoric patterns
Agreed: but what pain I had simply dissolved shortly after I started
using the new keyboard, and hasn't been back. (The RSI was light enough
that stopping typing for a few days made most symptoms fade completely
in any case; I'd not gone anywhere near as far as Ben. The only problem
was that starting typing again made things hurt within a quarter
hour... that doesn't happen anymore.
Downside: they're bloody expensive keyboards; not things to drop your
>> nix> Finsert_file_contents_internal: would that be
>> nix> If it is, I can spin a patch in the next day or so.
>> I don't know if it would be acceptable; I'll need to make time to
>> look at this and I also want a second opinion from "Dr." Wing. I
> Please! The last thing I want to do is cause a repeat of the
> XEmacs-21.4.8 fiasco.
A little fiasco now and then builds character.
> This is a completely tentative patch, bceause I'm still not
a) you have recently had some bit of recovery from severe RSI
I think I overspoke. It felt nasty, but I think it was just moderate.
Compared to Ben, it's probably `light'.
b) this RSI has struck as bad as to cut you off from computer
work pretty much completely
Only because I was being completely paranoid and saying `any pain, stop
right now' combined with very strict type-break.el timings (still in
force; fifteen minutes on, five minutes off, maximum of one-half day
spent doing any typing at all: work is annoyed, but there's nothing they
can do other than pay for expensive keyboards in the hope that things
improve). I've seen what *bad* RSI does and I don't want it coming
anywhere near me.
This crippled my *productivity*, but it didn't cripple *me*, if you see
what I mean. i.e., my disappearances have been preventative maintenance.
c) you have provided all the necessary details for the bug now,
describing it very completely so that people in the know can
recognize what to do and do it easily enough.
d) you show a lack of clue about the involved internals
yourself. So you obviously have to experiment around a lot, which
involves typing a lot, leafing through computerized documentation
and code a lot, prepare a complete patch including changelog entry
without even knowing whether the resulting code actually is the
right thing to do.
One ought to whack you with your Maltron keyboard. Though that may
just what you are in effect doing yourself.
I hope not!
With regard to RSI avoidance and speech recognition: there is just
that _amazing_ speech recognition technology that can deal with
varying pronunciation by using specialized dictionaries.
I've tried them (well, a couple of years back, when a friend got
one). They have a ~40% error rate with me.
So will someone please pick up what Nix provided here and finish the
matter off before he incapacitates himself over it?
I'm trying to avoid that (hence the intermittent online presence).
Most of the package I posted today was written over the preceding week
(I had the germ of the idea last weekend). I'd not try writing that
much in one day at the moment.
I am completely clueless about the matter at hand, but since dired
stuff are probably supposed to be loosely synchronized with Emacs and
I can't remember having seen any symptom like this on Emacs, maybe
I think the coding-system stuff is different.
`Blish is clearly in love with language. Unfortunately,
language dislikes him intensely.' --- Russ Allbery