From: Augusto Stoffel <arstoffel@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50236@debbugs.gnu.org
Subject: bug#50236: 27.2; electric-pair-mode is inconvenient in comint
Date: Mon, 22 Aug 2022 18:07:54 +0200 [thread overview]
Message-ID: <87v8qk5kit.fsf@gmail.com> (raw)
In-Reply-To: <87tu642sso.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 22 Aug 2022 17:37:27 +0200")
On Mon, 22 Aug 2022 at 17:37, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Augusto Stoffel <arstoffel@gmail.com> writes:
>
>> The following quick fix works for me:
>>
>> (defun electric-pair-skip-in-field (char)
>> (save-restriction
>> (narrow-to-region (field-beginning) (field-end))
>> (electric-pair-default-skip-self char)))
>>
>> (add-hook 'comint-mode-hook (lambda () (setq-local electric-pair-skip-self
>> 'electric-pair-skip-in-field)))
>>
>> Perhaps `electric-pair-default-skip-self' should always narrow to the
>> current field?
>
> That would make sense in this case... I'm trying to think of instances
> where it wouldn't make sense, and I can't think of any.
There's a second question of relevance here: would this change help
solving similar bugs in other modes? Consider for instance an Org file
like this
(
#+begin_src
f(<type close parens here>)
#+end_src
or a Markdown file like this
(
```
f(<type close parens here>)
```
Of course each of these modes could define their own
electric-pair-skip-self, but ideally a general mechanism to deal with
this situation should we provided.
So I guess my question here is: does it make sense for a major mode with
a notion of "code blocks" set field properties as part of the
font-locking? Or is there any reason not to mix up fields with
font-locking?
next prev parent reply other threads:[~2022-08-22 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 10:17 bug#50236: 27.2; electric-pair-mode is inconvenient in comint Augusto Stoffel
2022-02-06 9:33 ` Augusto Stoffel
2022-08-22 15:37 ` Lars Ingebrigtsen
2022-08-22 16:07 ` Augusto Stoffel [this message]
2022-08-23 9:53 ` Lars Ingebrigtsen
2022-08-23 16:56 ` Augusto Stoffel
2022-08-24 10:19 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8qk5kit.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=50236@debbugs.gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.