hello, greetings to all and thanks for having this excellent software. I have a problem opening cmds shell, it seems to be hard-coded, the Firefox browser, although I use firefox, I use the developer version "firefox-developer- edition" I think it is better to use the default browser using xdg. example xdg-open ShellCmds.html -- - | Walter Casanova | - - | Gnu / Linux - SysAdmin | -
В сообщении от Wednesday 27 January 2021 15:52:09 Walter Casanova via Cin написал(а):
hello, greetings to all and thanks for having this excellent software. I have a problem opening cmds shell, it seems to be hard-coded, the Firefox browser, although I use firefox, I use the developer version "firefox-developer- edition" I think it is better to use the default browser using xdg.
You can edit commands used to open those files or doing other scripty things in ~/.bcast5/Cinelerra_rc : SHBTNS_TOTAL 4 SHBTN0_NAME Online Help SHBTN0_COMMANDS kpdf https://cinelerra-gg.org/download/CinelerraGG_Manual.pdf SHBTN0_WARN 0 SHBTN1_NAME Orignal Manual SHBTN1_COMMANDS konqueror file://$CIN_DAT/doc/cinelerra.html SHBTN1_WARN 0 SHBTN2_NAME Shell Commands manual SHBTN2_COMMANDS $CIN_BROWSER file://$CIN_DAT/doc/ShellCmds.html SHBTN2_WARN 0 SHBTN2_RUN_SCRIPT 0 SHBTN3_NAME Сочетания клавиш SHBTN3_COMMANDS $CIN_BROWSER file://$CIN_DAT/doc/shortcuts.html SHBTN3_WARN 0 SHBTN3_RUN_SCRIPT 0 $CIN_BROWSER is by default firefox, but you can chnage this during compilation .. or may be at runtime via env. variables, too? but hand-editing those lines hopefully is faster :}
example xdg-open ShellCmds.html
El miércoles, 27 de enero de 2021 10:29:10 -03 Andrew Randrianasulu via Cin escribió:
В сообщении от Wednesday 27 January 2021 15:52:09 Walter Casanova via Cin написал(а):
hello, greetings to all and thanks for having this excellent software. I have a problem opening cmds shell, it seems to be hard-coded, the Firefox browser, although I use firefox, I use the developer version "firefox-developer- edition" I think it is better to use the default browser using xdg. You can edit commands used to open those files or doing other scripty things in ~/.bcast5/Cinelerra_rc :
SHBTNS_TOTAL 4 SHBTN0_NAME Online Help SHBTN0_COMMANDS kpdf https://cinelerra-gg.org/download/CinelerraGG_Manual.pdf SHBTN0_WARN 0 SHBTN1_NAME Orignal Manual SHBTN1_COMMANDS konqueror file://$CIN_DAT/doc/cinelerra.html SHBTN1_WARN 0 SHBTN2_NAME Shell Commands manual SHBTN2_COMMANDS $CIN_BROWSER file://$CIN_DAT/doc/ShellCmds.html SHBTN2_WARN 0 SHBTN2_RUN_SCRIPT 0 SHBTN3_NAME Сочетания клавиш SHBTN3_COMMANDS $CIN_BROWSER file://$CIN_DAT/doc/shortcuts.html SHBTN3_WARN 0 SHBTN3_RUN_SCRIPT 0
$CIN_BROWSER is by default firefox, but you can chnage this during compilation .. or may be at runtime via env. variables, too?
but hand-editing those lines hopefully is faster :}
example xdg-open ShellCmds.html
perfect, I did not know this xD. it's already solved thanks -- - | Walter Casanova | - - | Gnu / Linux - SysAdmin | -
*Walter*, good to see you using Shell Commands, but please remember to back up $HOME/.bcast5/Cinelerra_rc because that is where there usage is saved. $CIN_BROWSER is by default firefox, but you can chnage this during
compilation .. or may be at runtime via env. variables, too?
As Andrew has already stated, you can set your CIN_BROWSER value before bringing up CinelerraGG as noted in the manual. You can put that in your .profile file. This is the easiest way. *16.7 Environment Variables for Customization*
Environment variables are global variables in the shell which all applications can read. They are set with a command like set VARIABLE=value or export VARIABLE=value. Environment variables can be viewed with a command like env. The values set can be removed with unset VARIABLE. ... *CIN_BROWSER* name of browser to use by Shell Cmds options
El miércoles, 27 de enero de 2021 12:28:43 -03 Phyllis Smith via Cin escribió: *Walter*, good to see you using Shell Commands, but please remember to back up $HOME/.bcast5/Cinelerra_rc because that is where there usage is saved. $CIN_BROWSER is by default firefox, but you can chnage this during compilation .. or may be at runtime via env. variables, too? As Andrew has already stated, you can set your CIN_BROWSER value before bringing up CinelerraGG as noted in the manual. You can put that in your .profile file. This is the easiest way. *16.7 Environment Variables for Customization* Environment variables are global variables in the shell which all applications can read. They are set with a command like set VARIABLE=value or export VARIABLE=value. Environment variables can be viewed with a command like env. The values set can be removed with unset VARIABLE. ...*CIN_BROWSER* name of browser to use by Shell Cmds options yes, add the variable in .zshenv, because I use zsh, but beyond that it seems that cinelerra doesn't read the environment variables. because firefox is still [1] [2] if i put firefox-developer-edition directly in ~/.bcast5/Cinelerra_rc if it works, but it doesn't seem to read environment variables 🤨 At the moment it is hard coded, thanks Phyllis -- - | Walter Casanova | - - | Gnu / Linux - SysAdmin | - -------- [1] imagen [2] imagen1
Walter, thanks so much for the feedback as sometimes things unexpectedly are impacted by modifications and break. But I don't think that is the case here. The variable is not $CIN_BROWSER, but just CIN_BROWSER without the $ in front. Although I have no other browsers to test, I did the following and got the following result: [root@keystone bin]# CIN_BROWSER=firefox-developer-edition ./cin
Cinelerra Infinity - built: Jan 26 2021 09:26:19 ... /bin/bash: firefox-developer-edition: command not found
In addition. I used on the command line: CIN_BROWSER=vi ./cin and vi did come up in the terminal window. And just to be sure, I tried it as an ordinary user instead of root with the same results.
yes, add the variable in .zshenv, because I use zsh, but beyond that it seems that cinelerra doesn't read the environment variables. because firefox is still
El miércoles, 27 de enero de 2021 14:45:22 -03 Phyllis Smith via Cin escribió:
Walter, thanks so much for the feedback as sometimes things unexpectedly are impacted by modifications and break. But I don't think that is the case here. The variable is not $CIN_BROWSER, but just CIN_BROWSER without the $ in front. Although I have no other browsers to test, I did the following and got the following result:
[root@keystone bin]# CIN_BROWSER=firefox-developer-edition ./cin
This is very valid, but I prefer that it look for the variable directly, so I don't have to edit the shortcuts (.desktop).
Cinelerra Infinity - built: Jan 26 2021 09:26:19 ... /bin/bash: firefox-developer-edition: command not found
In addition. I used on the command line: CIN_BROWSER=vi ./cin and vi did come up in the terminal window. And just to be sure, I tried it as an ordinary user instead of root with the same results.
yes, add the variable in .zshenv, because I use zsh, but beyond that it seems that cinelerra doesn't read the environment variables. because firefox is still
I understand, the $ is to tell the interpreter that it is a variable if it is not going to print the written text literally [1] I noticed that I had a problem in a function in zshenv, which doesn't seem to export well. but it is already corrected. only added to bashrc, zshrc, profile, etc. export CIN_BROWSER=firefox-developer-edition Thanks greetings -- - | Walter Casanova | - - | Gnu / Linux - SysAdmin | - -------- [1] imagen
participants (3)
-
Andrew Randrianasulu -
Phyllis Smith -
Walter Casanova