OpenEuphoria

2. Re: Geany setup for Euphoria?

• Posted by Kir_Eev Dec 29, 2010
• 39423 views

If there is no ready-made settings, ask for help from English-speaking colleagues to freely read the documentation geany. In consequence of my poor English have difficulty understanding the details

Sorry Google, for his English :)

4. Re: Geany setup for Euphoria?

• Posted by Jerome Jan 01, 2011
• 39312 views

I'm also a big fan of Geany, and here is my attempt to add some Euphoria support. I don't think it has all the correct syntax coloring, but it works well for me. Here are the steps I used to get it working in Geany 0.19.2 on Ubuntu (I'm not sure if this will work on older versions of Geany...)

1) Make a file "filetypes.Eu.conf" and place it in "~/.config/geany/filedefs/" The contents of the file are listed below.
2) Edit "filetype_extensions.conf" located in "~/.config/geany/" to include an Eu reference, such as:

... 
D=*.d;*.di; 
# Eu filetypes  
Eu=*.ex;*.exw;*.e; 
F77=*.f;*for;*.ftn;*.f77; 
... 

That should do it. Also, you could make these changes globally in the Geany install directory instead of the the user path.

Hope this helps,
Ira

filetypes.Eu.conf

# For complete documentation of this file, please see Geany's main documentation 
[styling] 
# foreground;background;bold;italic 
default=default 
comment=comment 
commentline=comment 
commentdoc=commentdoc 
number=number 
word=word 
word2=word2 
string=string 
character=string 
uuid=0x404080 
preprocessor=preprocessor 
operator=operator 
identifier=default 
stringeol=stringeol 
# @"verbatim" 
verbatim=0x101030 
# (/regex/) 
regex=0x105090 
commentlinedoc=commentdoc,bold 
commentdockeyword=commentdoc,bold,italic 
commentdockeyworderror=commentdoc 
globalclass=type 
 
[keywords] 
# all items must be in one line 
primary=and as break by case constant continue do else elsif elsifdef end entry enum exit export fallthru for function global goto if ifdef include label loop namespace not or override procedure public retry return routine switch then to type until while witch without xor 
secondary=abort and_bits append arctan atom c_func c_proc call call_func call_proc clear_screen close command_line compare cos date delete delete_routine equal find find_from floor get_bytes get_key get_pixel getc getenv gets hash head include_paths insert integer length log machine_func machine_proc match match_from mem_copy mem_set not_bits object open option_switches or_Bits peek peek2s peek2u peek4s peek4u peek_string peeks pixel platform poke poke2 poke4 position power prepend print printf profile profile_time puts rand remainder remove repeat replace routine_id sequence sin splice sprintf sqrt string system system_exec tail tan task_clock_start task_clock_stop task_create task_list task_schedule task_self task_status task_suspend task_yield time trace value warning xor_bits xpcall 
# these are some doxygen keywords (incomplete) 
docComment=warning 
 
[settings] 
lexer_filetype=C 
tag_parser=Python 
 
# default extension used when saving files 
extension=gs 
 
# the following characters are these which a "word" can contains, see documentation 
#wordchars=_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 
 
# if only single comment char is supported like # in this file, leave comment_close blank 
#comment_open=// 
#comment_close= 
# this is an alternative way, so multiline comments are used 
comment_open=/* 
comment_close=*/ 
 
[build-menu] 
FT_00_LB=_Compile 
FT_00_CM=euc "%f" 
FT_00_WD= 
FT_01_LB=_Build 
FT_01_CM=eubind "%f" 
FT_01_WD= 
FT_00_LB=_Run 
FT_00_CM=eui "%f" 
FT_00_WD= 

6. Re: Geany setup for Euphoria?

• Posted by Jerome May 24, 2011
• 38982 views

I don't think I ever had any luck getting '--' recognized as comments. The color definitions are explained here: http://www.geany.org/manual/current/index.html#filetype-definition-files. I think I tried editing comment_open and comment_close, but it didn't like '--' for some reason!

Thanks,
Ira

8. Re: Geany setup for Euphoria?

• Posted by penpal0andrew May 24, 2011
• 38913 views

Actually I change my recommendation - VIM is the best editor! The color syntax is almost a non issue. The commands are a bit to get used to, but that is okay.

10. Re: Geany setup for Euphoria?

• Posted by jaygade May 24, 2011
• 38925 views

Yes, Vim is probably the most awesome editor.

12. Re: Geany setup for Euphoria?

• Posted by penpal0andrew May 24, 2011
• 38936 views

Matt -

Thanks for the sense of humor.

Which files from trunk should I grab?

Thanks.

14. Re: Geany setup for Euphoria?

• Posted by K_D_R Oct 25, 2011
• 38678 views

A rose by any other name is a rose just the same...

As far as I can tell, I have gained full Geany support for Euphoria. The only hitch is that you can't call it "Euphoria". I basically rewrote all the lua files for Euphoria. I suppose you could do it with any of the other fully supported files located in /usr/share/Geany/ just as well. I was never able to get color support to work using custom file types.

Geany has 7+ user defined sections in it's "Build" menu which can be configured to compile, Shroud, Bind, probably even to gather files for distribution using "eudist". It also has a configurable context command which can be assigned to a key.

The syntax color support looks very complicated at first blush, but there is a color chooser available in the tools menu which makes it a snap to configure the colors to your preference.

# filetypes.lua edited to support the Euphoria Programming Language 
# The lua filetype extensions in the global filetype_extensions file should be changed to Euphoria extensions 
# Lua=*.e;*.ex;*.eu;*.ew;*.exw; 
 
 
[styling] 
# foreground;background;bold;italic 
default=0x000000;0xffffff;false;false 
comment=0xd00000;0xffffff;false;false 
commentline=0xd00000;0xffffff;false;false 
# commentdoc=0x3f5fbf;0xffffff;true;false 
number=0x007f00;0xffffff;false;false 
word=0x00007f;0xffffff;true;false 
string=0xff901e;0xffffff;false;false 
character=0x008000;0xffffff;false;false 
literalstring=0x008020;0xffffff;false;false 
preprocessor=0x007f7f;0xffffff;false;false 
operator=0x301010;0xffffff;false;false 
identifier=0x000000;0xffffff;false;false 
stringeol=0x000000;0xe0c0e0;false;false 
keywords=0x0000FF;0xffffff;true;false 
function_other=0xCC99CC;0xffffff;false;false 
# extra could be used for 3rd party libraries: 
extra=0x#404080 
 
[keywords] 
# all items must be in one line 
 
keywords=and as break by case constant continue do else elsedef elsif elsifdef end entry export fallthru for function global goto if ifdef include label loop namespace not or override procedure public retry return routine switch then to type until while with without xor 
 
function_other=? abort and_bits append arctan atom c_func c_proc call call_func call_proc clear_screen close command_line compare cos date delete delete_routine equal find floor get_key getc getenv gets hash head include_paths insert integerlength log machine_func machine_proc match mem_copy mem_set not_bits object open option_switches or_bits peek peek2s peek2u peek4s peek4u peek_string peeks pixel platform poke poke2 poke4 position power prepend print printf puts rand remainder remove repeat replace routine_id sequence sin splice sprintf sqrt system system_exec tail tan task_clock_start task_clock_stop task_create task_list task_schedule task_self task_status task_suspend task_yield time trace xor_bits 
 
[settings] 
lexer_filetype=C 
tag_parser=c 
# default extension used when saving files 
extension=ex 
 
# the following characters are these which a "word" can contains, see documentation 
#wordchars=_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 
 
# if only single comment char is supported like # in this file, leave comment_close blank 
comment_open=-- 
comment_close= 
# this is an alternative way, so multiline comments are used 
#comment_open=--[[ 
#comment_close=]]-- 
 
# set to false if a comment character/string should start at column 0 of a line, true uses any 
# indentation of the line, e.g. setting to true causes the following on pressing CTRL+d 
#	#command_example(); 
# setting to false would generate this 
#	command_example(); 
# This setting works only for single line comments 
comment_use_indent=true 
 
# context action command (please see Geany's main documentation for details) 
context_action_cmd=epiphany http://openeuphoria.org/search/results.wc?manual=1&s="%s" 
 
[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=eui ./"%f" 
 
[build-menu] 
EX_00_LB=_Execute 
EX_00_CM=eui ./%e 
EX_00_WD= 
 
FT_00_LB=Compile 
FT_00_CM=euc  "%f" 
FT_00_WD= 
FT_01_LB=Bind 
FT_01_CM=eubind  "%f" 
FT_01_WD= 
FT_02_LB=Shroud 
FT_02_CM=eushroud  "%f" 
FT_02_WD= 

16. Re: Geany setup for Euphoria?

• Posted by K_D_R Oct 25, 2011
• 38600 views

Thanks - I corrected my post.

I do hope more people will give Geany a trial run. It is really a fantastic editor.

18. Re: Geany setup for Euphoria?

• Posted by Jerome Oct 27, 2011
• 38476 views

Thanks for the work! Geany is one of my favorite editors as well.

Ira

20. filetypes.lua edited to support Euphoria

• Posted by K_D_R Oct 31, 2011
• 38167 views

Well, I have learned a bit since my last few posts. One, the filetypes.language file which you choose to edit to support Euphoria does not have to reside in /usr/share/geany/ so root or superuser privileges are not required. Two, the filetypes.language files are extremely sensitive. I edited the filetypes.lua file which I was using with instructions contained in comments and uploaded the file to the RDS User Contributions page. After I upgraded from Geany 20 to Geany 20.1, I downloaded the file and was never able to get it to work properly.

Suffice it to say, you can copy the particular language filetypes file which you wish to use to /home/.config/geany/fildefs and edit it to support Euphoria. My current set up is as follows, using /home/.config/geany/filedefs/filetypes.lua:

# For complete documentation of this file, please see Geany's main documentation 
 
[styling] 
# foreground;background;bold;italic 
default=0x000000;0xffffff;false;false 
comment=0xd00000;0xffffff;false;false 
commentline=0xd00000;0xffffff;false;false 
commentdoc=0x3f5fbf;0xffffff;true;false 
number=0x007f00;0xffffff;false;false 
word=0x00007f;0xffffff;true;false 
string=0xff901e;0xffffff;false;false 
character=0x008000;0xffffff;false;false 
literalstring=0x008020;0xffffff;false;false 
preprocessor=0x007f7f;0xffffff;false;false 
operator=0x301010;0xffffff;false;false 
identifier=0x000000;0xffffff;false;false 
stringeol=0x000000;0xe0c0e0;false;false 
keywords=0x0000FF;0xffffff;true;false 
function_basic=0x991111;0xffffff;false;false 
function_other=0xA52A2A;0xffffff;false;false 
 
[keywords] 
# all items must be in one line 
#keywords=and break do else elseif end false for function if in local nil not or repeat return then true until while 
keywords=and as break by case constant continue do else elsedef elsif elsifdef end entry export fallthru for function global goto if ifdef include label loop namespace not or override procedure public retry return routine switch then to type until while with without xor 
# Basic functions 
function_basic=? abort and_bits append arctan atom c_func c_proc call call_func call_proc clear_screen close command_line compare cos date delete delete_routine equal find floor get_key getc getenv gets hash head include_paths insert integerlength log machine_func machine_proc match mem_copy mem_set not_bits object open option_switches or_bits peek peek2s peek2u peek4s peek4u peek_string peeks pixel platform poke poke2 poke4 position power prepend print printf puts rand remainder remove repeat replace routine_id sequence sin splice sprintf sqrt system system_exec tail tan task_clock_start task_clock_stop task_create task_list task_schedule task_self task_status task_suspend task_yield time trace xor_bits 
function_other=check_free_list db_close db_compress db_create db_create_table db_delete_record db_delete_table db_dump db_fatal_id db_find_key db_insert DB_LOCK_NO DB_OK db_open db_record_data db_record_key db_rename_table db_replace_data db_select db_select_table db_table_list db_table_size 
 
[settings] 
# default extension used when saving files 
extension=ex 
 
# if only single comment char is supported like # in this file, leave comment_close blank 
comment_open=-- 
comment_close= 
# this is an alternative way, so multiline comments are used 
#comment_open=/* 
#comment_close=*/ 
 
# set to false if a comment character/string should start at column 0 of a line, true uses any 
# indentation of the line, e.g. setting to true causes the following on pressing CTRL+d 
	#command_example(); 
# setting to false would generate this 
#	command_example(); 
# This setting works only for single line comments 
comment_use_indent=true 
 
# context action command (please see Geany's main documentation for details) 
context_action_cmd=epiphany http://openeuphoria.org/search/results.wc?manual=1&s="%s" 
 
[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) 
 
[build-menu] 
EX_00_LB=Run Source File with Euphoria Interpreter 
EX_00_CM=\seui ./%f 
EX_00_WD= 
FT_00_LB=Translate source to C code & Compile 
FT_00_CM=euc "%e" 
FT_00_WD= 
FT_01_LB=Bind source code with interpreter 
FT_01_CM=eubind "%e" 
FT_01_WD= 
FT_02_LB=Gather files into Eudist directory 
FT_02_CM=eudist "%f" 
FT_02_WD= 
EX_01_LB=Execute Compiled or Bound Code File 
EX_01_CM=\s./%e 
EX_01_WD=