Hi,
I am trying to run glpsol (glpk) in geany. I have problem using run_cmd. It seem that the build_settings is very limit.
Geany [build_settings] # %f will be replaced by the complete filename # %e will be replaced by the filename without extension # (use only one of it at one time) compiler = run_cmd="./%e"
It seem that the run_cmd is limited to accommodate various file extension and options for various languages and script. If not, how you do implement this in geany.
This is TextAdept implementation in running glpsol. TA runs the command perfectly.
mod = '/usr/local/bin/glpsol --math %(filename)', mps = '/usr/local/bin/glpsol --mps %(filename)', fms = '/usr/local/bin/glpsol --freemps %(filename)', lp = '/usr/local/bin/glpsol --lp %(filename)', glp = '/usr/local/bin/glpsol --dlp %(filename)',
In Geany, how do you do this.
run_cmd = glpsol --math ?????????
Would the run_cmd intelligence enough to know the filenames extension?
eg.
run_cmd = '/usr/local/bin/glpsol --math %(filename)', run_cmd = '/usr/local/bin/glpsol --mps %(filename)', run_cmd = '/usr/local/bin/glpsol --freemps %(filename)', run_cmd = '/usr/local/bin/glpsol --lp %(filename)', run_cmd = '/usr/local/bin/glpsol --dlp %(filename)',
For information on the documentation of glpk
Google: glpk http://www.google.com.au/#hl=en&source=hp&q=glpk&btnG=Google+Sea...
GLPK http://www.gnu.org/software/glpk/
GUSEK http://gusek.sourceforge.net/gusek.html
Noli
More information on GLPK and Editors. I want to include Geany as one of the editor for GLPK
http://spokutta.wordpress.com/the-gnu-linear-programming-kit-glpk/
Noli
On 2/23/10, Noli Sicad nsicad@gmail.com wrote:
Hi,
I am trying to run glpsol (glpk) in geany. I have problem using run_cmd. It seem that the build_settings is very limit.
Geany [build_settings] # %f will be replaced by the complete filename # %e will be replaced by the filename without extension # (use only one of it at one time) compiler = run_cmd="./%e"
It seem that the run_cmd is limited to accommodate various file extension and options for various languages and script. If not, how you do implement this in geany.
This is TextAdept implementation in running glpsol. TA runs the command perfectly.
mod = '/usr/local/bin/glpsol --math %(filename)', mps = '/usr/local/bin/glpsol --mps %(filename)', fms = '/usr/local/bin/glpsol --freemps %(filename)', lp = '/usr/local/bin/glpsol --lp %(filename)', glp = '/usr/local/bin/glpsol --dlp %(filename)',
In Geany, how do you do this.
run_cmd = glpsol --math ?????????
Would the run_cmd intelligence enough to know the filenames extension?
eg.
run_cmd = '/usr/local/bin/glpsol --math %(filename)', run_cmd = '/usr/local/bin/glpsol --mps %(filename)', run_cmd = '/usr/local/bin/glpsol --freemps %(filename)', run_cmd = '/usr/local/bin/glpsol --lp %(filename)', run_cmd = '/usr/local/bin/glpsol --dlp %(filename)',
For information on the documentation of glpk
Google: glpk http://www.google.com.au/#hl=en&source=hp&q=glpk&btnG=Google+Sea...
GLPK http://www.gnu.org/software/glpk/
GUSEK http://gusek.sourceforge.net/gusek.html
Noli
Hi Noli,
I'm not sure that my point was clear enough.
Geany has a unified model of a file type. When a file is loaded, its type is determined (or it is set by Document->Set Filetype ->...). This type controls the text highlighting and the filetype dependent build menu commands.
Scite (and apparently TextAdept) does not have a unified model, the commands have to be specified separately by extension as your post showed. I am not saying one model is better than another, they are just different. In this case Scite can be more flexible, but the Geany model has other advantages and AFAIK this is the first time this problem has occurred.
I am about to start more changes to the Geany build system that will further improve its flexibility. But providing separate commands for different extensions within a single filetype is not in the plan because as I said, its never been needed before. Without that capability Glpk can still be supported in two ways:
1. each of the extensions is a separate filetype, but using the same highlighting (BTW what lexer do you use with Scite because AFAIK it doesn't support GLPK) this is supported now in SVN with custom filetypes
2. a plugin is added which modifies the command for GLPK files depending on the extension, this requires the re-make to be available (and the plugin to be written) but might be considered to be cleaner
To use method 1 all you need to do is to copy your current filetypes file so you have one per extension, set the compile (or whatever) command in the [build-menu] section for each, and edit filetype_extensions.conf to reference them.
Cheers Lex
Hi Lex,
Thanks you for taking the time in answering my question.
I'm not sure that my point was clear enough.
I think your point is clear enough.
Geany has a unified model of a file type. When a file is loaded, its type is determined (or it is set by Document->Set Filetype ->...). This type controls the text highlighting and the filetype dependent build menu commands.
Probably if GLPK is created in the 50's the address the needs of the time, then there is no problem, it would a fit into the mold classic c/c++ compiler.
compiler = glpsol --mps mylinearprogramingmodel.mps run_cmd = glpsol -mps mylinearprogrammingmodle.mps.
BTW, the MPS is created by IBM in the 50. MPS is mathmatical programming system
On line doc http://projects.gnome.org/gnumeric/doc/file-format-mps.shtml
Then followed by the LP format LP format doc http://www.gurobi.com/html/doc/refman/node386.html
Scite (and apparently TextAdept) does not have a unified model, the commands have to be specified separately by extension as your post showed. I am not saying one model is better than another, they are just different. In this case Scite can be more flexible, but the Geany model has other advantages and AFAIK this is the first time this problem has occurred.
As I mentioned, SciTE is the father of all scintilla base editors. Since the developer of TextAdept is author of SciTE cloned (SciTe-tools - scintilla lua dynamic lexer). He knows exactly why SciTE has 56 languages and scripts and does not fit into "unified model", the classic c compier, I suppose.
I am about to start more changes to the Geany build system that will further improve its flexibility. But providing separate commands for different extensions within a single filetype is not in the plan because as I said, its never been needed before. Without that capability Glpk can still be supported in two ways:
- each of the extensions is a separate filetype, but using the same
highlighting (BTW what lexer do you use with Scite because AFAIK it doesn't support GLPK) this is supported now in SVN with custom filetypes
The problem is we will have 5 (mps, lp(cplex), fps(freemps), mod(mathprog), glp(glpk)) separates filetypes. What name should we use ? Probably, glpk_mps, glpk_lp, glpk_fmps, glpk_mathprog, and glpk_glp, it might work but messy. Aside from this, glpsol has ability to translate/convert one format to another. Most of the solvers use mps format. GLPK is one of the best in the area and this is the reason why I am promoting GLPK to the Geany users.
In GUSEK IDE, we use, c, sql and asm lexers to create the glmp.properties.
In TextAdept, I adopted c lexer and modified it to create glpk.lua lexer. TextAdept use the lua dynamic lexer loading.
- a plugin is added which modifies the command for GLPK files depending on
the extension, this requires the re-make to be available (and the plugin to be written) but might be considered to be cleaner
I think this is the best option.
To use method 1 all you need to do is to copy your current filetypes file so you have one per extension, set the compile (or whatever) command in the [build-menu] section for each, and edit filetype_extensions.conf to reference them.
I think this is the hack (method 1) and probably use just use - glpk1, glpk2, glpk3, glpk4, glpk5
I hope Geany developers that address this issue.
Right now, windows users can use GUSEK IDE and TextAdept, for Mac OS X users TextAdept and for linux users TextAdept and classic editors.
Lex, thanks again.
Regards, Noli
On 23 February 2010 18:18, Noli Sicad nsicad@gmail.com wrote:
Hi Lex,
Thanks you for taking the time in answering my question.
I'm not sure that my point was clear enough.
I think your point is clear enough.
Geany has a unified model of a file type. When a file is loaded, its
type
is determined (or it is set by Document->Set Filetype ->...). This type controls the text highlighting and the filetype dependent build menu commands.
Probably if GLPK is created in the 50's the address the needs of the time, then there is no problem, it would a fit into the mold classic c/c++ compiler.
compiler = glpsol --mps mylinearprogramingmodel.mps run_cmd = glpsol -mps mylinearprogrammingmodle.mps.
BTW, the MPS is created by IBM in the 50. MPS is mathmatical programming system
On line doc http://projects.gnome.org/gnumeric/doc/file-format-mps.shtml
Then followed by the LP format LP format doc http://www.gurobi.com/html/doc/refman/node386.html
Scite (and apparently TextAdept) does not have a unified model, the
commands
have to be specified separately by extension as your post showed. I am
not
saying one model is better than another, they are just different. In
this
case Scite can be more flexible, but the Geany model has other advantages and AFAIK this is the first time this problem has occurred.
As I mentioned, SciTE is the father of all scintilla base editors. Since the developer of TextAdept is author of SciTE cloned (SciTe-tools - scintilla lua dynamic lexer). He knows exactly why SciTE has 56 languages and scripts and does not fit into "unified model", the classic c compier, I suppose.
Actually the C compiler is the one that is most likely to require different handling of .h and .c files if your compiler produces pre-compiled headers. So the "traditional" is not the best example but I know what you mean :-)
I am about to start more changes to the Geany build system that will
further
improve its flexibility. But providing separate commands for different extensions within a single filetype is not in the plan because as I said, its never been needed before. Without that capability Glpk can still be supported in two ways:
- each of the extensions is a separate filetype, but using the same
highlighting (BTW what lexer do you use with Scite because AFAIK it
doesn't
support GLPK) this is supported now in SVN with custom filetypes
The problem is we will have 5 (mps, lp(cplex), fps(freemps), mod(mathprog), glp(glpk)) separates filetypes. What name should we use ? Probably, glpk_mps, glpk_lp, glpk_fmps, glpk_mathprog, and glpk_glp, it might work but messy. Aside from this, glpsol has ability to translate/convert one format to another. Most of the solvers use mps format. GLPK is one of the best in the area and this is the reason why I am promoting GLPK to the Geany users.
I know its messy but it is available NOW. All other options require development and will therefore take time.
In GUSEK IDE, we use, c, sql and asm lexers to create the glmp.properties.
In TextAdept, I adopted c lexer and modified it to create glpk.lua lexer. TextAdept use the lua dynamic lexer loading.
Oh, Ok you have your own lexer, which you would need to add to Geany anyway.
- a plugin is added which modifies the command for GLPK files depending
on
the extension, this requires the re-make to be available (and the plugin
to
be written) but might be considered to be cleaner
I think this is the best option.
To use method 1 all you need to do is to copy your current filetypes file
so
you have one per extension, set the compile (or whatever) command in the [build-menu] section for each, and edit filetype_extensions.conf to reference them.
I think this is the hack (method 1) and probably use just use - glpk1, glpk2, glpk3, glpk4, glpk5
I hope Geany developers that address this issue.
Right now, windows users can use GUSEK IDE and TextAdept, for Mac OS X users TextAdept and for linux users TextAdept and classic editors.
As I said option 1 its a way of using Geany until alternative means is supported, or use these alternatives instead.
Cheers Lex
Lex, thanks again.
Regards, Noli _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Hi Lex,
I download the geany nightly build windows and I can see that there is new built setting. And there is new menu item - Set Build Commands and dialog box. It is not useful to what I need -).
The new geany is really nice looking in this build. It seems that it has gtk theme now.
Anyway, I tried to implement what you suggested.
In .filetype_extensions.conf glpk = *.mod
In filetypes.glpk run_cmd=c:\glpsol -m "%f"
It is not working.
I tried this
run_cmd=c:\glpsol -m "%f"
I tried this run_cmd=c:/glpsol -m "%f"
I tried this as well. run_cmd=c://glpsol -m "%f"
I got this error / result
'.' is not recognized as an internal or external command, operable program or batch file. Press any key to continue . . .
It is not working!
Vellam 22 Feb build
Regards, Noli
On 2/23/10, Lex Trotman elextr@gmail.com wrote:
On 23 February 2010 18:18, Noli Sicad nsicad@gmail.com wrote:
Hi Lex,
Thanks you for taking the time in answering my question.
I'm not sure that my point was clear enough.
I think your point is clear enough.
Geany has a unified model of a file type. When a file is loaded, its
type
is determined (or it is set by Document->Set Filetype ->...). This type controls the text highlighting and the filetype dependent build menu commands.
Probably if GLPK is created in the 50's the address the needs of the time, then there is no problem, it would a fit into the mold classic c/c++ compiler.
compiler = glpsol --mps mylinearprogramingmodel.mps run_cmd = glpsol -mps mylinearprogrammingmodle.mps.
BTW, the MPS is created by IBM in the 50. MPS is mathmatical programming system
On line doc http://projects.gnome.org/gnumeric/doc/file-format-mps.shtml
Then followed by the LP format LP format doc http://www.gurobi.com/html/doc/refman/node386.html
Scite (and apparently TextAdept) does not have a unified model, the
commands
have to be specified separately by extension as your post showed. I am
not
saying one model is better than another, they are just different. In
this
case Scite can be more flexible, but the Geany model has other advantages and AFAIK this is the first time this problem has occurred.
As I mentioned, SciTE is the father of all scintilla base editors. Since the developer of TextAdept is author of SciTE cloned (SciTe-tools - scintilla lua dynamic lexer). He knows exactly why SciTE has 56 languages and scripts and does not fit into "unified model", the classic c compier, I suppose.
Actually the C compiler is the one that is most likely to require different handling of .h and .c files if your compiler produces pre-compiled headers. So the "traditional" is not the best example but I know what you mean :-)
I am about to start more changes to the Geany build system that will
further
improve its flexibility. But providing separate commands for different extensions within a single filetype is not in the plan because as I said, its never been needed before. Without that capability Glpk can still be supported in two ways:
- each of the extensions is a separate filetype, but using the same
highlighting (BTW what lexer do you use with Scite because AFAIK it
doesn't
support GLPK) this is supported now in SVN with custom filetypes
The problem is we will have 5 (mps, lp(cplex), fps(freemps), mod(mathprog), glp(glpk)) separates filetypes. What name should we use ? Probably, glpk_mps, glpk_lp, glpk_fmps, glpk_mathprog, and glpk_glp, it might work but messy. Aside from this, glpsol has ability to translate/convert one format to another. Most of the solvers use mps format. GLPK is one of the best in the area and this is the reason why I am promoting GLPK to the Geany users.
I know its messy but it is available NOW. All other options require development and will therefore take time.
In GUSEK IDE, we use, c, sql and asm lexers to create the glmp.properties.
In TextAdept, I adopted c lexer and modified it to create glpk.lua lexer. TextAdept use the lua dynamic lexer loading.
Oh, Ok you have your own lexer, which you would need to add to Geany anyway.
- a plugin is added which modifies the command for GLPK files depending
on
the extension, this requires the re-make to be available (and the plugin
to
be written) but might be considered to be cleaner
I think this is the best option.
To use method 1 all you need to do is to copy your current filetypes file
so
you have one per extension, set the compile (or whatever) command in the [build-menu] section for each, and edit filetype_extensions.conf to reference them.
I think this is the hack (method 1) and probably use just use - glpk1, glpk2, glpk3, glpk4, glpk5
I hope Geany developers that address this issue.
Right now, windows users can use GUSEK IDE and TextAdept, for Mac OS X users TextAdept and for linux users TextAdept and classic editors.
As I said option 1 its a way of using Geany until alternative means is supported, or use these alternatives instead.
Cheers Lex
Lex, thanks again.
Regards, Noli _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Lex,
I think "execute" is broken in this nightly build 22 February. Python programs are not running as well.
Noli
On 2/23/10, Noli Sicad nsicad@gmail.com wrote:
Hi Lex,
I download the geany nightly build windows and I can see that there is new built setting. And there is new menu item - Set Build Commands and dialog box. It is not useful to what I need -).
The new geany is really nice looking in this build. It seems that it has gtk theme now.
Anyway, I tried to implement what you suggested.
In .filetype_extensions.conf glpk = *.mod
In filetypes.glpk run_cmd=c:\glpsol -m "%f"
It is not working.
I tried this
run_cmd=c:\glpsol -m "%f"
I tried this run_cmd=c:/glpsol -m "%f"
I tried this as well. run_cmd=c://glpsol -m "%f"
I got this error / result
'.' is not recognized as an internal or external command, operable program or batch file. Press any key to continue . . .
It is not working!
Vellam 22 Feb build
Regards, Noli
On 2/23/10, Lex Trotman elextr@gmail.com wrote:
On 23 February 2010 18:18, Noli Sicad nsicad@gmail.com wrote:
Hi Lex,
Thanks you for taking the time in answering my question.
I'm not sure that my point was clear enough.
I think your point is clear enough.
Geany has a unified model of a file type. When a file is loaded, its
type
is determined (or it is set by Document->Set Filetype ->...). This type controls the text highlighting and the filetype dependent build menu commands.
Probably if GLPK is created in the 50's the address the needs of the time, then there is no problem, it would a fit into the mold classic c/c++ compiler.
compiler = glpsol --mps mylinearprogramingmodel.mps run_cmd = glpsol -mps mylinearprogrammingmodle.mps.
BTW, the MPS is created by IBM in the 50. MPS is mathmatical programming system
On line doc http://projects.gnome.org/gnumeric/doc/file-format-mps.shtml
Then followed by the LP format LP format doc http://www.gurobi.com/html/doc/refman/node386.html
Scite (and apparently TextAdept) does not have a unified model, the
commands
have to be specified separately by extension as your post showed. I am
not
saying one model is better than another, they are just different. In
this
case Scite can be more flexible, but the Geany model has other advantages and AFAIK this is the first time this problem has occurred.
As I mentioned, SciTE is the father of all scintilla base editors. Since the developer of TextAdept is author of SciTE cloned (SciTe-tools - scintilla lua dynamic lexer). He knows exactly why SciTE has 56 languages and scripts and does not fit into "unified model", the classic c compier, I suppose.
Actually the C compiler is the one that is most likely to require different handling of .h and .c files if your compiler produces pre-compiled headers. So the "traditional" is not the best example but I know what you mean :-)
I am about to start more changes to the Geany build system that will
further
improve its flexibility. But providing separate commands for different extensions within a single filetype is not in the plan because as I said, its never been needed before. Without that capability Glpk can still be supported in two ways:
- each of the extensions is a separate filetype, but using the same
highlighting (BTW what lexer do you use with Scite because AFAIK it
doesn't
support GLPK) this is supported now in SVN with custom filetypes
The problem is we will have 5 (mps, lp(cplex), fps(freemps), mod(mathprog), glp(glpk)) separates filetypes. What name should we use ? Probably, glpk_mps, glpk_lp, glpk_fmps, glpk_mathprog, and glpk_glp, it might work but messy. Aside from this, glpsol has ability to translate/convert one format to another. Most of the solvers use mps format. GLPK is one of the best in the area and this is the reason why I am promoting GLPK to the Geany users.
I know its messy but it is available NOW. All other options require development and will therefore take time.
In GUSEK IDE, we use, c, sql and asm lexers to create the glmp.properties.
In TextAdept, I adopted c lexer and modified it to create glpk.lua lexer. TextAdept use the lua dynamic lexer loading.
Oh, Ok you have your own lexer, which you would need to add to Geany anyway.
- a plugin is added which modifies the command for GLPK files
depending
on
the extension, this requires the re-make to be available (and the plugin
to
be written) but might be considered to be cleaner
I think this is the best option.
To use method 1 all you need to do is to copy your current filetypes file
so
you have one per extension, set the compile (or whatever) command in the [build-menu] section for each, and edit filetype_extensions.conf to reference them.
I think this is the hack (method 1) and probably use just use - glpk1, glpk2, glpk3, glpk4, glpk5
I hope Geany developers that address this issue.
Right now, windows users can use GUSEK IDE and TextAdept, for Mac OS X users TextAdept and for linux users TextAdept and classic editors.
As I said option 1 its a way of using Geany until alternative means is supported, or use these alternatives instead.
Cheers Lex
Lex, thanks again.
Regards, Noli _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On 23 February 2010 21:14, Noli Sicad nsicad@gmail.com wrote:
Lex,
I think "execute" is broken in this nightly build 22 February. Python programs are not running as well.
Noli
Sadly I can't help you with windows, I don't run or build Geany on windows.
Hopefully someone else will be able to look at it for you.
Cheers Lex
OK. Thanks. I am downloading geany svn 23 February. I am compiling for Mac OS X. I will report if I can run one of mathprog model (*.mod).
Noli
On 2/23/10, Lex Trotman elextr@gmail.com wrote:
On 23 February 2010 21:14, Noli Sicad nsicad@gmail.com wrote:
Lex,
I think "execute" is broken in this nightly build 22 February. Python programs are not running as well.
Noli
Sadly I can't help you with windows, I don't run or build Geany on windows.
Hopefully someone else will be able to look at it for you.
Cheers Lex
Lex,
Again, no sucess.
In Mac OS X, 23 February build
[build_settings] # %f will be replaced by the complete filename # %e will be replaced by the filename without extension # (use only one of it at one time) #compiler=/usr/local/bin/glpsol -m "%f" #linker=g++ -Wall -o "%e" "%f" run_cmd="/usr/local/bin/glpsol -m "%f""
error
./geany_run_script.sh: line 5: ./filetypes: No such file or directory
------------------ (program exited with code: 127) Press return to continue
Noli
Keine ahnung!
On 2/23/10, Noli Sicad nsicad@gmail.com wrote:
OK. Thanks. I am downloading geany svn 23 February. I am compiling for Mac OS X. I will report if I can run one of mathprog model (*.mod).
Noli
On 2/23/10, Lex Trotman elextr@gmail.com wrote:
On 23 February 2010 21:14, Noli Sicad nsicad@gmail.com wrote:
Lex,
I think "execute" is broken in this nightly build 22 February. Python programs are not running as well.
Noli
Sadly I can't help you with windows, I don't run or build Geany on windows.
Hopefully someone else will be able to look at it for you.
Cheers Lex
On 23 February 2010 22:34, Noli Sicad nsicad@gmail.com wrote:
Lex,
Again, no sucess.
In Mac OS X, 23 February build
[build_settings] # %f will be replaced by the complete filename # %e will be replaced by the filename without extension # (use only one of it at one time) #compiler=/usr/local/bin/glpsol -m "%f" #linker=g++ -Wall -o "%e" "%f" run_cmd="/usr/local/bin/glpsol -m "%f""
error
./geany_run_script.sh: line 5: ./filetypes: No such file or directory
Hmmmm, try configuring using the [build-menu] settings, [build_settings] is the old format that is not necessarily properly converted in the SVN version because it does not contain all the information that the new format needs so some defaults are picked, but of course they might not be right.
In fact you could try configuring it with the dialog, that should write the new section and format to your user filetype file.
Also I'd recommend that you configure the compile command, not the execute command. That way the output from the command is captured and shown in the message window. And if glpsol is consistent with the GCC error format it will be parsed for easily jumping to the source of the error.
Cheers Lex
(program exited with code: 127) Press return to continue
Noli
Keine ahnung!
On 2/23/10, Noli Sicad nsicad@gmail.com wrote:
OK. Thanks. I am downloading geany svn 23 February. I am compiling for Mac OS X. I will report if I can run one of mathprog model (*.mod).
Noli
On 2/23/10, Lex Trotman elextr@gmail.com wrote:
On 23 February 2010 21:14, Noli Sicad nsicad@gmail.com wrote:
Lex,
I think "execute" is broken in this nightly build 22 February. Python programs are not running as well.
Noli
Sadly I can't help you with windows, I don't run or build Geany on windows.
Hopefully someone else will be able to look at it for you.
Cheers Lex
Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Lex,
Hmmmm, try configuring using the [build-menu] settings, [build_settings] is the old format that is not necessarily properly converted in the SVN version because it does not contain all the information that the new format needs so some defaults are picked, but of course they might not be right.
In fact you could try configuring it with the dialog, that should write the new section and format to your user filetype file.
OK. I try to look at it. But it seems the dialog form is only intended for real languages i.e. c and c++ and really for scripting languages.
Also I'd recommend that you configure the compile command, not the execute command. That way the output from the command is captured and shown in the message window. And if glpsol is consistent with the GCC error format it will be parsed for easily jumping to the source of the error.
I have configure the compile command but still error
[build_settings] # %f will be replaced by the complete filename # %e will be replaced by the filename without extension # (use only one of it at one time) compiler=/usr/local/bin/glpsol -m "%f" #linker=g++ -Wall -o "%e" "%f" run_cmd="/usr/local/bin/glpsol -m "%f""
Would it be possible to show me the right syntax on compiler for linux?
I tried these commands:
compiler=/usr/local/bin/glpsol -m "%f"
compiler="/usr/local/bin/glpsol -m "%f""
The 2 syntax is not working. What is the right syntax for linux, mac os and windows?
Based on experience glpsol is not so difficult to run in scintilla base editors. R package is the worst to configure.
Any R package users in this group? How do you configure R package in windows, mac os x and linux in geany?
Please show us your compiler and cmd_run configuration?
Any of 56 languages in the scintilla lexer will do? Not c/c++, python, perl, php, javac, current languages that run out of the box (default) in geany
Thanks. Noli
On 24 February 2010 09:18, Noli Sicad nsicad@gmail.com wrote:
Lex,
Hmmmm, try configuring using the [build-menu] settings, [build_settings]
is
the old format that is not necessarily properly converted in the SVN
version
because it does not contain all the information that the new format needs
so
some defaults are picked, but of course they might not be right.
In fact you could try configuring it with the dialog, that should write
the
new section and format to your user filetype file.
OK. I try to look at it. But it seems the dialog form is only intended for real languages i.e. c and c++ and really for scripting languages.
Part of the changes I am about to make will be to improve the dialog by breaking it into a simple and advanced version.
It should work now, but both custom filetypes and the build system are newly added to the development version so there may still be bugs, especially when using them together :-(
Also I'd recommend that you configure the compile command, not the
execute
command. That way the output from the command is captured and shown in
the
message window. And if glpsol is consistent with the GCC error format it will be parsed for easily jumping to the source of the error.
I have configure the compile command but still error
[build_settings] # %f will be replaced by the complete filename # %e will be replaced by the filename without extension # (use only one of it at one time) compiler=/usr/local/bin/glpsol -m "%f" #linker=g++ -Wall -o "%e" "%f" run_cmd="/usr/local/bin/glpsol -m "%f""
Would it be possible to show me the right syntax on compiler for linux?
I tried these commands:
compiler=/usr/local/bin/glpsol -m "%f"
compiler="/usr/local/bin/glpsol -m "%f""
The 2 syntax is not working. What is the right syntax for linux, mac os and windows?
Is the first syntax working? That should be it on Linux, I don't use Geany on Windows and I don't even have a Mac, but as far as I know the commands should be the same as the command line with the %f as you used.
Based on experience glpsol is not so difficult to run in scintilla base editors. R package is the worst to configure.
Any R package users in this group? How do you configure R package in windows, mac os x and linux in geany?
Someone was working on the R integration recently, maybe they will see this and can help.
Please show us your compiler and cmd_run configuration?
Any of 56 languages in the scintilla lexer will do? Not c/c++, python, perl, php, javac, current languages that run out of the box (default) in geany
Thanks. Noli _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Wed, 24 Feb 2010 12:28:18 +1100 Lex Trotman elextr@gmail.com wrote:
Someone was working on the R integration recently, maybe they will see this and can help.
I've done a little work with R package, but I must confess that I just did everything in a terminal rather than through geany. I'll add it to my todo list of things to take a look at, but I don't know that I'll get a chance in the near future.
Jon
Jon,
Most of the problem of R package inside editor is the graphic windows is not showing up. However, the plugin in kodomo Edit manage pass the input file from the editor to the Rwindow and the result of the graphic windows. This is both for Kodomo edit in windows, mac os x and mostly in linux as well. I don't have linux installation at the moment.
Regards, Noli
On 2/24/10, Jon Senior jon@restlesslemon.co.uk wrote:
On Wed, 24 Feb 2010 12:28:18 +1100 Lex Trotman elextr@gmail.com wrote:
Someone was working on the R integration recently, maybe they will see this and can help.
I've done a little work with R package, but I must confess that I just did everything in a terminal rather than through geany. I'll add it to my todo list of things to take a look at, but I don't know that I'll get a chance in the near future.
Jon _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel