Replies: 3 comments 2 replies
-
Because the XCL exec uses the Common Lisp readtable, which converts to uppercase by default, There's no |
Beta Was this translation helpful? Give feedback.
1 reply
-
But maybe this is something that should be changed. Given the case issue, why is this particular function in camel case rather than changed rather than in eithr the dot or hyphen conventions that are more generally used: SHELL.COMMAND or SHELL-COMMAND?
… On Dec 6, 2024, at 5:23 AM, Paolo Amoroso ***@***.***> wrote:
That works thanks.
—
Reply to this email directly, view it on GitHub <#1894 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJIJSUETYPNGDQI5O7D2EGQNLAVCNFSM6AAAAABTC2PEE2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBYGUYDMMY>.
You are receiving this because you are subscribed to this thread.
|
Beta Was this translation helpful? Give feedback.
1 reply
-
what is the history of ShellCommand? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is the UNIXUTILS function
ShellCommand
supposed to be called from Common Lisp? When I callIL:ShellCommand
from a XCL Exec I get the error:but
ShellCommand
works as expected from an Interlisp Exec:Beta Was this translation helpful? Give feedback.
All reactions