unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: haj@posteo.de (Harald Jörg)
To: 28962@debbugs.gnu.org
Subject: bug#28962: (no subject)
Date: Mon, 23 Aug 2021 10:50:20 +0000	[thread overview]
Message-ID: <87sfz0305v.fsf@hajtower> (raw)
In-Reply-To: <CALOSHoQ9EdBmx_u3GUSmU5J+=FmQxOd_c+s=8NLknXcjxFmtpg@mail.gmail.com>

merge 28962 14343
thanks

After some more digging, I'm merging this bug with Bug#14343.

The root cause of both bugs is the same: Here-documents in CPerl mode
are marked with text properties.  Normal editing (in Emacs: via
`self-insert-command' will make new characters inherit from their
surroundings, so all is fine.

If, however, text is entered with another elisp function, then no
automatic inheritance takes place.  Examples are `insert' (this bug
report), `yank' (Bug#14343), but also `replace-string' if the first
character of the here-document gets replaced.

I am confident that this can be fixed if CPerl mode "steals" from Perl
mode and marks here-documents as c-style comments for fontification.
I am going to prepare a patch for this.

-- 
Cheers,
haj





  parent reply	other threads:[~2021-08-23 10:50 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
2021-08-23 10:50 ` Harald Jörg [this message]
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=87sfz0305v.fsf@hajtower \
    --to=haj@posteo.de \
    --cc=28962@debbugs.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).