Hi
I want to use Geany as a LaTeX editor. However, for now (version 0.14), there is no tool available for makeindex and bibtex.
It would be very practical to have such a tool, just like a tool for pdflatex and pdfview with the ability to set parameters, e.g. by hitting the key F6 with command parameters makeindex "%e.idx" e.g. by hitting the key F7 with command parameters bibtex "%f"
Wilfried
Yes, I do agree that this would be a very helpful feature for those of us using Geany for editing Latex files. I use VTE for bibtexing, but it is not the most practical way to do that. I also suggest the inclusion of options to completely build a ps or a pdf file from source, in the same manner as the rubber utility (http://www.pps.jussieu.fr/~beffara/soft/rubber/) does.
Thanks.
Adrovane.
2008/6/14 Wilfried Van Hirtum wilfriedvanhirtum@yahoo.com:
Hi
I want to use Geany as a LaTeX editor. However, for now (version 0.14), there is no tool available for makeindex and bibtex.
It would be very practical to have such a tool, just like a tool for pdflatex and pdfview with the ability to set parameters, e.g. by hitting the key F6 with command parameters makeindex "%e.idx" e.g. by hitting the key F7 with command parameters bibtex "%f"
Wilfried
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Sat, 14 Jun 2008 11:23:30 -0300, "Adrovane Kade" adrovane@gmail.com wrote:
Yes, I do agree that this would be a very helpful feature for those of us using Geany for editing Latex files. I use VTE for bibtexing, but it is not the most practical way to do that. I also suggest the inclusion of options to completely build a ps or a pdf file from source, in the same manner as the rubber utility (http://www.pps.jussieu.fr/~beffara/soft/rubber/) does.
I'm not a LaTeX user and I actually don't like the current way of having Create DVI/PDF and Run DVI/PDF commands. Every filetype in Geany has a Compile, an optionally Linker and a Run command. LaTeX is the only filetype which has more, special commands and this caused lots of extra code whereas all other filetypes are handled by a smaller, more generic code base.
Instead of adding even more very special cases for LaTeX, I'd like to remove the special code and make it as every other filetype. For the mentioned special cases, Makefiles can be used, a separate plugin (probably best way). There is already a GeanyLatex plugin which adds some more functionality, maybe it can be extend to provide better build commands for special LaTeX needs and we can remove the special code from Geany's core to keep it cleaner.
As a workaround for a least one more command you can use the "Context action command" (see the manual for details).
Regards, Enrico
Hi,
On Sun, June 15, 2008 11:45 am, Enrico Tröger wrote:
Instead of adding even more very special cases for LaTeX, I'd like to remove the special code and make it as every other filetype.
With existing plugin interface a much better way.
For the mentioned special cases, Makefiles can be used, a separate plugin (probably best way).
I know a number of people that are using makefiles for their bigger documents. I've never tried it.
There is already a GeanyLatex plugin which adds some more functionality, maybe it can be extend to provide better build commands for special LaTeX needs and we can remove the special code from Geany's core to keep it cleaner.
Extending of GeanyLatex is planned for one of the upcoming versions also with support for bibtex. Makeindex wasn't on my ToDo-list, but maybe it is also possible to add support for it. Even I think this will be a bit more compelcated, since there are als a number of alternative application for doing stuff of makeindex. I'm guessing for example xindy can do something like that. The next step at GeanyLatex will be to update the build system as well as the binding to Geany's plugin API. But, patches are highly welcome ;)
Regards, Frank
On Sun, 15 Jun 2008 13:45:26 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
...
Instead of adding even more very special cases for LaTeX, I'd like to remove the special code and make it as every other filetype.
I think this is best also.
...
There is already a GeanyLatex plugin which adds some more functionality, maybe it can be extend to provide better build commands for special LaTeX needs and we can remove the special code from Geany's core to keep it cleaner.
Yes, or maybe even a plugin that just adds extra command items to run (if anyone wants to write it ;-)).
Regards, Nick
Yes, now that I know more about the plugin model, I can see that you are right. A plugin with this features would be really nice. I'm so sorry I can't directly contribute with this effort, because I'm not really a C developer. :-(
Regards, Adrovane.
2008/6/16 Nick Treleaven nick.treleaven@btinternet.com:
On Sun, 15 Jun 2008 13:45:26 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
...
Instead of adding even more very special cases for LaTeX, I'd like to remove the special code and make it as every other filetype.
I think this is best also.
...
There is already a GeanyLatex plugin which adds some more functionality, maybe it can be extend to provide better build commands for special LaTeX needs and we can remove the special code from Geany's core to keep it cleaner.
Yes, or maybe even a plugin that just adds extra command items to run (if anyone wants to write it ;-)).
Regards, Nick _______________________________________________ Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Hi,
On Mon, June 16, 2008 12:59 pm, Adrovane Kade wrote:
Yes, now that I know more about the plugin model, I can see that you are right. A plugin with this features would be really nice.
Can you explain a bit more detailed, what you are thinking about?
I'm so sorry I can't directly contribute with this effort, because I'm not really a C developer. :-(
Me also not and I'm pretty sure my code looks like exactly like this. ;)
But there are more ways then only contribute code for supporting a plugin/project. but you already know.
Cheers, Frank
Hi, Frank.
2008/6/16 Frank Lanitz frank@frank.uvena.de:
Can you explain a bit more detailed, what you are thinking about?
I simply didn't know there was a plugin like geanyLatex. Besides that, I think it's preferable to have additional features provided by plugins than inserted in the main code. IMHO, this keeps the main code simpler, as well as the plugins keep it extendable. Just a thought, however.
Me also not and I'm pretty sure my code looks like exactly like this. ;) But there are more ways then only contribute code for supporting a plugin/project. but you already know.
Yeah! You can keep counting on me :-)
Regards, Adrovane.
On Mon, 16 Jun 2008 13:37:47 -0000 (UTC) "Frank Lanitz" frank@frank.uvena.de wrote:
Hi,
On Mon, June 16, 2008 12:59 pm, Adrovane Kade wrote:
Yes, now that I know more about the plugin model, I can see that you are right. A plugin with this features would be really nice.
Can you explain a bit more detailed, what you are thinking about?
I was thinking about a plugin that allows the user to add a number of commands to run, usually ones that would use the current document's filename. So the user could set commands like bibtex "%f" or touch "%f" or just system-config-date or anything else they like. The plugin could show the commands in a Tools->Commands menu. It could also set configurable keybindings for each command dynamically, like the Lua plugin does.
Regards, Nick