Skip to content

Test: provide a function to report working directory and library paths #7734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

SlySven
Copy link
Member

@SlySven SlySven commented Feb 21, 2025

Brief overview of PR changes/additions

Adds applicationPaths() function to Lua API which reports the Mudlet application's idea of its current working directory and the location(s) from which it would look to find binary libraries.

Motivation for adding to Mudlet

A user was reporting issues where Mudlet would load their first profile, including loading all the Lua binary libraries (such as the Lua File System) one and then fail to find it for a second profile, given that in their case (Windows 64 bit) release version this would be from the same directory as the Mudlet executable itself (the ./lfs.dll entry reported) in the error message in the main console. This function is intended to enable the "current" working directory to be monitored - so that if it gets changed it can be detected.

Other info (issues closed, discussion etc)

This is a test/draft PR - it is not intended to be merged into the main code-base. The user concerned with whom I have been helping with this is the Discord user kyrus78.

#### Brief overview of PR changes/additions
Adds `applicationPaths()` function to Lua API which reports the Mudlet
application's idea of its current working directory and the location(s)
from which it would look to find binary libraries.

#### Motivation for adding to Mudlet
A user was reporting issues where Mudlet would load their first profile,
including loading all the Lua binary libraries (such as the Lua File
System) one and then fail to find it for a second profile, given that in
their case (Windows 64 bit) release version this would be from the same
directory as the Mudlet executable itself (the `./lfs.dll` entry reported)
in the error message in the main console. This function is intended to
enable the "current" working directory to be monitored - so that if it gets
changed it can be detected.

#### Other info (issues closed, discussion etc)
**This is a test/draft PR - it is not intended to be merged into the main
code-base.** The user concerned with whom I have been helping with this is
the Discord user `kyrus78`.

Signed-off-by: Stephen Lyons <slysven@virginmedia.com>
Copy link
Contributor

Fails
🚫

PR title must start with fix, improve, add or infra for release notes purposes.

Generated by 🚫 dangerJS against 9ab1953

@add-deployment-links
Copy link

add-deployment-links bot commented Feb 21, 2025

Hey there! Thanks for helping Mudlet improve. 🌟

Test versions

You can directly test the changes here:

No need to install anything - just unzip and run.
Let us know if it works well, and if it doesn't, please give details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy