From: Heime <heimeborgia@protonmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Drew Adams <drew.adams@oracle.com>,
Pierre Rouleau <prouleau001@gmail.com>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: [External] : Re: Matching parenthesis for long constructs
Date: Thu, 09 May 2024 18:57:58 +0000 [thread overview]
Message-ID: <d4ttro1zBkzoXNM13wIcAdTOdQIz2ym8p7x_EadvSQGzcrffac_OCvgHKJooVoFsFe2ZV3gWNKXSEVLcFcKED_r158q0KA5iCXc8Qa4ftyk=@protonmail.com> (raw)
In-Reply-To: <CAP_d_8XmVj95GVfC6Q+Om9Z0Okm-z+H7BvB+qh3orfcq+odVAg@mail.gmail.com>
On Friday, May 10th, 2024 at 6:24 AM, Yuri Khan <yuri.v.khan@gmail.com> wrote:
> On Thu, 9 May 2024 at 23:59, Heime heimeborgia@protonmail.com wrote:
>
> > Try going to the closing parenthesis of a pcase construct where the closing
> > parenthesis start to blink. You are effectively within the construct that
> > encloses the pcase (the construct at the next higher level) and you get shown
> > that rather than the pcase construct in the echo area.
> >
> > You cannot tell what you are closing off.
>
>
> Are you typing programs from a print magazine? Because in real
> programming you close off parentheses as you open them (or
> electric-pair-mode or smartparens does it for you), then you go inside
> and add inner forms, keeping parentheses balanced most of the time.
Most times I am changing existing code, and encounter this problem whilst
removing things. I quite like the idea of typing programs from a print
magazine like byte magazine from 1975. Quite a shame people can't do that
anymore.
next prev parent reply other threads:[~2024-05-09 18:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 12:33 Matching parenthesis for long constructs Heime
2024-05-09 14:00 ` Pierre Rouleau
2024-05-09 14:22 ` Heime
2024-05-09 14:48 ` [External] : " Drew Adams
2024-05-09 15:35 ` Emanuel Berg
2024-05-11 1:43 ` Drew Adams
2024-05-11 5:40 ` tomas
2024-05-09 16:58 ` Heime
2024-05-09 17:45 ` Drew Adams
2024-05-09 17:52 ` Eli Zaretskii
2024-05-09 18:09 ` Emanuel Berg
2024-05-11 6:27 ` Eli Zaretskii
2024-05-09 18:24 ` Yuri Khan
2024-05-09 18:29 ` Emanuel Berg
2024-05-09 18:57 ` Heime [this message]
2024-05-09 19:45 ` Heime
2024-05-09 19:46 ` Yuri Khan
2024-05-09 20:44 ` Drew Adams
2024-05-09 15:14 ` Pierre Rouleau
2024-05-09 15:38 ` Emanuel Berg
2024-05-11 4:58 ` Pierre Rouleau
2024-05-09 14:24 ` Emanuel Berg
2024-05-09 14:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-05-09 21:49 ` Daniel Martín
2024-05-10 19:38 ` tpeplt
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='d4ttro1zBkzoXNM13wIcAdTOdQIz2ym8p7x_EadvSQGzcrffac_OCvgHKJooVoFsFe2ZV3gWNKXSEVLcFcKED_r158q0KA5iCXc8Qa4ftyk=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=prouleau001@gmail.com \
--cc=yuri.v.khan@gmail.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.
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).