This channel is intended for people just starting with the Raku Programming Language (raku.org). Logs are available at irclogs.raku.org/raku-beginner/live.html
Set by lizmat on 8 June 2022.
00:10 stanrifkin left
rcmlz Can you append a ‚&‘ at the command? 05:09
like so raku # (For example) my Str constant $DIFF-TOOL = 'C:\Program Files\WinMerge\WinMergeU.exe &'; run $DIFF-TOOL, $full-file-path, $network-path; 05:11
05:42 sjn left 05:43 sjn joined
Welemtam I did the equivalent on windows which is run 'cmd', '/c', 'start', '/B', 'WinMergeU.exe', 'my', 'arguments'; it works like this, it's specific to windows, but for now it'll be OK 🙂 06:40
For curious people ; the correct way on Windows is to pass an empty string to cmd /c start as a placeholder ; otherwise if you give a quoted program name (which is necessary if it has spaces), it doesn't interpret it as the program name, but as a window title. (which gives a completely absurd result since your 1st arg becomes the program name, ...) (but this is because the windows console is dreadful) so 09:26
this is works for me : run 'cmd', '/c', 'start', '""', '/b', $DIFF-TOOL, $full-file-path, $network-path; Sadly qx / qqx has the same blocking behavior that I saw with "run winmerge.exe" I believe my question is item 5. in the following topic github.com/Raku/problem-solving/is...-487715316 > I want to run a exe file via cmd.exe, but don't want any cmd.exe side effect > Why would one
want to do such a thing and not just call the exe file directly? > Number 4. and 5. won't happen in any normal usage scenarios. As my scenario is "run some application and go away" I'm still curious to know if there's a simpler way (just like a fork-exec in C or subprocess.Popen in python)
coranila @Welemtam may I suggest trying to capture that insight in a module? 10:38
I'm pretty sure others will appreciate having a mature solution to fall back on, plus it's a great opportunity to dig a bit deeper into how Raku handles distribution across platforms - as you note yourself, this is explicitly OS dependent. 10:39
I'm failure sure you should have access to most, if not all, you need via dynamic variables during runtime.
Should it turn out that you don't that might very well be a compiler or even roast bug. 10:40
...although maybe a note in the docs is enough 🤔 I have been away for a while and used to be deep in the backend... 😇 10:41
Welemtam sure, I will 10:47
coranila From the looks of it everything we have in the ecosystem does indeed insist on managing stuff longterm; there's no canonical way to say "just fire and forget"" as far as I can tell. 10:48
Maybe this means we need a wild-life extension of the adoption center... 🤔 11:11
lizmat coranila are you referring to the Raku Ecosystem Archive (REA) ? 11:16
coranila lizmat: I found github.com/Raku/ecosystem/blob/mas...OPT-ME.md, which to me seems to imply strict ownership; I'm asking about a mechanism for maintanance fixes that doesn't require ownership; my last ownership did escalate to the JVM backend almost 10 years ago, hi :) 11:18
(that's to say I am Pepe/Nele Schwarz) 11:19
lizmat aha... ok, I guess I will need to look at that list, as its outdated
hi Pepe!
coranila nele please!
lizmat ah, Nele, sorry
coranila cause ykno, ~gender~
:)
lizmat Hi Nele, nice to see you (again)! 11:20
coranila thank you! I am trying to get back into things but yeah, it's got to be loose hence the idea of some interface for an evolutionary drive, so to speak
as in, a means to allow "this is what community thinks should maybe change", a reflective testing stage maybe a la debian? 11:21
lizmat many of my modules fall in that category...
some may be adopted into Raku at some point, most will not: but that's fine :)
coranila also glad to be around again and see you and others and a community; very cool!! 11:22
lizmat yeah, although pretty small compared to other communities, it's pretty cool :-) 11:24
13:37 stanrifkin joined 23:54 kjp left 23:55 kjp joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!