unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: giecrilj@stegny.2a.pl (Krzysztof =17belechowski)
Cc: 10106@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#10106: 23.2; how to pass command arguments to gud-go
Date: Tue, 10 May 2022 06:24:16 +0200	[thread overview]
Message-ID: <87fslikob3.fsf@gnus.org> (raw)
In-Reply-To: <877h2spg7e.fsf@linux-4qi7.site> (Krzysztof's message of "Tue, 22 Nov 2011 12:08:37 +0100")

giecrilj@stegny.2a.pl (Krzysztof =17belechowski) writes:

> <menu-bar> <tools> <gdb> ls C-u <tool-bar> <go> 
>
> The command, when invoked under C-u, should ask for command line
> arguments to pass to the program.
>
> Example interaction:
> *Minibuffer* Run with arguments: -l

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

I'm not quite sure I understand the request, but you just want to be
able to type in further switches to be used here?

  ;; TODO Why arg here?
  (gud-def
   gud-go (gud-call (if gdb-active-process
                        (gdb-gud-context-command "-exec-continue")
                      "-exec-run") arg)
   nil "Start or continue execution.")

That seems easy enough to add, I guess.

> Also, please add a keyboard binding for gud-go (e.g. C-c !)

There's:

gud-until is an interactive compiled Lisp function.
It is bound to C-x C-a C-u.

So perhaps something else under C-x C-a?

I don't use these functions a lot myself, so I don't really have much of
an opinion on either requests.  Perhaps Eli has an opinion here; added
to the CCs.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-10  4:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 11:08 bug#10106: 23.2; how to pass command arguments to gud-go Krzysztof =17belechowski
2022-05-10  4:24 ` Lars Ingebrigtsen [this message]
2022-05-10 11:56   ` Eli Zaretskii
2022-05-11 11:31     ` Lars Ingebrigtsen
2022-05-11 12:02       ` Eli Zaretskii
2022-05-11 12:27         ` Lars Ingebrigtsen

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/emacs/

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

  git send-email \
    --in-reply-to=87fslikob3.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=10106@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=giecrilj@stegny.2a.pl \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).