From: Christopher Dimech <dimech@gmx.com>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Defun Self Documentation
Date: Thu, 5 Nov 2020 20:34:45 +0100 [thread overview]
Message-ID: <trinity-209a37ac-1939-40f7-a9f9-b40631d4ff44-1604604885713@3c-app-mailcom-bs14> (raw)
In-Reply-To: <X6Q/tuN+nXtrESc4@protected.rcdrun.com>
Yes, I really like minibuffer details on Closing parentheses.
> Sent: Thursday, November 05, 2020 at 7:08 PM
> From: "Jean Louis" <bugs@gnu.support>
> To: tomas@tuxteam.de
> Cc: "Christopher Dimech" <dimech@gmx.com>, help-gnu-emacs@gnu.org
> Subject: Re: Defun Self Documentation
>
> * tomas@tuxteam.de <tomas@tuxteam.de> [2020-11-05 19:02]:
> > On Thu, Nov 05, 2020 at 04:55:54PM +0100, Christopher Dimech wrote:
> > > Don't people find it tough to immediately figure out which bracket closes
> > > what? But if readers will thank me, I would certainly comply. I come from
> > > the C-Language as is evident.
>
> I can understand the problem. Here is short advise:
>
> - (setq electric-pair-mode t) ;; This will give automatic () instead of only (
> and it will work with [] and "", this helps to make sure what is closed
>
> - highlight matching parenthesis in menu and save options, that
> will give you flashing parenthesis and you will know what you
> are closing.
>
> - additionally you may see in minibuffer also first part of the
> list that you are closing
>
next prev parent reply other threads:[~2020-11-05 19:34 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 15:16 Defun Self Documentation Christopher Dimech
2020-11-05 15:45 ` tomas
2020-11-05 15:55 ` Christopher Dimech
2020-11-05 16:00 ` tomas
2020-11-05 16:10 ` Christopher Dimech
2020-11-05 18:08 ` Jean Louis
2020-11-05 19:34 ` Christopher Dimech [this message]
2020-11-05 16:15 ` Drew Adams
2020-11-05 16:27 ` Christopher Dimech
2020-11-05 16:41 ` Stefan Monnier
2020-11-05 16:51 ` Arthur Miller
2020-11-05 16:59 ` Christopher Dimech
2020-11-05 17:28 ` Stefan Monnier
2020-11-05 17:29 ` Michael Heerdegen
2020-11-05 17:50 ` Christopher Dimech
2020-11-05 19:35 ` Michael Heerdegen
2020-11-05 19:22 ` Joost Kremers
2020-11-05 19:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-05 19:50 ` Eli Zaretskii
2020-11-05 21:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 5:27 ` Eli Zaretskii
2020-11-06 7:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 7:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 7:45 ` Eli Zaretskii
2020-11-06 8:17 ` tomas
2020-11-06 8:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 8:45 ` tomas
2020-11-09 3:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 8:44 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-11-06 11:54 ` Eli Zaretskii
2020-11-06 12:12 ` Christopher Dimech
2020-11-06 17:36 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-11-06 18:03 ` Christopher Dimech
2020-11-09 3:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 18:39 ` Eli Zaretskii
2020-11-09 4:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09 3:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09 3:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09 3:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 11:10 ` Defun Self Documentation (let us do it different) Jean Louis
2020-11-09 4:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 17:02 ` Defun Self Documentation Stefan Monnier
2020-11-06 18:35 ` Eli Zaretskii
2020-11-06 18:50 ` Stefan Monnier
2020-11-06 19:07 ` Christopher Dimech
2020-11-06 19:23 ` Stefan Monnier
2020-11-06 19:41 ` Christopher Dimech
2020-11-05 16:07 ` Drew Adams
2020-11-05 18:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
-- strict thread matches above, loose matches on Subject: below --
2020-11-06 9:10 Anders Munch
2020-11-06 11:58 ` Eli Zaretskii
2020-11-06 15:33 Anders Munch
2020-11-06 15:48 ` Eli Zaretskii
2020-11-06 16:07 ` Christopher Dimech
2020-11-09 4:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09 4:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09 4:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09 13:32 ` Eric S Fraga
2020-11-11 15:34 ` Michael Heerdegen
2020-11-09 15:51 ` 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=trinity-209a37ac-1939-40f7-a9f9-b40631d4ff44-1604604885713@3c-app-mailcom-bs14 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@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.
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).