From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, 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 18:23:36 +0000 [thread overview]
Message-ID: <Y+kuqIkrrRhrDHMg@ACM> (raw)
In-Reply-To: <838rh2hmbh.fsf@gnu.org>
Hello, Eli.
On Sun, Feb 12, 2023 at 18:37:22 +0200, Eli Zaretskii wrote:
> > Date: Sun, 12 Feb 2023 16:14:49 +0000
> > Cc: 61453@debbugs.gnu.org, acm@muc.de
> > From: Alan Mackenzie <acm@muc.de>
> > > How will this help? You will ask people to deliberately remove any
> > > delimiters from what they type? That's a terrible annoyance. It
> > > means, for example, that you cannot simply copy/paste code fragments.
> > It seems that the same problem exists with pp.
> 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?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-02-12 18:23 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 [this message]
2023-02-12 18:33 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+kuqIkrrRhrDHMg@ACM \
--to=acm@muc.de \
--cc=61453@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.