unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Luca Cartasegna <cartasegna.luca@gmail.com>, 17222@debbugs.gnu.org
Subject: bug#17222: 24.3; In f90-mode variables declared in continuation lines are not colored.
Date: Tue, 17 May 2022 19:32:11 +0200	[thread overview]
Message-ID: <87ilq4kquc.fsf@gnus.org> (raw)
In-Reply-To: <FFF4C6D0-6B22-405C-9B81-616891CAC393@acm.org> ("Mattias Engdegård"'s message of "Tue, 17 May 2022 17:20:46 +0200")

Mattias Engdegård <mattiase@acm.org> writes:

> part at the end is a potential empty-string repetition that indicates an ambiguity which we'd like to remove.
> What is the desired grammar here? Moving to rx for clarity, the above snippet means
>
> (+ (* (not (in "\n!&")))
>   (? "&\n"))
>
> What about rewriting it as
>
> (: (* (not (in "\n!&")))
>   (* "&\n"
>      (* (not (in "\n!&")))))
>
> which should be equivalent but unambiguous?

Yes, I think that's correct.

> However there may be something more fundamentally wrong with the original change, because it only seems to work for me after loading a file, not when writing the code incrementally. More precisely, when I've typed
>
> program main
>  integer :: alpha, &&
>
> in a new buffer then everything looks correctly coloured, but if I add
>
>   beta
>
> to the next line then it isn't fontified at all. Saving and reloading the buffer helps. Can you confirm?

Yes.  I had forgotten all about the rules for multiline font locking
(i.e., (elisp)Multiline Font Lock).  So I think my changes here were
basically misguided, and this should be implemented in a totally
different way.

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





  reply	other threads:[~2022-05-17 17:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 14:45 bug#17222: 24.3; In f90-mode variables declared in continuation lines are not colored Luca Cartasegna
2022-05-11 14:12 ` Lars Ingebrigtsen
2022-05-17 15:20 ` Mattias Engdegård
2022-05-17 17:32   ` Lars Ingebrigtsen [this message]
2022-05-24 15:40     ` Mattias Engdegård
2022-05-24 16:03       ` Lars Ingebrigtsen
2022-05-24 18:18         ` Mattias Engdegård
2022-05-25  0:17           ` 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

  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=87ilq4kquc.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=17222@debbugs.gnu.org \
    --cc=cartasegna.luca@gmail.com \
    --cc=mattiase@acm.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).