[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#10106: 23.2; how to pass command arguments to gud-go
From: |
Eli Zaretskii |
Subject: |
bug#10106: 23.2; how to pass command arguments to gud-go |
Date: |
Tue, 10 May 2022 14:56:11 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 10106@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 10 May 2022 06:24:16 +0200
>
> 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.
The first request indeed makes sense, I think. We'd need to use the
-exec-arguments command before -exec-run.