all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Okam via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 47261@debbugs.gnu.org
Cc: monnier@iro.umontreal.ca
Subject: bug#47261: Destructuring with Pcase without assigning values
Date: Fri, 19 Mar 2021 13:47:29 +0000	[thread overview]
Message-ID: <cc1975f5-4e2f-2a62-5141-062422a754a2@protonmail.com> (raw)

X-Debbugs-Cc: monnier@iro.umontreal.ca

Hello.

For a Pcase pattern, it would be convenient to have Pcase destructure
the pattern and have a way to see what values Pcase would like to assign
to variables within the pattern.

This would allow one to know the variables found in the pattern and to
manipulate the values that Pcase would like to assign, instead of just
letting `pcase` assign them.

This was asked about on the Help mailing list:
https://lists.gnu.org/archive/html/help-gnu-emacs/2021-03/msg00089.html

Thank you.






             reply	other threads:[~2021-03-19 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 13:47 Okam via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-19 21:45 ` bug#47261: Destructuring with Pcase without assigning values Stefan Monnier
2021-04-17  1:24   ` Okam via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-17  3:22     ` Stefan Monnier
     [not found]       ` <1dacded9-3e40-bc02-56c7-a157d739ffb7@protonmail.com>
2021-04-19 22:06         ` bug#47261: Fwd: " Earl Hyatt via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]         ` <jwveef84hcl.fsf-monnier+emacs@gnu.org>
     [not found]           ` <4925d1a5-4669-8290-e534-1662f13ca183@protonmail.com>
2021-04-19 22:10             ` Okam via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 18:36   ` 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

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

  git send-email \
    --in-reply-to=cc1975f5-4e2f-2a62-5141-062422a754a2@protonmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=47261@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=okamsn@protonmail.com \
    /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.