Path bug?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Path bug?

gciriani
The function path shows C:\Octave\OCTAVE~1.1\ etc. However the folder where
the package is installed in my PC is C:\Octave\Octave-4.2.1. Shall I report
this as a bug?
P.S.
I initially installed the older version 4.0.0 of Octave at the beginning of
this month in C:\Octave\Octave-4.0.0. However, after running it a couple of
times I discovered it was not the latest version available. I then deleted
the whole directory and downloaded again the most recent installation zip
file.



-----
Giovanni Ciriani - Windows 10, Octave 4.2.1, configured for x86_64-w64-mingw32
--
Sent from: http://octave.1599824.n4.nabble.com/Octave-General-f1599825.html

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Giovanni Ciriani - Windows 10, Octave 4.2.1, configured for x86_64-w64-mingw32
Reply | Threaded
Open this post in threaded view
|

Re: Path bug?

NJank
On Aug 31, 2017 8:21 AM, "gciriani" <[hidden email]> wrote:
The function path shows C:\Octave\OCTAVE~1.1\ etc. However the folder where
the package is installed in my PC is C:\Octave\Octave-4.2.1. Shall I report
this as a bug?

Not as bug. Both of those paths are correct. The former is the short name version . It is how windows stores long filenames to maintain compatibility. I haven't been able to figure out the reason why some parts of octave use the short form and others use the long form.


_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: Path bug?

gciriani
This post was updated on .
NJank wrote
> The former is the short name version . It is how windows stores long
> filenames to maintain compatibility.

The former is not how Windows stores the filename but the way Octave
displays it when I type the function path. I would understand an
abbreviation, but if you notice there is a difference after the
abbreviation; the former shows 1.1, the latter shows 2.1, which is what I
can't figure out.

It may be explained by the way the tilde expansion "~" works; see
(--edit--) https://octave.sourceforge.io/octave/function/tilde_expand.html (--edit--)
However, even after reading the manual explanation, it still escapes me.




-----
Giovanni Ciriani - Windows 10, Octave 4.2.1, configured for x86_64-w64-mingw32
--
Sent from: http://octave.1599824.n4.nabble.com/Octave-General-f1599825.html

_______________________________________________
Help-octave mailing list
Help-octave@gnu.org
https://lists.gnu.org/mailman/listinfo/help-octave
Giovanni Ciriani - Windows 10, Octave 4.2.1, configured for x86_64-w64-mingw32
Reply | Threaded
Open this post in threaded view
|

Re: Path bug?

NJank
On Thu, Aug 31, 2017 at 9:17 AM, gciriani <[hidden email]> wrote:
NJank wrote
> The former is the short name version . It is how windows stores long
> filenames to maintain compatibility.

The former is not how Windows stores the filename but the way Octave
displays it when I type the function path. I would understand an
abbreviation, but if you notice there is a difference after the
abbreviation; the former shows 1.1, the later shows 2.1, which is what I
can't figure out.

It may be explained by the way the tilde expansion "~" works; see
https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html
However, even after reading the manual explanation, it still escapes me.


It has nothing to do with tilde expansion.  it is the method windows chose to use to bridge the short-to-long filename transition back in the Windows 95. Maybe this is a better wiki explanation:
https://en.wikipedia.org/wiki/Long_filename

Both versions:

C:\Octave\OCTAVE~1.1\
C:\Octave\Octave-4.2.1\

point to the same location and are equally valid as far as windows is concerned.

open a command prompt, go to c:\octave, and type:

dir /x

the /x will display the short names stored along with the long names for any files and directories.

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Reply | Threaded
Open this post in threaded view
|

Re: Path bug?

gciriani
Got it. Thanks. You meant the DOS prompt. It was a fluke that the Windows
abbreviation coincided with the Octave version number.



-----
Giovanni Ciriani - Windows 10, Octave 4.2.1, configured for x86_64-w64-mingw32
--
Sent from: http://octave.1599824.n4.nabble.com/Octave-General-f1599825.html

_______________________________________________
Help-octave mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-octave
Giovanni Ciriani - Windows 10, Octave 4.2.1, configured for x86_64-w64-mingw32