unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 61453@debbugs.gnu.org
Subject: bug#61453: It is annoying to have to type 'print foo' before each .gdbinit command.
Date: Sun, 12 Feb 2023 20:33:07 +0200	[thread overview]
Message-ID: <831qmuhgyk.fsf@gnu.org> (raw)
In-Reply-To: <Y+kuqIkrrRhrDHMg@ACM> (message from Alan Mackenzie on Sun, 12 Feb 2023 18:23:36 +0000)

> Date: Sun, 12 Feb 2023 18:23:36 +0000
> Cc: 61453@debbugs.gnu.org, acm@muc.de
> From: Alan Mackenzie <acm@muc.de>
> 
> > Which is why we also have "pr".
> 
> OK, but that doesn't help with the annoyance in xpr and friends.
> Anybody typing an expression with spaces into xpr can continue to use
> print followed by xpr without arguments.  For the usual case, when
> there's exactly one argument, my patch resolves the annoyance.  It now
> handles the $argc > 1 case as an error.
> 
> So, why not install this patch in master, now?

I don't like it, sorry.  It is not clean enough, and it goes against
the overall consistency of the commands we have in src/.gdbinit.

You can always have any commands you want in your own ~/.gdbinit.





  reply	other threads:[~2023-02-12 18:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 13:01 bug#61453: It is annoying to have to type 'print foo' before each .gdbinit command Alan Mackenzie
2023-02-12 13:08 ` Eli Zaretskii
2023-02-12 13:34   ` Alan Mackenzie
2023-02-12 14:04     ` Eli Zaretskii
2023-02-12 14:42       ` Alan Mackenzie
2023-02-12 14:49         ` Eli Zaretskii
2023-02-12 16:14           ` Alan Mackenzie
2023-02-12 16:37             ` Eli Zaretskii
2023-02-12 18:23               ` Alan Mackenzie
2023-02-12 18:33                 ` Eli Zaretskii [this message]
2023-02-12 18:56                   ` Alan Mackenzie
2023-02-12 19:27                     ` Eli Zaretskii

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=831qmuhgyk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61453@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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).