unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: RE: Defun Self Documentation
Date: Thu, 5 Nov 2020 17:27:15 +0100	[thread overview]
Message-ID: <trinity-3c3283b0-dca7-4232-9d1a-a2b3a43234e9-1604593635402@3c-app-mailcom-bs14> (raw)
In-Reply-To: <5fcc7561-be7f-46b4-baa7-ab430ade5e74@default>


Following your argument through, and with show-paren-mode and blink-matching-paren-*,
I agree that it is not a problem having parentheses together.


> Sent: Thursday, November 05, 2020 at 5:15 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>, tomas@tuxteam.de
> Cc: help-gnu-emacs@gnu.org
> Subject: RE: Defun Self Documentation
>
> > 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.
>
> No.
>
> Turn on `show-paren-mode'.
>
> See also option `blink-matching-paren' and the
> other `blink-matching-paren-*' options.
>
> Double-click `mouse-1' on a paren, to select it,
> its match, and the text between them.
>
> `C-x C-x' bounces the cursor from end to end of
> the region.
>
> If code is formatted normally then you can
> pretty much count on the ))))) at the end of a
> sexp to balance what you'd expect.  Otherwise,
> someone (e.g. you) would already have fixed that.
>
> There's zero reason to put an opening or closing
> paren on a line by itself, unless you want to
> indicate something specially or add a comment in
> a particular way.
>
> `C-M-q' indents an entire sexp (e.g. a defun) in
> a conventional way.  It, `TAB', and other keys
> know Lisp syntax.
>
>



  reply	other threads:[~2020-11-05 16:27 UTC|newest]

Thread overview: 49+ 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
2020-11-05 16:15     ` Drew Adams
2020-11-05 16:27       ` Christopher Dimech [this message]
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

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-3c3283b0-dca7-4232-9d1a-a2b3a43234e9-1604593635402@3c-app-mailcom-bs14 \
    --to=dimech@gmx.com \
    --cc=drew.adams@oracle.com \
    --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).