Sat 12 Oct 2013 10:52:16 PM UTC, comment #13:
Oops. I forgot to push from my repository. It's in the main repo now.
|
Sat 12 Oct 2013 08:53:35 PM UTC, comment #12:
Rik, I wasn't sure from your last comment if you meant you were going to push it so I didn't push. I don't see it on the main repo yet though.
|
Sat 12 Oct 2013 05:54:43 PM UTC, comment #11:
I applied Mike's patch and crossed the bug off the must-fix list (http://wiki.octave.org/3.8_Bug_Fix_List).
|
Sat 12 Oct 2013 03:43:33 PM UTC, comment #10:
I was thinking just for this case, but I also wasn't sure where the error was coming from.
I think the patch is fine for now. At least it avoids the infinite loop.
|
Sat 12 Oct 2013 03:32:16 PM UTC, comment #9:
Oops, attached now.
Do you mean make it a warning for just this case, or change octave_getcwd to only generate a warning and return an empty string? I wonder if the latter would have unintended consequences.
(file #29361)
|
Sat 12 Oct 2013 03:22:38 PM UTC, comment #8:
BTW, I don't see a patch attached.
|
Sat 12 Oct 2013 03:18:59 PM UTC, comment #7:
I know in comment #1 jwe mentions the best solution might be for Octave to keep what it thinks the current working directory is. This would probably bring other benefits as well. My patch does not address that, just the immediate problem.
|
Sat 12 Oct 2013 03:15:39 PM UTC, comment #6:
Should the error be a warning instead?
Otherwise it seems OK to me.
|
Sat 12 Oct 2013 03:13:02 PM UTC, comment #5:
Attached patch fixes the infinite loop. Not pushed yet because I'm not sure what string is best to present in place of the directory. This patch does the following:
If no one objects I can push this fix.
|
Thu 29 Aug 2013 08:30:55 PM UTC, comment #4:
Bug is still here, 8/29/13.
|
Fri 19 Apr 2013 11:45:00 PM UTC, comment #3:
Confirmed still present in the development version, if and only if PS1 contains the \W or \w escape sequences.
|
Wed 19 Jan 2011 01:08:48 PM UTC, comment #2:
Oh I see it's not the Octave's default, but my own in $HOME/.octaverc:
Unfortunately Octave cannot be interrupted by Ctrl-C in the infinite loop but it must be killed completely.
|
Wed 19 Jan 2011 11:15:14 AM UTC, comment #1:
I think this could be avoided by having Octave maintain an internal idea of what the current working directory is and that is only updated when chdir is called. But unfortunately, I think this will require more changes that I'd like to make right before the release.
BTW, in the Octave sources, the default value of the Octave prompt is
so I guess someone else is giving you the value you have.
|
Wed 19 Jan 2011 10:03:08 AM UTC, original submission:
If current working directory where Octave runs is removed (by another process, for example) then:
1. If PS1 contains cwd, e.g. the default value of W|\t|\#>
then Octave goes into an infinite loop saying:
2. If PS1 does not contain cwd, then it says:
Could 1. behave as 2.?
|