octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #49214] ".octave_hist" not updated if it is a


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #49214] ".octave_hist" not updated if it is a "hidden" Windows file
Date: Wed, 28 Sep 2016 20:13:31 +0000 (UTC)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40

Follow-up Comment #5, bug #49214 (project octave):

Renaming hidden files with a name starting with a period works perfectly fine
in Octave's file browser.

It does not work in Windows Explorer ("you must type a file name" -> it thinks
one entered just a file extension), nor in a cmd window "The system cannot
find the file specified." -> it is really hidden (!).

On Windows systems, files starting with a "." are not automatically hidden
files. That is simply how Windows file system work under Windows. That *nix
etc. treat Windows file systems like NTFS and FAT differently makes no
difference here.

I can confirm Hartmut's bug; just before closing Octave-GUI with .octave_hist
set to "hidden" I see two error messages flashing by.
A fix might be a question of merely a different system call (in the MinGW
libs, probably needing #ifdef WIN32 clauses), but the "bug" may also be
associated with more fundamental issues on Windows and thus harder to solve
(if at all possible)

"history_save" returns 1 but it didn't really update the file.

>> history -w
error: history: writing file 'C:\Users\philip\.octave_hist': Permission
denied


As there is a workaround by simply leaving .octave_hist to be not hidden I
fully agree with lowering priority and severity.

BTW, IIRC jwe has adapted .octave_hist processing some time ago (a year+ ?)
related to an old bug report that may even have been entered by me. Again IIRC
it was related to writing in the root dir of a drive (different from some OF
pkg configure issues that Mike or Rik investigated). Maybe there are some
clues there.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49214>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]