From: Glenn Morris <rgm@gnu.org>
To: 19809-done@debbugs.gnu.org
Subject: bug#19809: 24.4; f90-beginning-of-subprogram wrong behavior with string continuation
Date: Tue, 24 Feb 2015 02:18:08 -0500 [thread overview]
Message-ID: <eqbnkjpykv.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CADOJ32BFNsSJDV3229-bN242KVt+g7hZjptUNx6oVR0eE4b0ng@mail.gmail.com> (Raul Laasner's message of "Wed, 11 Feb 2015 21:33:37 +0200")
Version: 25.1
I added some support for this in e8a11db, but I suspect there are more
places where f90.el assumes strings are not continued in that way. It
doesn't seem especially important to me to track them all down.
prev parent reply other threads:[~2015-02-24 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 20:25 bug#19809: 24.4; f90-beginning-of-subprogram wrong behavior with string continuation Raul Laasner
2015-02-11 1:27 ` Glenn Morris
2015-02-11 9:53 ` Raul Laasner
2015-02-11 19:09 ` Glenn Morris
2015-02-11 19:33 ` Raul Laasner
2015-02-24 7:18 ` Glenn Morris [this message]
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=eqbnkjpykv.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=19809-done@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).