unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: 14399@debbugs.gnu.org
Subject: bug#14399: octave-mode bug
Date: Thu, 28 Nov 2013 08:37:21 +0100	[thread overview]
Message-ID: <877gbtasem.fsf@Rainer.invalid> (raw)
In-Reply-To: <230D3614-8BA1-4161-9B2E-6174894BF1D4@partech.com>

Stefan Monnier writes:
> That's the part I knew already ;-)
>
> But in which way is 
>
>    a = [ foo;...
>          bar ]
>
> different from
>
>    a = [ foo
>          bar ]
> or
>    a = [ foo;
>          bar ]

For these three examples there is no difference because the newlines and
whitespace the continuation marker gobbles up wouldn't terminate or
alter the statement.  On the other hand

a = [ foo ...
      bar ]

_is_ different (introducing another column rather than a row).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds






  parent reply	other threads:[~2013-11-28  7:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 17:05 bug#14399: octave-mode bug Tom Olin
2013-05-15 12:00 ` Leo Liu
2013-05-17 23:13   ` Leo Liu
2013-11-22  2:11     ` Leo Liu
2013-11-22 14:27       ` Stefan Monnier
2013-11-22 14:57         ` Rüdiger Sonderfeld
2013-11-23  2:03           ` Stefan Monnier
2013-11-28  4:40             ` Stefan Monnier
2013-11-30 13:09               ` Tom Olin
2013-11-28  7:37             ` Achim Gratz [this message]
2013-11-30 17:19               ` Stefan Monnier
2013-12-02 14:51                 ` Rüdiger Sonderfeld
2013-12-02 15:15       ` Stefan Monnier
2013-12-02 15:58         ` Leo Liu
2013-12-02 16:08           ` Stefan Monnier
2013-12-03 14:56           ` Tom Olin
2013-12-03 18:32             ` Rüdiger Sonderfeld
2013-12-03 18:45               ` Tom Olin
2013-12-03 21:00               ` Tom Olin

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=877gbtasem.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=14399@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).