external text editor for scripting
#1
Posted 19 March 2009 - 02:08 AM
could someone tell me how is it possible to use an external text editor for scripting?
thanks
bmt
#2
Posted 19 March 2009 - 04:37 AM
beeemtee, on Mar 19 2009, 01:08 PM, said:
could someone tell me how is it possible to use an external text editor for scripting?
thanks
bmt
http://www.sidefx.co...essions/_custom
Houdini uses the external editor defined by the $EDITOR environment variable. If $EDITOR is not set, Houdini uses a default editor for the platform (e.g. vi or notepad.exe).
#3
Posted 19 March 2009 - 05:31 AM
but now:
1. it only opens gvim if i click on the "external editor" button in houdini's default editor not for simple alt-e, as i expected
2. even then it doesn't load the script in hand and not even refresh it, not when i save, nor when i click on the reload button
is it supposed to be like this? do i miss something? what is the common workfolw?
thanks again!
bmt
#4
Posted 19 March 2009 - 05:41 AM
so i go with vim it's not such a big difference, but if someone know how to work around this i would be really grateful.
thanks anyway!
bmt
#5
Posted 19 March 2009 - 06:44 AM
#6
Posted 19 March 2009 - 07:20 AM
kubabuk, on Mar 19 2009, 05:44 PM, said:
#7
Posted 30 March 2010 - 09:55 AM
kubabuk, on 19 March 2009 - 06:44 AM, said:
Hi
I cannot find the hconfig file. Can someone tell me where it is?
thanks
#8
Posted 30 March 2010 - 10:10 AM
oldiesgoodies, on 30 March 2010 - 09:55 AM, said:
I cannot find the hconfig file. Can someone tell me where it is?
thanks
hconfig is an executable, and it should be found in the same place as all your other Houdini executables for your platform (e.g: in Linux, this would be <houdini_install_path>/bin).
With regards to gvim and setting it as your default external editor, this can be done, as stated above, by setting either the EDITOR or VISUAL envars. However, gvim (unlike vim) will normally fork a new process upon startup (i.e: it will run in the background). But for Houdini to be able to stream to/from it, it has to run in the foreground, so you have to disable forking. In cshell, for example, you could set it like this:
setenv EDITOR "gvim --nofork"
HTH.
#9
Posted 30 March 2010 - 11:03 AM
Mario Marengo, on 30 March 2010 - 10:10 AM, said:
With regards to gvim and setting it as your default external editor, this can be done, as stated above, by setting either the EDITOR or VISUAL envars. However, gvim (unlike vim) will normally fork a new process upon startup (i.e: it will run in the background). But for Houdini to be able to stream to/from it, it has to run in the foreground, so you have to disable forking. In cshell, for example, you could set it like this:
setenv EDITOR "gvim --nofork"
HTH.
Hi
Thanks for the quick follow up. This should help me out
#10
Posted 23 April 2010 - 01:09 PM
say
Applications/TextWrangler
I get an error with the above string as $EDITOR.
thanks
Tom
oldiesgoodies, on 30 March 2010 - 11:03 AM, said:
Thanks for the quick follow up. This should help me out
#11
Posted 26 April 2010 - 03:41 AM
In the Shell area, turn on the Run Command option and put in the following string:
cd /Library/Frameworks/Houdini.framework/Versions/10.0.595/Resources;source houdini_setup; cd ~
where the 10.0.595 would be replaced with the version you have installed.
Launch this shell, then type in the hconfig -ap to see the env that Houdini creates on launch.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users











