unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Al Haji-Ali <abdo.haji.ali@gmail.com>
Cc: 40814@debbugs.gnu.org
Subject: bug#40814: 26.3; show-paren-mode hightlights parentheses at eol
Date: Sun, 13 Jun 2021 14:29:51 +0200	[thread overview]
Message-ID: <871r963q2o.fsf@gnus.org> (raw)
In-Reply-To: <CAAhfW2yq3CRG6eG-wad+K1Q-OUy-b1r+qXNPAhN3ooy7bJHgkw@mail.gmail.com> (Al Haji-Ali's message of "Fri, 24 Apr 2020 11:55:24 +0100")

Al Haji-Ali <abdo.haji.ali@gmail.com> writes:

> would highlight `(paren)` only if the point is at the end of the line,
> not the beginning. This would also be consistent with the following
> case
>
>    (paren1) some other text (paren2)
>
> where, correctly, (paren1) is highlighted if the point is in the
> beginning of the line and (paren2) is highlighted if the point is in
> the end of the line.

Looking at the code and the documentation, as far as I can tell, this is
working as designed (even if it's slightly eccentric).  With this
setting, when point is in the "periphery" of a line, it'll highlight the
closest parens -- if those parens are also in the "periphery".  Which is
what the manual says:

@vindex show-paren-when-point-in-periphery
@code{show-paren-when-point-in-periphery}, when non-@code{nil}, causes
highlighting also when point is in whitespace at the beginning or end
of a line, and there is a paren at, respectively, the first or last,
or the last, non-whitespace position on the line.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-06-13 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 10:16 bug#40814: 26.3; show-paren-mode hightlights parentheses at eol Abdo Haji-Ali
2020-04-24 10:37 ` Eli Zaretskii
2020-04-24 10:55   ` Al Haji-Ali
2021-06-13 12:29     ` Lars Ingebrigtsen [this message]

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=871r963q2o.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=40814@debbugs.gnu.org \
    --cc=abdo.haji.ali@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.
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).