| 01:25.35 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 01:28.28 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 01:56.13 | Stragus | I have a very stupid question for OSX users... When you double-click (or single or triple click, whatever it takes) an executable that only deals with stdin/stdout/stderr, what happens? Is the output lost or does it automatically create a terminal? |
| 01:56.48 | Stragus | You can probably tell I never used OSX :), besides a ssh remote connection that is. Is there some kind of right-click and "Run in terminal" or something? |
| 04:28.47 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 04:32.07 | *** join/#brlcad bhattigurjot (~scott@202.164.53.117) |
| 04:39.12 | Notify | 03BRL-CAD Wiki:Sameer bhosle * 0 /wiki/User:Sameer_bhosle: |
| 07:27.32 | *** join/#brlcad simran (~simran@115.242.97.133) |
| 07:55.21 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
| 08:53.14 | *** join/#brlcad ries (~ries@D979EA84.cm-3-2d.dynamic.ziggo.nl) |
| 09:21.38 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
| 11:30.29 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 11:35.26 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
| 12:06.32 | ``Erik | Stragus: double click (or right click and "open") on a 'non-bundle' executable will launch a new Terminal.app window, and their icon will be a terminal window |
| 13:09.05 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
| 14:10.24 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 14:22.05 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
| 14:38.09 | *** join/#brlcad kintel (~kintel@unaffiliated/kintel) |
| 14:52.43 | Notify | 03BRL-CAD:starseeker * 63121 brlcad/trunk/src/libbrep/brep_except.h: Add common.h |
| 15:44.57 | brlcad | Stragus: yeah, since 10.4 or so, double-clicking a non-bundle application launches a terminal and runs that command ... "regular" mac applications are actually just special directories that have more detailed information about the application and how to launch it |
| 15:49.32 | brlcad | so if you double-click gdb, you'll be at the gdb prompt. if it's a command that doesn't wait for / read input, it's going to run the command in a tty and exit. shell scripts are not run automatically and usually best placed in an app bundle if you want them to have double-click behavior. |
| 15:55.45 | *** join/#brlcad gaganjyot (~gaganjyot@124.253.225.188) |
| 15:56.20 | *** join/#brlcad Darshpreet (~Darsh@202.164.53.117) |
| 16:17.45 | *** join/#brlcad FreezingCold (~Freezing@174.116.104.142) |
| 16:24.27 | Stragus | Cool. Thanks ``Erik and brlcad |
| 16:30.52 | *** join/#brlcad teepee- (bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
| 16:47.07 | *** join/#brlcad Darshpreet (~Darsh@202.164.53.117) |
| 17:08.52 | *** join/#brlcad Darshpreet (~Darsh@202.164.53.117) |
| 17:31.38 | *** join/#brlcad infobot (ibot@rikers.org) |
| 17:31.38 | *** topic/#brlcad is BRL-CAD || http://brlcad.org || logs: http://ibot.rikers.org/%23brlcad/ || GCI winners: Jacob Burroughs and Peter Amidon! || GSoC 2014 selections are announced! Thank you to all we got to work with. Remember that SOCIS is coming up right around the corner and you don't need a summer of code to get involved with open source. |
| 18:04.38 | *** join/#brlcad Darshpreet (~Darsh@202.164.53.117) |
| 18:24.07 | *** join/#brlcad user_name (~Divyanshi@223.225.233.80) |
| 19:35.57 | *** join/#brlcad clock (~clock@77-58-143-135.dclient.hispeed.ch) |
| 19:44.22 | Notify | 03BRL-CAD:n_reed * 63122 brlcad/branches/brep-debug/src/libbrep/boolean.cpp: Rewrite the get_subcurves_inside_faces() routine. The prior algorithm had multiple issues, the most significant of which was that we were merging two sets of curve intervals, one in terms of the domain of the 2d intersection curve in the first face, and the second in terms of the 2d curve domain in the second face. The separate 2d curve |
| 19:44.24 | Notify | parameterizations are sometimes the same, but generally are not, which means that we have to convert the intervals to 3d for merging, and then convert the final 3d subcurve intervals back to the equivelent intervals in each of the two distinct 2d curve domains (much harder). |
| 20:07.08 | DarkCalf | waves to brlcad |