From: Stefan Kangas <stefankangas@gmail.com>
To: "Harald Jörg" <haj@posteo.de>, 28962@debbugs.gnu.org
Subject: bug#28962: A workaround to this issue is available in cperl-mode
Date: Thu, 27 Aug 2020 02:36:56 -0700 [thread overview]
Message-ID: <CADwFkmkgpAb-8LKOZLAo0UteUqcmi9n-5NrOPCH4aAcdVKbe3w@mail.gmail.com> (raw)
In-Reply-To: <5bbbe7e1-9d77-277a-cf7c-86ea2b134de8@posteo.de>
Harald Jörg <haj@posteo.de> writes:
> After some more digging (my experience with elisp is still limited)
> I found that the problem can be avoided by using `insert-and-inherit'
> instead of `insert'. cperl-mode uses text properties to detect the
> HEREiness of buffer contents - and `insert' just doesn't provide them.
>
> So, the problem only occurs when text is inserted via elisp code. It
> can be avoided by using `insert-and-inherit', or, if one can't modify
> the function, recovered from by calling `cperl-find-pods-heres'. In
> my eyes this is good enough. It seems that the reporter wasn't aware
> of either possibility, so maybe they're happy if we tell them about
> the workarounds - and then close as wontfix.
Makes sense to me. I think you should do that.
next prev parent reply other threads:[~2020-08-27 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 23:13 bug#28962: inserting newline at start of line in HERE doc breaks syntax highlighting Troy Hinckley
2020-08-26 16:26 ` bug#28962: A workaround to this issue is available in cperl-mode Harald Jörg
2020-08-26 20:21 ` Stefan Kangas
2020-08-27 8:58 ` Harald Jörg
2020-08-27 9:36 ` Stefan Kangas [this message]
2021-08-23 10:50 ` bug#28962: (no subject) Harald Jörg
2021-08-31 7:04 ` bug#28962: cperl-mode: Inserting text into here-documents now works Harald Jörg
2021-08-31 9:12 ` Vincent Lefevre
2021-08-31 11:56 ` bug#14343: " Harald Jörg
2021-08-31 12:08 ` Vincent Lefevre
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=CADwFkmkgpAb-8LKOZLAo0UteUqcmi9n-5NrOPCH4aAcdVKbe3w@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=28962@debbugs.gnu.org \
--cc=haj@posteo.de \
/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).