From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: "up" and "down", "top" and "bottom" again
Date: Wed, 06 Jun 2007 21:46:00 -0000 [thread overview]
Message-ID: <4666E3E9.30400@redhat.com> (raw)
Picking up from today's meeting and going through more carefully.
"up" and "down": The just problem seems to just be with the commands.
Long long ago it was agreed that "up" would behave as "inner" (i.e. go
towards the top) and "down" as "outer" (i.e., go towards the bottom) and
not mimic gdb. It seems to have been switched somehow. See:
http://sources.redhat.com/ml/frysk/2006-q4/msg00196.html
"where": The possability of, in the HPD, printing stacks bottom-to-top
instead of top-to-bottom came up. That way the last stack printed would
be the outer-most (and so wouldn't be scrolled off the screen). That
would however make it inconsistent with fstack and the gui, and put the
"top" frame at the "bottom" of the screen.
"inner" and "outer": Nurden? suggested adding these as commands to just
get rid of the confusion. Sounds like a good idea :-)
Andrew
reply other threads:[~2007-06-06 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4666E3E9.30400@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).