Ok. Could you please open a bug report on that for the inspector?

Since as Nicolai pointed out there is this��"14250��Enable large file support on linux", there is probably no point in creating an extra one.

I built custom VM with��_FILE_OFFSET_BITS=64��and it seems to hold, so thank you.

No problem. Here you go:
GLMTabulator new with: [ :tabulator |��
tabulator column: #favorites; column: #files span: 5.
tabulator transmit to: #favorites; andShow: [ :a |��
a list��
title: 'Favorites';
display: { 'test' asFileReference . 'tmp' asFileReference };
format: #fullName ].
tabulator transmit from: #favorites; to: #files; andShow: [ :a |
a custom: (GLMPager new with: [ :pager |
�� pager show: [ :composite :file |
�� composite title: file basename.
�� file gtInspectorItemsIn: composite.
�� file gtInspectorContentsIn: composite ] ]) ] ];
�� openOn: FileSystem disk workingDirectory

This is really cool! I will have to study this tomorrow.

UITheme builder fileOpen: 'Import model from MSE file' extensions: #('mse').

I am aware of this one, but it has all the issues mentioned in the first (and following) posts, since it is basically same as FileBrowser. That is why I was looking for an alternative.

They would just need to be hooked in the right place instead of the funny text field.

Why? From what I understood the way to build what I want would be a combination of GLM* browsers you mentioned above and in such configuration I do not see why would I need to hook up the default browsers.

Thanks,

Peter

On Fri, Nov 7, 2014 at 12:04 AM, Nicolai Hess <nicolaihess@web.de> wrote:

2014-11-06 23:25 GMT+01:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,

On Thu, Nov 6, 2014 at 10:50 PM, Peter Uhn��k <i.uhnak@gmail.com> wrote:
>��It is indeed known that Pharo cannot open files larger than 4GB (even that after you setup the VM specifically).
It seems like Pharo bug

1. FileReference>>gtInspectorItemsIn: composite
...
column: 'Size' evaluated: [:each | each humanReadableSize] width: 100;
...

2. FileReference>>humanReadableSize
^ self size humanReadableSIByteSize

3. MessageNotUnderstood: False>>humanReadableSIByteSize
because "self size" returns false for files > 4GB so it fails and thus I cannot navigate to folders with such files (for example my home directory).

Ok. Could you please open a bug report on that for the inspector?

This is an issue for the linux vm :
"14250 Enable large file support on linux"

on windows, you can list directories with files > 2G

FileSystemStore returns false on #size, if the file can not be found. Thats the reason why the inspector shows the "MessageNotUnderstood: False>>humanReadableSIByteSize" error.
And the files can not be found, because the unix VM uses lstat on the directory entries to retrieve the file attributes. And lstat does not work for files with sizes larger than 32Bit.