unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark Harig <idirectscm@aim.com>
To: bug-guile@gnu.org
Subject: Re: ,show repl command
Date: Sun, 23 Jan 2011 14:20:22 -0500	[thread overview]
Message-ID: <8CD8949B6F936FD-F84-18E69@webmail-d083.sysops.aol.com> (raw)
In-Reply-To: <AANLkTin1BD4C2MJ82gN8XH+mO5jDhNJY8r-webSr66wz@mail.gmail.com>

On Sun, Jan 23, 2011 at 07:53:14PM +0530, Ramakrishnan Muthukrishnan 
wrote:
> Not sure whether this is a bug.
>
> The Guile manual [1] mentions the existance of a repl command called
> `show'. When I tried this, I get the following message.
>
> scheme@(guile-user)> ,show
> Show Commands:
>
> While executing meta-command:
> ERROR: In procedure car:
> ERROR: Wrong type argument in position 1 (expecting pair): #f

I have seen this error for the `show' command, too, and a
similar error for `statistics'.  There are also a number of
errors in the help text from several commands (see below).

This is for guile 1.9.14.

Error 1)

scheme@(guile-user)> ,show w
While executing meta-command:
ERROR: In procedure car:
ERROR: Wrong type argument in position 1 (expecting pair): #f

scheme@(guile-user)> ,show copying
While executing meta-command:
ERROR: In procedure car:
ERROR: Wrong type argument in position 1 (expecting pair): #f

scheme@(guile-user)> ,show v
While executing meta-command:
ERROR: In procedure car:
ERROR: Wrong type argument in position 1 (expecting pair): #f


Error 2)

scheme@(guile-user)> ,statistics
GC times:                     0 /         7 times

Memory size:            current /     limit
                heap         #f /        #f cells
              malloc         #f /        #f bytes

Cells collected:           diff /     total
While executing meta-command:
ERROR: In procedure -:
ERROR: Wrong type argument in position 1: #f


Error 3)

scheme@(guile-user)> ,h -c step
Usage: step
Step until control reaches a different source location.

Step until control reaches a different source location.


NOTE: The same sentence is repeated twice.


Error 4)

scheme@(guile-user)> ,h -c step-instruction
Usage: step-instruction
Step until control reaches a different instruction.

Step until control reaches a different VM instruction.


NOTE: Nearly the same sentence is repeated twice.


Error 5)

scheme@(guile-user)> ,h -c next
Usage: next
Step until control reaches a different source location in the current 
frame.

Step until control reaches a different source location in the current 
frame.


NOTE: The same sentence is repeated twice.


Error 6)

scheme@(guile-user)> ,h -c next-instruction
Usage: next-instruction
Step until control reaches a different instruction in the current frame.

Step until control reaches a different VM instruction in the current 
frame.


NOTE: Nearly the same sentence is repeated twice.


Error 7)

scheme@(guile-user)> ,h -c traps
Usage: traps
Show the set of currently attached traps.

Show the set of currently attached traps (breakpoints and tracepoints).


NOTE: Repeated information that could be reduced to one
sentence.


Error 8)

scheme@(guile-user)> ,h del
Usage: delete IDX
Delete a trap.

Delete a trap.


NOTE: The same sentence is repeated twice.


Error 9)

scheme@(guile-user)> ,h -c disable
Usage: disable IDX
Disable a trap.

Disable a trap.


NOTE: The same sentence is repeated twice.


Error 10)

scheme@(guile-user)> ,h -c enable
Usage: enable IDX
Enable a trap.

Enable a trap.


NOTE: The same sentence is repeated twice.


Error 11)

scheme@(guile-user)> ,h -c registers
Usage: registers
Print registers.

Print the registers of the current frame.


NOTE: Repeated information that could be reduced to one
sentence.

--



  parent reply	other threads:[~2011-01-23 19:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 14:23 ,show repl command Ramakrishnan Muthukrishnan
2011-01-23 14:24 ` Ramakrishnan Muthukrishnan
2011-01-23 19:20 ` Mark Harig [this message]
2011-02-09  4:42   ` Mark Harig
2011-02-09  5:00     ` Mark Harig
2011-03-04  9:34     ` Andy Wingo
2011-01-26 22:43 ` Andy Wingo
2011-01-28 17:35   ` Andreas Rottmann

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8CD8949B6F936FD-F84-18E69@webmail-d083.sysops.aol.com \
    --to=idirectscm@aim.com \
    --cc=bug-guile@gnu.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).