#Textadept start without configuration how to
#Textadept start without configuration mac os
#Textadept start without configuration portable
#Textadept start without configuration code

By the way, this changes has no short-time prevision ifĭepends only on my effort - i'm writing my msc. But it can be more complex to the final user. Or directly incorporate the GLPK languages in the sourceĮditor, as well.

#Textadept start without configuration code

Rebuilds and code changing after every new version of the base My last idea was convert Gusek into a plugin to an text-editor, avoiding

#Textadept start without configuration portable

It will make Gusek less portable (needs GTK+2 runtime), but can be aīetter option make it more cross-platform than portable. Relatively new and not so popular / stable. Sounds good, based on Scite (can be easier migrate), flexible, but it is Screenshot - output pane - status, compiler, messages, scribble, Luiz, which one is easier to port, TextAdept or Geany?īut I think Geany has more advance features just looking at the I just encountered TextAdept last night will googling for scintillaĪnd scite software. syntax lighting,Ĭompiling or running and getting the results. Use when you are looking for advance features i.e. I have been toying the idea that probably Komodo Edit would be goodĬandidate for cross platform GLPK/MathProg IDE.

#Textadept start without configuration mac os

SciTE 2.03, both replied saying that it would not compile in Mac OS X.

#Textadept start without configuration how to

Mike Lischke (SciTE for Mac OS X) regarding how to compile the latest I emalied Neil Hodgson (author of SciTE) and Officially, it would NOTĬompile in Mac OS X. I think SciTE is out of the question now. I openĪlmost everything with GUSEK and see what is the content of the such I think GLPK/GMLP needs a cross platform IDE take advantage of ODBCĬapabilities of Mathprog in reading and writing tables in databases Thanks a lot making the discussion of cross platform GLPK/GMLP alive. (and thanks, i'll need some luck (in thesis) ! =) Someone can share their expertise with them, also, to help us decide. We can test these (and others) editors to get more solid impressions. Who wants an GLPK IDE? What OS they are using? Portable, needs GTK to run, more slow, bigger sizes, maybe requireĪdditional configuration like system enviroment.), so we need to ask: Gusek Windows users will be prejudiced by editor migration (not Under windows, but really faster under Linux. TextAdept appear to be more flexible, but less sophisticated (as you How much easier one than other? I don't know, need more research.

Geany and TextAdept are based on scintilla, so can be less complex to Komodo looks good, also, but i'm not sure how complicated can be use it. With Mac OS will be great, if someone can join and develop - today even I'm not a Mac OS user, then will be necessary some people to help toĭevelop / debug possible ports. Sounds good see more people using it as is. I've been using Gusek as you described in the last 2 years, it's my Re: Gusek / Scite2003 Linux and (Mac OS X?) VS Codium).Re: Gusek / Scite2003 Linux and (Mac OS X?) help-glpk On VS Code, while built on electron, it still feels fast, and open source builds do exist (e.g. My point is that I’d make these (or Windows support) the reason for the sake of clarity. Avoiding friction or wanting to learn one thing at a time (and thus focus on the thing you’re learning) are very valid. Key-bindings also quickly become muscle-memory, allowing you to quickly navigate without thought other than what you’re looking for it all becomes automatic.Īll that said, I’ve been recommending VS Code whenever anyone getting started with Julia asks for an editor recommendation (for Atom, the writing is on the wall). I’ve also seen people talk online about how much time they spend messing with their config files for these editors, which I found off-putting.īut I’ve hardly touched mine after starting, and certainly not found it to be a distraction. I wouldn’t characterize them as not-modern pejoratively.īut if you don’t want something with a steep learning curve, that is perfectly reasonable. On emacs and vim: they can be powerful, and they’re actively maintained.