On Thu, Mar 15, 2018 at 18:55:22 +0000, Gregory White wrote:
> It doesn't seem to tolerate the "&" symbol in the filename or the
> path. I did some looking to see if an escape was needed for &, but did
> not find anything.
>From: Mike Miller [mailto:[hidden email]]
>Sent: Thursday, March 15, 2018 2:49 PM
>To: Gregory White <[hidden email]>
>Cc: [hidden email] >Subject: Re: print with ampersand (&) in path or name
>On Thu, Mar 15, 2018 at 18:55:22 +0000, Gregory White wrote:
>> It doesn't seem to tolerate the "&" symbol in the filename or the
>> path. I did some looking to see if an escape was needed for &, but did
>> not find anything.
>Can you please file a bug report at
I will do that.
>This should work. This does work for me on a GNU/Linux system, so may be something with the way external commands are called when printing to a file on Windows.
>Btw, it seems obvious to me that I would want to avoid any file or directory names that have '&' in them, but this may not be obvious to everyone, and I do think Octave should support this.
I don't like use of the ampersand for these things, but... getting people to not use R&D, V&V, or simile is already a lost battle. :-(