From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Proposed extension of show-paren-mode: Highlight parens when point is in L or R margin.
Date: Sun, 12 Oct 2014 10:18:46 +0000 [thread overview]
Message-ID: <20141012101846.GD3148@acm.acm> (raw)
In-Reply-To: <837g058xvd.fsf@gnu.org>
Hi, Eli.
On Sun, Oct 12, 2014 at 12:01:58PM +0300, Eli Zaretskii wrote:
> > Date: Sun, 12 Oct 2014 08:39:09 +0000
> > Cc: emacs-devel@gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> > > Thanks, but PLEASE don't call this a "margin".
[ ... ]
I've now called it "periphery" and for that doc-string first line I've
got:
"If non-nil, show parens when point is in the line's periphery."
[ ... ]
> Now, let me ask something about the feature as designed (sorry, don't
> have time right now to apply the patch and try this myself). Suppose
> I have this line of C code:
> FOO = xyz + foobar (a + (b * sqrt (c) - d) * e) - some; /* foo */
> Is the intent to have the parentheses of the call to 'foobar'
> highlighted when point is before "FOO" or inside the comment, but
> _not_ when point is between "xyz" and "foobar"? If so, this is soooo
> weird!
No. The only parens that get highlighted are ones at the beginning or
end of the code on the line (together with their partners).
> And what about this part of your description:
> > So: If point is in the LH margin of the code, highlight the first paren
> > on the line and its match, or failing that, the last paren on the line
> > with its match. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> When would the "first paren and its match" fail?
When the first non-whitespace character on the line isn't a paren.
> Does this mean you are not going to look past the line with point, i.e.
> multi-line parenthesized expressions will not be highlighted?
They will be highlighted when one of the parens touches the line's
periphery; it doesn't matter how far away the matching paren is, it will
get highlighted.
Anyhow, I've just blasted off an amended patch to Stefan. Maybe it's
almost all right now.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2014-10-12 10:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 13:43 Proposed extension of show-paren-mode: Highlight parens when point is in L or R margin Alan Mackenzie
2014-10-11 14:21 ` Eli Zaretskii
2014-10-12 8:39 ` Alan Mackenzie
2014-10-12 8:55 ` David Kastrup
2014-10-12 9:25 ` Alan Mackenzie
2014-10-12 9:01 ` Eli Zaretskii
2014-10-12 10:18 ` Alan Mackenzie [this message]
2014-10-12 4:12 ` Stefan Monnier
2014-10-12 10:04 ` Alan Mackenzie
2014-10-14 17:49 ` Stefan Monnier
2014-10-14 18:32 ` John Yates
2014-10-15 9:12 ` Alan Mackenzie
2014-10-15 22:38 ` Andy Moreton
2014-10-16 2:43 ` Stefan Monnier
2014-10-16 9:53 ` Alan Mackenzie
2014-10-16 12:59 ` Stefan Monnier
2014-10-16 13:31 ` Alan Mackenzie
2014-10-16 14:37 ` Stefan Monnier
2014-10-16 15:46 ` Alan Mackenzie
2014-10-16 17:40 ` Stefan Monnier
2014-10-16 21:26 ` Alan Mackenzie
2014-10-17 0:14 ` Stefan Monnier
2014-10-14 21:50 ` João Távora
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=20141012101846.GD3148@acm.acm \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).