unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ben Pfaff <blp@cs.stanford.edu>
Cc: PSPP Development Mailing List <pspp-dev@gnu.org>,
	mail@vasilij.de, John Darrington <john@darrington.wattle.id.au>,
	emacs-devel@gnu.org
Subject: Re: Fwd: [ELPA] New package: pspp-mode.el for PSPP/SPSS syntax highlighting
Date: Sun, 05 Jul 2020 18:01:06 -0400	[thread overview]
Message-ID: <jwvv9j1myhm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAA_G9+hib7Mtwi4e4LE3nPDLc03Xrk+Q2bFo2NZ-VNr=AN7j5Q@mail.gmail.com> (Ben Pfaff's message of "Sun, 5 Jul 2020 10:16:19 -0700")

Hi Ben,

Thanks for chiming in,

> SPSS syntax is bizarre. It has two modes: "batch" and "interactive" mode.

Aha!

> A syntax file might be written in either syntax.  There's no way to
> easily guess which one.
>
> In "interactive" syntax, a command ends with a line that ends with . or
> with a blank line.

So that's the syntax that's documented in the Texinfo, and that's the
syntax handled by `segmenter_parse_comment_1__`?

> PSPP can be configured to interpret files in either syntax mode. It's a pain
> requiring users to do this, so by default it tries to guess on a line-by-line
> basis: if a line is not indented and if it begins with keywords that are an
> SPSS command name, then it assumes that it is the beginning of a command
> and that the previous command ended. This is nasty also, but it works
> well most of the time regardless of what syntax mode the file was written
> in.

Thanks.
I guess `pspp-mode.el` should try to reproduce the same DWIMish behavior.

Yet another question: do comments (either "*" or "COMMENT") always start
in column 0 or can they start indented or even on the same line as some
other command, as in:

    input program.  * let's get started.

> I think that's why the file above gets treated the way it does.
>
> Maybe PSPP should treat comment commands specially. That would
> be yet another special case in the lexer/parser, but maybe it is warranted.

Of course, I prefer it when comments are handled in the lexer rather
than in the parser, so they can occur anywhere between tokens, but
I expect that this boat has sailed ;-)


        Stefan




  reply	other threads:[~2020-07-05 22:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jwvr1twzlte.fsf-monnier+emacs@gnu.org>
2020-06-30 21:55 ` Fwd: [ELPA] New package: pspp-mode.el for PSPP/SPSS syntax highlighting Friedrich Beckmann
2020-07-04  9:20   ` John Darrington
2020-07-04 13:12   ` Stefan Monnier
2020-07-04 15:15     ` John Darrington
2020-07-04 22:45       ` Stefan Monnier
2020-07-05  6:06         ` John Darrington
2020-07-05 14:59           ` Stefan Monnier
2020-07-05 17:17             ` Ben Pfaff
2020-07-05 17:16         ` Ben Pfaff
2020-07-05 22:01           ` Stefan Monnier [this message]
2020-07-05 22:17             ` Ben Pfaff
2020-07-05  9:44       ` Friedrich Beckmann
2020-07-05 11:18         ` John Darrington
2020-07-05 16:51         ` Sean Whitton
2020-07-05 17:14           ` Friedrich Beckmann
2020-07-05 18:35           ` John Darrington
2020-07-05 18:50             ` tomas
2020-07-05 20:20             ` Sean Whitton
2020-07-06  5:53               ` Dmitry Alexandrov
2020-07-06  6:01                 ` Sean Whitton
2020-07-06  6:38                   ` Dmitry Alexandrov
2020-07-07  4:51                     ` Sean Whitton

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=jwvv9j1myhm.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=blp@cs.stanford.edu \
    --cc=emacs-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    --cc=mail@vasilij.de \
    --cc=pspp-dev@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).