Logged on to a local tournament server for the first time ever. Very excited to
actually be able to play at something approaching normal speed for the first
time ever.
I pick a Valk, get an Altar on Lvl1 and soon have Mjollnir. Starting well! But
whats with not being able to use the Alt key and whats with # commands? # is
lame, if people really play like that they are missing out on a much swifter way
to play. I grab a corpse, go to sacrifice it and then either I try to eat or sac
or something but my keystrokes get muddled by the new interface I am not used to
and it ends up - throwing an egg at the altar. Ugh!
God is now angry, duh! And I am hungry and foodless with a phat ass prayer
timeout.
From there I crawl arround for an amazingly long time fainting, finding a newt
hitting it with mjollnir and eating it, then quickly back to fainting, repeat,
repeat. This actually drags on through fluke after fluke finding scraps of food
just enough to lengthen it out to the next. I consider my only hope a horn of
plenty or big stock of rations.
Eventually Fatdick the Valkyrie gets nibbled to death by newts.
Lesson learned: pay stricter attention to lame new keyboard commands.
--
It is possible to use alt as a meta-key over telnet and ssh.
Most #-commands are 3 consecutive keystrokes rather than 2 concurrent
ones, so I'm not quite sure what you mean by "much swifter".
Up until fairly recent versions one also missed out on angering one's god
by praying accidentally through the proximity of Alt-p and Alt-o.
--
David Damerell <dame...@chiark.greenend.org.uk> flcl?
How?
--
"Sometimes I stand by the door and look into the darkness. Then I
am reminded how dearly I cherish my boredom, and what a precious
commodity is so much misery." -- Jack Vance
I use the DOS and Unix versions. I could use the NT version, but the DOS one
works on all of the PCs I have access to so it's good enough. Since the Unix
version might be used in a context without the alt function, I always use #.
So, the # is only lame if you know you'll always be using one version. Lowest
common denominator. Same as why I keep the graphics turned off.
In CRT there is an option "Use 8th bit for meta key". Don't know about
the others.
"David Damerell" <dame...@chiark.greenend.org.uk> wrote in message
news:RZr*dJ...@news.chiark.greenend.org.uk...
> Edgar Almox <al...@nospam.nospam> wrote:
> >I pick a Valk, get an Altar on Lvl1 and soon have Mjollnir. Starting well!
But
> >whats with not being able to use the Alt key and whats with # commands? # is
> >lame, if people really play like that they are missing out on a much swifter
> >way to play.
>
> Most #-commands are 3 consecutive keystrokes rather than 2 concurrent
> ones, so I'm not quite sure what you mean by "much swifter".
You are quite sure what I mean you just want to nit pick my wording, or at least
you could work it out if you wanted to understand rather than quibble. You just
said it. Most are 3, some are 4. I think it's quicker for the brain to think
alt-c than to think shift-#-something, then check if it needs another letter.
All of this would get trained into you over time regardless of method but I'm
bitching because my method doesn't work and I have to learn a new one. You just
disagree and prefer your own method.
> Up until fairly recent versions one also missed out on angering one's god
> by praying accidentally through the proximity of Alt-p and Alt-o.
Never been a problem for me. I also prefer Alt also because I have never liked
the idea of a generic # command, it makes more complete sense to me to have all
(or as many as possible) commands available directly with keys and 2 button
combos with alt cntrl and shift.
--
Ingo Rohlfs
My complaint against the # commands is that I can never tell when its going
to complete the command for me.
Its
# (a)djust
but its
# (co)nduct
It gets annoying if your not used to it.
> Seraph <Geoffr...@aol.com> writes:
>
>> My complaint against the # commands is that I can never tell when its
>> going to complete the command for me.
>> Its
>> # (a)djust
>
> Because #adjust is the only extended command that begins with a.
>
>> but its
>> # (co)nduct
>
> Because there is also #chat.
> It completes the command when there's only one possible command that
> begins with what you already typed after the #.
I am fully aware of the autocomplete option
My point was that if I type in "#ad" the program shouldnt spit out
"#adjustd" it should have the brains to not enter characters if they are
the next ones in sequence after the autocomplete feature does its thing.
I often type faster then I can read, and find it annoying when I go to
punch in an extended command and have to stop to check to see if the
program did something unexpected.
Oh, actually you meant "very marginally slower" - so, why do you care?
>said it. Most are 3, some are 4. I think it's quicker for the brain to think
>alt-c than to think shift-#-something, then check if it needs another letter.
Check? Check? Don't you learn after a couple of uses?
>>Up until fairly recent versions one also missed out on angering one's god
>>by praying accidentally through the proximity of Alt-p and Alt-o.
>Never been a problem for me.
No, because you have not been playing for long enough to have played those
versions.
Your wish is my command: (tty only, because that's all I ever use)
Index: nethack/win/tty/getline.c
diff -u nethack/win/tty/getline.c:1.3 nethack/win/tty/getline.c:1.3.6.2
--- nethack/win/tty/getline.c:1.3 Sat Oct 19 03:21:54 2002
+++ nethack/win/tty/getline.c Fri Nov 8 23:55:46 2002
@@ -59,6 +59,7 @@
Sprintf(toplines, "%s ", query);
Strcat(toplines, obufp);
if((c = Getchar()) == EOF) {
+ bufp = eos(bufp);
*bufp = 0;
break;
}
@@ -101,30 +102,43 @@
}
if(c == erase_char || c == '\b') {
if(bufp != obufp) {
+ int i;
+
bufp--;
- putsyms("\b \b");/* putsym converts \b */
+ putsyms("\b");
+ for (i = bufp; i < eos(bufp); i++)
+ putsyms(" ");
+ for (i = eos(bufp); i > bufp; i--)
+ putsyms("\b");
+ *bufp = 0;
} else tty_nhbell();
#if defined(apollo)
} else if(c == '\n' || c == '\r') {
#else
} else if(c == '\n') {
#endif
+ bufp = eos(bufp);
*bufp = 0;
break;
} else if(' ' <= (unsigned char) c && c != '\177' &&
(bufp-obufp < BUFSZ-1 && bufp-obufp < COLNO)) {
/* avoid isprint() - some people don't have it
' ' is not always a printing char */
+ int i;
+
*bufp = c;
bufp[1] = 0;
putsyms(bufp);
bufp++;
if (hook && (*hook)(obufp)) {
putsyms(bufp);
- bufp = eos(bufp);
+ /* pointer and cursor left where they were */
+ for (i = eos(bufp); i > bufp; i--)
+ putsyms("\b");
}
} else if(c == kill_char || c == '\177') { /* Robert Viduya */
/* this test last - @ might be the kill_char */
+ bufp = eos(bufp);
while(bufp != obufp) {
bufp--;
putsyms("\b \b");
@@ -162,7 +176,7 @@
/*
* Implement extended command completion by using this hook into
- * tty_getlin. Check the characters already typed, if they uniquely
+ * tty_getlin. Check the characters already typed, if they
* identify an extended command, expand the string to the whole
* command.
*
@@ -176,20 +190,13 @@
ext_cmd_getlin_hook(base)
char *base;
{
- int oindex, com_index;
+ int oindex;
- com_index = -1;
for (oindex = 0; extcmdlist[oindex].ef_txt != (char *)0; oindex++) {
if (!strncmpi(base, extcmdlist[oindex].ef_txt, strlen(base))) {
- if (com_index == -1) /* no matches yet */
- com_index = oindex;
- else /* more than 1 match */
- return FALSE;
+ Strcpy(base, extcmdlist[oindex].ef_txt);
+ return TRUE;
}
- }
- if (com_index >= 0) {
- Strcpy(base, extcmdlist[com_index].ef_txt);
- return TRUE;
}
return FALSE; /* didn't match anything */
--
++acr@,ka"
> Jukka Lahtinen wrote:
>> Seraph <Geoffr...@aol.com> writes:
>>> Jukka Lahtinen <juk...@despammed.com> wrote in
>>> > It completes the command when there's only one possible command
>>> > that begins with what you already typed after the #.
>>>
>>> My point was that if I type in "#ad" the program shouldnt spit out
>>> "#adjustd" it should have the brains to not enter characters if they
>>> are the next ones in sequence after the autocomplete feature does
>>> its thing.
>>
>> Yes, the autocomplete could be improved there.
>> (Anybody out there to write a patch..?)
>
> Your wish is my command: (tty only, because that's all I ever use)
> [Snip patch code]
This is great, thanks.
And tty is all I use, so thats fine for me.