unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: npostavs@users.sourceforge.net
Cc: 25517@debbugs.gnu.org
Subject: bug#25517: 25.1.91; print-format specifier mistaken as comment
Date: Tue, 24 Jan 2017 16:35:01 +0100	[thread overview]
Message-ID: <5cfb7593-833a-5417-414e-3bf11f46c4d6@easy-emacs.de> (raw)
In-Reply-To: <87vat4tx2x.fsf@users.sourceforge.net>



On 24.01.2017 14:19, npostavs@users.sourceforge.net wrote:
> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>
>> See also png attached
>>
> It looks like the problem is that octave-mode-syntax-table sets single
> quotes as punctuation even though GNU Octave's manual says single quotes
> are string syntax [1].
>
> [1]:
> https://www.gnu.org/software/octave/doc/interpreter/String-Objects.html
>
> Does this fix it?
>
> --- i/lisp/progmodes/octave.el
> +++ w/lisp/progmodes/octave.el
> @@ -165,7 +165,7 @@ octave-mode-syntax-table
>       (modify-syntax-entry ?| "."   table)
>       (modify-syntax-entry ?! "."   table)
>       (modify-syntax-entry ?\\ "."  table)
> -    (modify-syntax-entry ?\' "."  table)
> +    (modify-syntax-entry ?\' "\""  table)
>       (modify-syntax-entry ?\` "."  table)
>       (modify-syntax-entry ?. "."   table)
>       (modify-syntax-entry ?\" "\"" table)
>

Thanks. That should be a useful cure in octave-mode.

A resp. fix seems needed in inferior-octave-mode-map.





  reply	other threads:[~2017-01-24 15:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 10:36 bug#25517: 25.1.91; print-format specifier mistaken as comment Andreas Röhler
2017-01-24 13:19 ` npostavs
2017-01-24 15:35   ` Andreas Röhler [this message]
2017-01-24 15:41     ` Noam Postavsky
2017-01-24 16:10       ` Andreas Röhler
2017-01-24 22:49         ` npostavs
2017-01-25  8:41           ` Andreas Röhler
2017-01-25 16:13             ` Noam Postavsky
2020-08-24 15:34   ` 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=5cfb7593-833a-5417-414e-3bf11f46c4d6@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=25517@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).