You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using pxf:info to see if images that a document refers to are available. Local builds happen on MacOS, which is typically case insensitive, but remote builds happen on a case-sensitive filesystem.
If I refer to an image file, Alice.jpg, three times, as alice.jpg, Alice.jpg, and aLice.jpg, in the case-insensitive environment pxf:info tells me each time that the file is there, but doesn't tell me what the case of the file on the filesystem actually is:
It would be great if there were a way to get the actual spelling of the path to the file, even in a case-insensitive environment so I could compare that with the path to the file in the document and warn the user that this doc will not build on the build machine.
The text was updated successfully, but these errors were encountered:
I'm using pxf:info to see if images that a document refers to are available. Local builds happen on MacOS, which is typically case insensitive, but remote builds happen on a case-sensitive filesystem.
If I refer to an image file,
Alice.jpg
, three times, as alice.jpg, Alice.jpg, and aLice.jpg, in the case-insensitive environment pxf:info tells me each time that the file is there, but doesn't tell me what the case of the file on the filesystem actually is:It would be great if there were a way to get the actual spelling of the path to the file, even in a case-insensitive environment so I could compare that with the path to the file in the document and warn the user that this doc will not build on the build machine.
The text was updated successfully, but these errors were encountered: