From: Juan Quintela <quintela@mandrakesoft.com>
To: slurn@verisign.com
Cc: george@mvista.com (george anzinger),
kaos@melbourne.sgi.com (Keith Owens),
kdb@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: kdb wishlist
Date: 08 May 2001 19:38:06 +0200 [thread overview]
Message-ID: <m2itjbspvl.fsf@trasno.mitica> (raw)
In-Reply-To: <200105081657.JAA05739@slurndal-lnx.verisign.com>
In-Reply-To: <200105081657.JAA05739@slurndal-lnx.verisign.com>
>>>>> "slurn" == slurn <slurn@verisign.com> writes:
>>
>> Keith Owens wrote:
>> >
>> > This is part of my kdb wishlist, does anybody fancy writing the code to
>> > add any of these features? It would be a nice project for anybody
>> > wanting to start on the kernel. Replies to kdb@oss.sgi.com please.
>> > Current patches at http://oss.sgi.com/projects/kdb/download/
>> >
>> > * Change kdb invocation key from ^A to ^X^X^X within 3 seconds. ^A is
>> > used by emacs, bash, minicom etc.
>> >
>> ^X^X swaps point and mark in emacs. One (well, I) often will do
>> ^X^X^X^X to examine where mark is and then return to point.
slurn> How about using the break condition instead. This is only for the
slurn> serial port, and most terminal emulators (e.g. kermit, minicom) provide
slurn> a means to generate a break condition on the serial port.
kdb uses BREAK in the serial port (that minicom uses C-a for sending a
break is an anecdote :) But the problem at hang is the console. I
vote for the ^X^X^X as I a think that it is not a difficult shortcut.
(and yes, I also use emacs and ^X^X all the time, but I think that
this combination is not specially bad, and I suppose that the pet
aplication of other people will have problems with something like:
^A^A^A that I never use).
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2001-05-08 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 12:09 kdb wishlist Keith Owens
2001-05-08 12:41 ` Tigran Aivazian
2001-05-08 15:56 ` george anzinger
2001-05-08 16:57 ` slurn
2001-05-08 17:38 ` Juan Quintela [this message]
2001-05-08 18:04 ` slurn
2001-05-08 18:15 ` mirabilos
-- strict thread matches above, loose matches on Subject: below --
2001-05-08 12:40 r1vamsi
2001-05-08 13:32 Manfred Spraul
2001-05-08 13:36 ` Keith Owens
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=m2itjbspvl.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=george@mvista.com \
--cc=kaos@melbourne.sgi.com \
--cc=kdb@oss.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=slurn@verisign.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.