From: Corwin Brust <corwin@bru.st>
To: "Harald Jörg" <haj@posteo.de>
Cc: emacs-devel@gnu.org
Subject: Re: Enhancing cperl-mode
Date: Mon, 19 Jun 2023 16:49:49 -0500 [thread overview]
Message-ID: <CAJf-WoQxx3++vyCSd5GmBerb7qk6OUwEczyJMjnuTfZyeYRpZg@mail.gmail.com> (raw)
In-Reply-To: <87352nbe19.fsf@oook.m.uunet.de>
On Mon, Jun 19, 2023 at 11:41 AM Harald Jörg <haj@posteo.de> wrote:
>
> Corwin Brust <corwin@bru.st> writes:
> "live", but it needs preparation. I made a proof-of-concept, but the
> implementation is crap. It still hangs around at
> https://github.com/HaraldJoerg/cperl-mode/, but I more or less stopped
> working on it when I started to contribute to the savannah repository.
>
POC is much; thank you, friend I am warned :D
I will report back.
>
> I'm a bit stuck with indentation, where the code in cperl-mode is
> messy. Keywords that are followed by a { code block } sometimes need a
> semicolon, and sometimes they don't, and cperl-mode needs to understand
> this in order to decide whether the next line is a continuation line or
> a new statement.
I will come back on this another time (if someone wiser doesn't reveal
more than --I think-- I know before that).
> activities. I'm also interested to get cperl-mode published via ELPA,
> so that it can be used once Perl 5.38 is out.
Sounds like a good plan and I'm proud to be a part of it <g>
Indeed,
> --
> Cheers,
> haj
Corwin
next prev parent reply other threads:[~2023-06-19 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 10:14 Does Emacs need two Perl modes? Peter Oliver
2023-06-18 12:15 ` Po Lu
2023-06-18 12:56 ` Jens Schmidt
2023-06-19 13:01 ` Corwin Brust
2023-06-19 14:34 ` Enhancing cperl-mode (was: Re: Does Emacs need two Perl modes?) Harald Jörg
2023-06-19 14:58 ` Corwin Brust
2023-06-19 16:41 ` Enhancing cperl-mode Harald Jörg
2023-06-19 21:49 ` Corwin Brust [this message]
2023-06-20 2:57 ` Does Emacs need two Perl modes? Richard Stallman
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=CAJf-WoQxx3++vyCSd5GmBerb7qk6OUwEczyJMjnuTfZyeYRpZg@mail.gmail.com \
--to=corwin@bru.st \
--cc=emacs-devel@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).