Re: D, GTK, Qt, wx,…
On Tuesday, 31 May 2016 at 08:57:51 UTC, MGW wrote: QtE5 - is my wrapper for Qt-5 https://www.youtube.com/watch?v=DuOl-4g117E https://github.com/MGWL/QtE5 How can we build QtE5 and/or the examples?
Re: 2.068.0 std.process.executeShell how to set the shell?
On Thursday, 3 September 2015 at 05:07:10 UTC, Jonathan M Davis wrote: key thing that you're missing is -c. - Jonathan M Davis Hi Jonathan, I would just like to say thank you for the time you took to help and clarify. Obrigado
Re: 2.068.0 std.process.executeShell how to set the shell?
On Wednesday, 2 September 2015 at 01:46:18 UTC, Jonathan M Davis wrote: On Wednesday, 2 September 2015 at 01:26:23 UTC, Jonathan M Davis wrote: [snip] https://issues.dlang.org/show_bug.cgi?id=15000 - Jonathan M Davis Thank you for your reply and for the bug report. Looking at your suggestions I do not fully understand/agree. executeShell has been one of the easiest ways for us to interact with the shell, all other functions require more work to implement. Being able to define the shell to be used is something that makes sense across all functions in std.process. Honestly being able to set a different variable name instead of SHELL would make more sense. It would not take the default shell from the user thus using /bin/sh and would allow us to change it if desired with a different value. The change would be minimal across code and documentation. But that's just my suggestion, I'm not a library developer. I understand that all variants may have their own issues, but taking away from the developer the power to make decisions also doesn't seem a good option. Anyway I would like to ask if you can help to understand why this simple example using execute fails? auto outputDiff = execute ( ["bash","echo"] ); writeln (outputDiff.output); Output: /bin/echo: /bin/echo: cannot execute binary file At the moment some of the uses I had are not working and I'm not able to implement any workaround. Obrigado
2.068.0 std.process.executeShell how to set the shell?
Hi, since the upgrade to the latest version the function
executeShell (also the other functions), is not working has it
used to be, older versions of the compiler did not require any
change or setting the SHELL.
How to change the SHELL, that is used by executeShell? userShell
will always return /bin/sh.
I've tested by setting the SHELL to /bin/bash using the
environment function. If I execute echo $SHELL inside the
executeShell it will show /bin/bash has expected.
My issue is that the command I'm executing inside executeShell is
throwing and error and showing that the execution is done by
/bin/sh.
My code:
executeShell("diff -u <(echo "~data1~") <(echo "~data2~")");
Output:
/bin/sh: 1: Syntax error: "(" unexpected
This is caused by a limitation from /bin/sh that cannot perform
process substitution.
Can this commit be the reason?
https://github.com/D-Programming-Language/phobos/commit/a524a3571b18e440c4dd751fcf4e2d00b834fb22
Re: Berlin D Meetup June 2015
On Tuesday, 16 June 2015 at 16:42:22 UTC, Ben Palmer wrote: on the 3rd floor. Mathias Lang will be doing a presentation titled Intro to Vibe.web.rest. Hi Would be nice if it was possible to have the presentation recorded or even live for the rest of us to watch. I which you all a nice time.
Re: Breaking changes in Visual C++ 2015
Would like to suggest strip to be added to the page. It makes wonders to the final executable. On Friday, 8 May 2015 at 15:47:11 UTC, Vladimir Panteleev wrote: On Thursday, 7 May 2015 at 22:27:57 UTC, Walter Bright wrote: But let's not forget the meat and potatoes on our plate while looking at our neighbor's salad dressing. I decided to line up our potatoes on a nice new wiki page: http://wiki.dlang.org/Development_tools
Re: SDC needs you
On Thursday, 16 April 2015 at 17:33:09 UTC, Andrei Alexandrescu wrote: On 4/16/15 8:47 AM, bachmeier wrote: Please let me know if https://github.com/D-Programming-Language/dlang.org/blob/master/CONTRIBUTING.md floats your boat. We should make it more visible, too. -- Andrei Can the document be improved with additional info: Were are the files to be changed? How to generate new documentation files after making a change? Thanks
Re: This week in D #13: =void tip, ddmd, if(arr) warn, dconf registration
Can I suggest to have a summary/list of the last added projects to code.dlang.org. On Monday, 13 April 2015 at 03:37:17 UTC, Adam D. Ruppe wrote: http://arsdnet.net/this-week-in-d/apr-12.html http://www.reddit.com/r/d_language/comments/32ek17/this_week_in_d_13_void_tip_ddmd_ifarr_warn_dconf/ https://twitter.com/adamdruppe/status/587459000729473024
Re: DDT 0.11.0 released
Just go to project Properties, Builders, de-select DUB Build and add any another build option or script you need. On Tuesday, 17 March 2015 at 23:54:06 UTC, Manu wrote: I just checked out DDT, and I noticed it seems to use DUB... _
Re: Fwd: Interfacing with C++
On Monday, 3 November 2014 at 20:32:34 UTC, Abdulhaq wrote: You might find my project Smidgen (https://github.com/alynch4047/smidgen) useful, It's not finished but you might consider extending it rather than starting elsewhere. woe... The first time I see this project mentioned. You may consider publishing this in the announcement forum, it will give it more visibility, it looks very promising. And now to play with it... Thank you
Re: Recommendation on option parsing
Too late I see, but maybe next time it will provide you a way to search available projects faster. On DUB http://code.dlang.org/ there is one project that looks like address the issues you had with std.getopt, post-rock. Have not used it so I cannot give any further recommendations. Maybe you will find there others. On Friday, 9 May 2014 at 23:09:34 UTC, Chris Piker wrote: Phobos' std.getopt is a bit spare for my taste, as there is no builtin general help facility with word-wrapping. Does anyone have a recommendation on which of the existing command line option parsing libraries floating around in the wild to use? If it doesn't compile against the current version of phobos I'm willing to put in a little work, but since I'm very new to D I probably would not make the best design decisions. -- Chris
